Fix AD DS DNS Initialization Error

I’m running Windows Server 2019 inside a small VMware home-lab and my domain controller refuses to finish promoting itself. Active Directory Domain Services keeps reporting that “the initialization of the directory has not completed,” and as a side-effect the DNS service will not start. Every other machine in the lab simply shows “DNS unreachable,” so nothing can resolve names or join the domain.

I’d like someone who knows the ins-and-outs of AD DS on Server 2019—metadata cleanup, SYSVOL/NTDS health checks, secure channel repair, the whole lot—to jump in, locate the root cause of the stalled initialization, and bring DNS online so the controller functions as it should. Expect to work inside VMware vSphere, but all guest access will be through standard Windows tools (Server Manager, PowerShell, Event Viewer, and DNS/DHCP consoles).

Success for me means:
• AD DS completes its first-run initialization without errors
• The DNS service starts automatically and can resolve both internal and external queries
• Workstations in the same virtual network no longer report “DNS unreachable” and can join the domain

If this sounds straightforward to you, let’s get the lab talking again.