DNS failed to bind to the Domain Controller's IP address during startup, causing a cascade of AD and DNS registration failures.

Hi Keith Gauci,

The failure after rebooting is caused by a startup race condition between the DNS Server service and the virtual network adapter. On high-speed host hardware like your HPE ProLiant Gen10 Plus and Gen11 servers, the operating system boots so rapidly that the DNS service executable at %SystemRoot%\System32\dns.exe launches before the Hyper-V network driver (%SystemRoot%\System32\drivers\netvsc.sys) finishes Duplicate Address Detection on the virtual network card. Because the DNS server is configured to listen only on the server's specific IP address rather than all available interfaces, Windows stores that IP address in the ListenAddresses value under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DNS\Parameters. When dns.exe attempts to bind its network sockets exclusively to that IP address while the operating system is still verifying that no other device is using it, Windows rejects the request with Winsock error 10049 (WSAEADDRNOTAVAIL, meaning the requested address is not yet available). This logs DNS Event IDs 404 for TCP, 407 for UDP, and 408 for the failed socket. DNS service does not retry binding to that specific IPv4 address after the network finishes initializing, Active Directory cannot locate its zone (DNS Event ID 4013), the Netlogon service inside %SystemRoot%\System32\lsass.exe cannot register the domain locator records listed in %SystemRoot%\System32\Config\netlogon.dns (Netlogon Event ID 5774), and the DHCP Server service fails its Active Directory authorization check (DHCP Event ID 20322).

You need to configure the DNS service to listen on all IP addresses rather than binding to a specific IP address. Open the DNS Manager console by launching %SystemRoot%\System32\dnsmgmt.msc, right-click your server name, select Properties, open the Interfaces tab, and switch the selection to All IP addresses. Applying this setting deletes the restrictive ListenAddresses value from HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DNS\Parameters. This allows the DNS service to bind to the wildcard addresses 0.0.0.0 for IPv4 and :: for IPv6, which succeeds immediately during early boot without waiting for the virtual adapter to complete Duplicate Address Detection. Do not configure the DNS Server service for delayed automatic startup; delaying DNS on a sole Domain Controller will starve dependent Active Directory and Netlogon services of name resolution during boot. Finally, keep IPv6 enabled on the network adapter to maintain official Microsoft Domain Controller compliance, and verify inside Network Connections (%SystemRoot%\System32\ncpa.cpl) that the adapter lists the server's static IP as the primary DNS server alongside the loopback address 127.0.0.1 (and ::1 for IPv6) to ensure consistent local name resolution.

Hope this answer has brought you some useful information. If it did, please hit “accept answer”. Should you have any questions, feel free to leave a comment.

VPHAN