The only problem with using DNS round robin like this, is
that, in this scenario when 1 server is down, on average 1 in
3 requests to the web server will fail. But as previous
posters have commented DNS should respond with the same 3
addresses, but it will rotate the order each time, in
Jonas Fornander wrote:
Does anyone know if there is a simple way to mirror two servers
without spending $ on hardware? I'm NOT talking about mirroring the
OS and the files, I'm talking about sending http requests to a second
server if the first server is down/un-reachable. This is sometimes
Does anyone know if there is a simple way to mirror two servers
without spending $ on hardware? I'm NOT talking about mirroring the
OS and the files, I'm talking about sending http requests to a second
server if the first server is down/un-reachable. This is sometimes
referred to as
Aaron Burke [EMAIL PROTECTED] writes:
To my knowlege, yes. Lets say you had a server called www.
You would just give it two addresses in your domain configuration
files.
www IN CNAME 12.34.56.78
www IN CNAME 9.10.11.12
www IN CNAME 65.4.3.21
That should be A
Aaron Burke [EMAIL PROTECTED] writes:
To my knowlege, yes. Lets say you had a server called www.
You would just give it two addresses in your domain configuration
files.
www IN CNAME 12.34.56.78
www IN CNAME 9.10.11.12
www IN CNAME 65.4.3.21
That should be
The only problem with using DNS round robin like this, is that, in this
scenario when 1 server is down, on average 1 in 3 requests to the web server
will fail. But as previous posters have commented DNS should respond with the
same 3 addresses, but it will rotate the order each time, in the
Does anyone know if there is a simple way to mirror two servers
without spending $ on hardware? I'm NOT talking about mirroring the
OS and the files, I'm talking about sending http requests to a second
server if the first server is down/un-reachable. This is sometimes
referred to as
