control over them in all
likelihood.
Just my $0.02, and I may be wrong on some of the points... but I know he can
do this with DNS, just not necessarily practically.
Bill Ward
-Original Message-
From: Alan Mead [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 09, 2000 6:11 PM
To: [EMAIL
On Thu, 9 Nov 2000, Ed Lazor wrote:
>
> >What you need is the second server to assume the primary server's IP address.
>
> What if they the two servers are at different ISP's?
>
This is a sticky problem, one that I've been working on for a year (off
and on).
When a DNS entry points to more t
>What you need is the second server to assume the primary server's IP address.
What if they the two servers are at different ISP's?
-Ed
___
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
This sort of behavior is called names like "high availability" or "failure
roll-over". As you note, when the primary host is not operating, it cannot
refer surfers to the second. So this is not a solution you can implement
on the primary host. It has to be implemented "earlier" in the proces
Someone more knowledgeable will have to answer, but I figured I'd
step forward in the meanwhile and offer some ideas of where to explore.
I think I came across something like this awhile back and I think the
solution relates to DNS. Something having to do with mapping the domain
name to two ip a
