This is a path to problems. I recommend that after you demote a DC, and BEFORE CLICKING THE REBOOT BUTTON, go and remove DNS Server. Reboot. Go clean up DNS on another DC in the same or a covering site ASAP.
After you have run all of your demotions, use dcdiag and dnslint and netdiag to ensure that everything is clean. Social.forums.microsoft.com requires registration, but it's free. However, you've got plenty of technical talent on this forum right here, IMHO. From: richardmccl...@aspca.org [mailto:richardmccl...@aspca.org] Sent: Thursday, January 14, 2010 2:24 PM To: NT System Admin Issues Subject: DCPROMO demotion and DNS Greetings! Our network and AD structure have been in the process of being "moved", "renamed", "merged", "whatevered" for the past few weeks. All the workstations and laptops are now a part of the new domain. Next come all servers... Question - We have AD-integrated DNS through our DCs. What becomes of the DNS functions if the DC is demoted to a member server? Does it become a "secondary" DNS server getting its information from a remaining DC? Become a static DNS server (manual entries, etc but functioning on the information it had at the time of demo)? Cease any and all DNS services (but can be made a secondary DNS server later if desired)? One chooses what becomes of DNS at the time of demo? Any good links to a site that does not require registering for a blog/forum? Thanks! -- Richard D. McClary Systems Administrator, Information Technology Group ASPCA(r) ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
