Score:0

Can't get rid of old DC from DNS (reappear after deletion)

in flag

I think I'm missing something here with regards to a fundamental...

Had two 2012 r2 DC's (dc1 and dc2), dc1 was demoted years ago, and dc2 has been flying solo working just fine. Promo'd up a new DC1 last week without making sure everything was already clean.. bad assumption. The new DC1 wouldn't replicate (due to the bad existing data i assume) so we demoted it back down, and removed the DNS.

Now I still want to add the 2nd DC, and prefer to use the old name, even though yes choosing another name would be a cop out. So I want to make sure everything is cleaned out, but DNS is still showing a lot of _msdcs records for the old DC1.

I can find and delete all the old DC1 entries (with DFSR off or on) and they come back a short time later. Very standard install with AD integrated zones, all default stuff. There are no other DC's, REPADMIN clean, DCDIAG is clean, it is just the bad records keep coming back, and I want them to only register after I promo the server back into the environment. I tried to see if ADSIEDIT could get to the _msdcs stuff, but it appears not.

Ideas?

ZivkoK avatar
ru flag
It depends on how you demoted the DC but most probably you still have some metadata flying around. Here is one example on how to perform the cleanup afterwards : https://server-essentials.com/support/metadata-cleanup-remove-a-failed-domain-controller
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.