Hey Tony,
I will take a look at this today, and will get back to you today.
Thank you - J
Main Topics
Browse All TopicsHello guys,
I just did a demotion of a DC, and the demotion failed midstream with an error indication of "failed to configure the NETLOGON service as requested ... The wait operation timed out".
So I stopped the process, restarred the NETLOGON service, and re ran the demotion, all worked wellm the demotion finalized, system rebooted.
Now when I look at the DNS server (AD integrated), I notice that NS and A Record for the old DC is there, the A record is listed as "same as parent".
After further research I found that the DC I demoted had its NIC configured to point to only itself, so when I demoted it ofcourse "itself" would no longer be a valid DNS server.
So my question is:
1. Should i have set the secondary DNS of the demoted DC to an alternative DC before beginning?
2. Also, what do I do not to correct this issue at hand (extra DNS records). Should I go in and delete the NS and A record of the demoted DC (now member), and re register DNS?
Thank you all.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Yep, that seems fine. Now the server is just a member server, and not a DNS server, then really the only record that should remain for this server is the Host (A) record referring to it's DNS name (the same as any other client on the network).
So from what you have said, it looks like you've cleared it up correctly.
Tony
1
Depends if you're you using AD integrated DNS zones? If you are, you should use another DNS before demoting it. If you intend to keep it as a DNS server after the demotion, you will need to configure it as a primary, secondary or stub (depending on your DNS infrastructure.)
2
If the dcpromo failed, it would be worth running throught this to clean the active directory metadata and the DNS zones incase anything hasn't been removed properly.
http://support.microsoft.c
Hi there,
Just to avoid confusion, I think I may not have been clear earlier -
If you are demoting a DC that is also a DNS server, you don't have to point it to another DC in order to demote it. However, if you have it *only* pointing to itself, it may leave a few records in DNS after the installation. This will not cause the demotion to fail though. As you have experienced, you may have to manually remove a few records. Obviously you will also need to point it elsewhere after the demotion so it can still resolve names.
As you stated that the demotion the second tiome around was successful, then you shouldn't have to worry about a metadata cleanup.
Thanks.
Business Accounts
Answer for Membership
by: bluntTonyPosted on 2009-07-26 at 13:18:05ID: 24947228
Hi there,
1. No, during a successful demotion, the DC will remove itself from AD and these changes will replicate to all other DCs, i.e, that server will be removed from the other replicas. Since AD integrated DNS is actually part of AD, then this should be fine. You don't need to point the to use another DC for DNS before demoting.
2. When you say there is an NS and A record for the DC, if the server is no longer a DNS server then yes, remove the NS record. An NS record refers to a DNS server, so not necessarily always a DC.
A DC has more than one A record - the one which refers to the server's DNS name, e.g. 'server.domain.local' should remain as it is still required by the member server. The one that says '(same as parent)' should be deleted now the server isn't a DC. This is a record used by legacy clients to locate a DC. If you were to have any leftover SRV records leftover, then you would need to delete these as well, along with the CNAME record in the root of the _msdcs zone.
Hope this explains...