After performing a long round of recovery on a Server 2008R2 domain controller my one lingering issue is a corrupt primary DNS zone. This is a single DC environment with only the one primary DNS zone.
I am attempting to delete the zone and recreate it, then run a DCDiag to help put the pieces back together but running into the following error when trying to delete the zone:
The zone cannot be deleted.
The Active Directory service is not available.
All AD services are running and serving logon requests, but knowing now reliant on DNS AD is I'm guessing it's the corruption in DNS that's keeping me from deleting the zone.
I did attempt to remove the zone via ADSIEdit but it doesn't show up in the console, so it's really jacked up. And, unfortunately, a good back up is not available to restore from (that's a tongue lashing for another day).
Our Dev teams are like yours. They’re continually cranking out code for new features/bugs fixes, testing, deploying, testing some more, responding to production monitoring events and more. It’s complex. So, we thought you’d like to see what’s working for us.
In this article, I am going to show you how to simulate a multi-site Lab environment on a single Hyper-V host. I use this method successfully in my own lab to simulate three fully routed global AD Sites on a Windows 10 Hyper-V host.
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller.
Log onto the new domain controller with a user account t…
This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource.
Use Google, Bing, or other preferred search engine to locate trusted NTP …