That will work. You can use sysInternal PsTools like psExec to IPCONFIG a remote machine, if needed. Pipe all the static IPs out and re-enter them in DNS in the new w2k3 server. You must have a good reason for not using DHCP so I won't ask. ;-)
Cheers. -----Original Message----- From: Cody Lewis [mailto:co...@bfhd.wa.gov] Sent: Monday, March 30, 2009 11:28 AM To: NT System Admin Issues 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 does����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/> ~
