Windows 2019 RemoveDnsServerZoneDelegation

A

Alex3117

Many years ago I set up my test domain with a Windows 2008 R2 domain controller, and I named the DC "toph". At some point I decided to start naming my servers with characters from GI Joe, so I renamed the DC to "duke". Fast forward to this month. I've drug my feet (a lot) in upgrading my domain controller, so I decided to go from 2008 R2 right to 2019. I set up a 2019 server (cleverly named duke2), added it to the domain, transferred the fsmo roles, and then shut down the old domain controller (duke, formerly toph) for a week or so to make sure all the other computers in the lab were using the new DC properly. I used the approach found here:




SAtisfied things looked good, today I started the old DC back up, ran dcpromo, and things went fine except it told me it wasn't able to Delete the Zone Delegation, and I'd have to do that manually. Not a problem. DCPROMO completed and the old 2008 R2 server was no longer a DC. I checked Get-ADForest and Get-ADDomain and all looked well, so I went ahead and raised the forest level to 2016.


I then decided to attempt to manually remove the zone delegation as was instructed by the DCPROMO command. I found the powershell command Remove-DnsServerZoneDelegation, which I figured would probably be involved, but first I decided to run the related command Get-DnsServerZoneDelegation, and that's when I got this error.


Get-DnsServerZoneDelegation : There is no glue record associated with the name server toph.<mydomain>.net. in zone <mydomain>.net hosted on server DUKE2.
At line:1 char:1
+ Get-DnsServerZoneDelegation
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (DUKE2:root/Microsoft/...rZoneDelegation) [Get-DnsServerZoneDelegation], CimException
+ FullyQualifiedErrorId : WIN32 9714,Get-DnsServerZoneDelegation


Somehow the old name for the 2008 R2 server has gotten stuck somewhere it shouldn't be. Can anyone help me get this worked out?

Continue reading...
 
Back
Top Bottom