Local IP address cannot be registered on DNS server after DNS Client service is restarted in Windows

Applies to: Windows Server 2012 R2 DatacenterWindows Server 2012 R2 StandardWindows Server 2012 R2 Essentials


This issue occurs because the DNS client service has an idle time-out, and restarts on demand when required. This issue occurs when the DNS Client stops after it has been idle (15 minutes default) and then restarts. After the service restarts in Windows 8.1, Windows RT 8.1, or Windows Server 2012 R2, the local IP addresses stop being registered in DNS. Therefore, because the time stamp of the record is not updated, DNS scavenger eventually deletes this record, and the server becomes unreachable by DNS name.

Note This issue occurs only if the firewall rule that allows IPv6 Link-Local Multicast Name Resolution (LLMNR) traffic is disabled. When the rule is disabled, the service does not have to listen to the LLMNR traffic. Only then it stops when idle.


To work around this issue, enable the allow rule for LLMNR in the advanced firewall Microsoft Management Console (MMC).


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.


See the terminology that Microsoft uses to describe software updates.