Best practice for adding a third Windows DNS server for backup (not AD Integrated)
Posted on 2005-04-06
We are dusting off our Disaster Recovery plan and need some DNS advice. Our primary and secondary Win2003 DNS servers (stand alone, not AD) are located in a Co-Lo facility along with our web servers. If a major disaster were to occur at this facility, we can turn up and restore the web servers in a different location no problem, but we would be using a different block of IP addresses for all of our web sites, so there would be some DNS problems to resolve for sure.
In order to have the least amount of down time, our thinking was to install a 3rd dns server in a different location for all of the zones/domains we handle, which would just act as another secondary DNS server. But if a disaster were to occur at our main Co-Lo facility and knock out the 2 main dns servers, we could make this 3rd DNS server the primary (is this possible?) and load up the zones with the different block of IP addresses. Does this sound feasible?
How would you recommend we tackle this DNS issue? What logistics are we missing?