Follow up: Bring up the new DC with AD DNS. Then after hours do a quick IP address swap so the new DC has the old DC's IP address for your static clients. Then start bringing down the old DC.
-----Original Message----- From: Michael Leone [mailto:[email protected]] Sent: Tuesday, March 02, 2010 3:09 PM To: NT System Admin Issues Subject: Demote a DC that is primary DNS for a forest? I want to demote a DC that is the primary DNS for my forest. I have 2 other DNS servers in the forest (my parent domain). What I want to happen - I want to demote DC1 and still have it act as a DNS/DHCP server for the forest. (I have a number of devices with static IP addresses, that point to this DC for DNS and DHCP. I'd rather not have to go in and change all of them) Once I demote it, I can upgrade my Win200 AD to Win2003. At that point, I will re-format that machine (with the same IP), and then re-promote it to a DC in the new Win2003 AD. So: if I demote this DC, will the DNS still continue to work, and load the AD-integrated zones? Has anyone done this? What steps do I need to prepare beforehand? Reason I ask - I did something similar to a child domain - demoted a DC that was also DNS, and DNS would not load the AD-integrated zones after that (on that one server). I'm looking to avoid that. I *think* that may have happened becase the DC pointed to itself as primary DNS. In the case of the forest DCs, that is not the case - each forest DNS server points to a different DC for primary DNS, not itself. Thanks ~ 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/> ~
