Link to home
Start Free TrialLog in
Avatar of Seth Morris
Seth MorrisFlag for United States of America

asked on

Demoted DC still a part of DNS configuration

I've been having strange DNS issues, and poking around through the registry of the new DC, I found entries of the old DC that still seem relevant to current settings.
It is in HKLM\System\CurrentControlSet\Services\Microsoft\WindowsNT\CurrentVersion\DNS Server\Zones\18.168.192.in-addr.arpa
User generated imageThis server 192.168.18.12 is no longer carrying the DNS role, or AD.
I came to this by way of BPA , in which this server was listed in the servers to be Notified in the "Notify" options.
Either related or unrelated, my DHCP Bindings list is empty for some reason, but appears to be handing out addresses normally.
User generated imageIs this registry entry significant?
Is the DHCP binding issue related and fixable? (The DC with DHCP has a static address...)
Avatar of Shaun Vermaak
Shaun Vermaak
Flag of Australia image

How was server decommissioned? Did you try metadata cleanup?
Avatar of Seth Morris

ASKER

I did yes. From all appearances it was a clean demotion. I do not see any stale info in ntdsutil. FSMO roles are all hosted by new DC properly.
The only clue I have is that I believe I had set one or the other servers as a Secondary DNS instead of AD Integrated. Regardless, the current DC's with DNS are both AD Integrated zones
Do any of your existing DNS zones currently have zone transfers configured?
Indeed, I have both DC's hosting DNS set for Zone transfers only to servers in Name Servers, with correct servers listed. I have poured through _msdcs and forward/reverse zones for any wrong records.
ASKER CERTIFIED SOLUTION
Avatar of DrDave242
DrDave242
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
No further response. Removing the zone transfer configuration should remove the references.