Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

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


View products that this article applies to.

Cause

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.

↑ Back to the top


Workaround

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

↑ Back to the top


Status

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

↑ Back to the top


References

See the terminology that Microsoft uses to describe software updates.

↑ Back to the top


Keywords: kb, kbqfe, kbfix, kbsurveynew, kbexpertiseinter

↑ Back to the top

Article Info
Article ID : 3014170
Revision : 1
Created on : 1/7/2017
Published on : 2/10/2015
Exists online : False
Views : 239