There are several options for the goal you are seeking. The question is how much money you have. The best solution of course would be to distribute the site over geographically distant locations, multi-homed at each site peering (BGP) with multiple providers. Also, don't forget farms of redundant servers/switches/routers at each site with load balancers.
I suggest starting your high redundancy plan with a single good data center with redundant connections to an ISP with a very high SLA and a redundant backbone that is peered to multiple providers. Go redundant on switches and routers to your server farm, and add a pair of load balancers. You can also add DNS load balancers, cisco calls theirs "distributed director". I personally don't believe in relying on DNS for disaster recovery, unless I have a data center explode, I can bring everything back up long before the DNS updates propagate everywhere. 
 
Erik Mintz
Mail.com
 
 
----- Original Message -----
Sent: Wednesday, September 06, 2000 4:37 AM
Subject: dns

Hi,
 
I need a solution for the configuration below:
 
             Internet
             |         |
             |         |
     ISP A         ISP B
             |         |
             |         |
           Customer
                  |
             ----------------------------  Web Server
 
Web Server will has 2 IP addresses, one will be given by ISP A and the other one will be given by ISP B.
Primary DNS server is on ISP A and secondary DNS server is on ISP B.
The DNS server on ISP A has two records for customer's web server, for example :
www  a   10.0.0.1  (IP address given by ISP A)
www  a   20.0.0.1  (IP address given by ISP B)
The goal is to use dual ISP for back-up purpose, so the web server will serve for 24 hour / day.
Since the DNS server only load balance between two same host records, how about if one link is broken ?
For example :
Link from ISP B to Customer is broken, meanwhile someone in Internet is accessing the web server and the DNS server give him the IP address of  20.0.0.1, so the session will time out. He will has an access to web server until the DNS server give him the IP address of 10.0.0.1 (because the DNS server load balance these two records).
Are there any solutions to solve this problem, so the DNS server could detect the unreachable IP address and after that it would give the correct reachable IP address to the client ?
 
Thank you
 

Reply via email to