Hi Cody, can you bring up the new ones, make them DNS in the domain and let things replicate to them. Them decommission your old ones one at a time dcpromo, etc. to remove them. Next change the IP of one new server to use the old decommissioned server's ip address, and once that is replicated, do the same for the other old/new combo ?
Just a thought. Don K ----- Original Message ---- From: Cody Lewis <co...@bfhd.wa.gov> To: NT System Admin Issues <ntsysadmin@lyris.sunbelt-software.com> Sent: Monday, March 30, 2009 11:27:58 AM Subject: DNS server replacement I have 2 DNS servers (DCs) to replace and would like some opinions on strategy. They are AD integrated DNS. Clients are static ip configured. Domain is 2003, DNS servers are 2000 DCs, new servers are 2003 DCs. (I am upgrading the domain to 2003) I really do not want to touch client machines. So I would like to bring DNS up on new 2003 servers, swap the IP addresses of the old DNS and the new DNS. Am I missing anything? Is there a better strategy? I know I know...DHCP. Any guidance you guys may have would be appreciated. I found a few articles http://support.microsoft.com/kb/323383 on replacing primary DNS servers, but that doesn’t apply in an AD integrated situation right? Thanks Cody ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
