Sign in with Microsoft
Sign in or create an account.
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.


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 resolve this issue, install the December 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2.


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.

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?

Thank you for your feedback!