Planning for Emergencies -- A DNS Solution ?

wwebb at wwebb at
Fri Mar 17 20:13:09 UTC 2000

> You seem to be assuming that secondary servers are only used 
>when the  primary is unavailable....

I worded my previous message as set forth below poorly.  I realize 
that in the scenario I set out there would be no way of knowing if a 
particular inquiry was going to reach the server associated with the 
master or the slave--but then again, it would have at least some 
load balancing effect. :-)

Would there be any other drawbacks to the scenario below  ?

Bill Webb

> >Place the primary DNS server on the same server as 
> >the primary web server and the secondary DNS server  on the 
> >same server as the secondary web server.  The primary DNS 
> >server has an IP pointing to the primary web server. The 
> >dns server has an IP pointing it to the secondary  web server.  
> >dns records have very short TTL's.  
> >
> >If the primary goes down, then the primary dns server 
> >fails as well and people would automatically be routed to the 
> >secondary dns server, which would push them to the working 
> >website on the secondary network..  The secondary server 
> >also que mail for the primary, until it came online. 
> >
> >Also if the both networks are up, and the primary's pipe 
> >congested, then the site would be served up by the secondary...
> >
> >I suspect this solution will not be found in any RFC ;-)

More information about the bind-users mailing list