juanguirao
Technical User
I have two web servers hosting 2 copies of my site:
One copy with host1.com at IP 255.190.190.190 (bad example)
Another one with host2.com at IP 255.200.100.120 (another bad example)
I would like to setup the DNS so that if one of the web servers goes down, the users will be able to access the other one.
---
I have set up the DNS like this:
primary nameserver is on host 1: nsX.host1.com
secondary nameserver is on host 2: nsZ.host2.com
nsX.host1.com allows zone transfers to nsZ.host2.com so the information on both nameservers is identical.
THe SOA identifies nsX.host1.com as the primary nameserver.
However, I think this does not work.
Here's why...
Both nameservers have identical information and this information includes a single A-RECORD for the domain pointing at the web server on host 1 (255.190.190.190).
So, here is the problem...
If the web server 255.190.190.190 on host1.com goes down, then
- If the nameserver nsX.host1.com is not down, it will send the user to 255.190.190.190 (which is down)
- If the nameserver nsX.host1.com is down and nsZ.host2.com is not, then nsZ.host2.com will ALSO send the user to 255.190.190.190, which is down !
Dammit.
So what is the point of having two independent and geographically distant nameservers, if both have the same A-record for the domain and both send the user to the same IP address.
If machine for that IP address is down, then it does not matter how many nameservers you have, the user will always end up trying to load a site from a web server that is down.
IS THIS CORRECT?
IS THERE ANOTHER SOLUTION?
AM I MISSING SOMETHING?
Thanks,
DNS confused and Non redundant loser Juan Guirao
One copy with host1.com at IP 255.190.190.190 (bad example)
Another one with host2.com at IP 255.200.100.120 (another bad example)
I would like to setup the DNS so that if one of the web servers goes down, the users will be able to access the other one.
---
I have set up the DNS like this:
primary nameserver is on host 1: nsX.host1.com
secondary nameserver is on host 2: nsZ.host2.com
nsX.host1.com allows zone transfers to nsZ.host2.com so the information on both nameservers is identical.
THe SOA identifies nsX.host1.com as the primary nameserver.
However, I think this does not work.
Here's why...
Both nameservers have identical information and this information includes a single A-RECORD for the domain pointing at the web server on host 1 (255.190.190.190).
So, here is the problem...
If the web server 255.190.190.190 on host1.com goes down, then
- If the nameserver nsX.host1.com is not down, it will send the user to 255.190.190.190 (which is down)
- If the nameserver nsX.host1.com is down and nsZ.host2.com is not, then nsZ.host2.com will ALSO send the user to 255.190.190.190, which is down !
Dammit.
So what is the point of having two independent and geographically distant nameservers, if both have the same A-record for the domain and both send the user to the same IP address.
If machine for that IP address is down, then it does not matter how many nameservers you have, the user will always end up trying to load a site from a web server that is down.
IS THIS CORRECT?
IS THERE ANOTHER SOLUTION?
AM I MISSING SOMETHING?
Thanks,
DNS confused and Non redundant loser Juan Guirao