Share this question

Welcome to Teachnovice Q&A, where you can ask questions and receive answers from other members of the community.

This is a collaboratively edited question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Windows 10 DNS issues?

0 like 0 dislike
201 views

I'm experiencing DNS issues on my Win 10 machine which are the following:

  • On system start-up, everything works just fine
  • After some time, DNS requests start to time-out
  • When requests are timed out, the issue either persists for some time and then it starts working again by itself for a brief period of time (after which the issue is cycling again) or it persists till I Disable / Enable my adapter (which fixes it immediately, again for a brief period of time)

More details:

It affects only DNS. Requests like ICMP or direct IP are just fine. If the connection is established and there is no need to request DNS again for it - it works without any issues for any period of time.

During the time when there is a DNS issue, I can observe the following:

C:\Users\almado>nslookup yahoo.com
DNS request timed out.
    timeout was 2 seconds.
Server:  UnKnown
Address:  8.8.8.8

DNS request timed out.
    timeout was 2 seconds.
Non-authoritative answer:
Name:    yahoo.com
Addresses:  2001:4998:58:c02::a9
          2001:4998:c:a06::2:4008
          2001:4998:44:204::a7
          98.138.253.109
          98.139.183.24
          206.190.36.45

and for the DNS server itself:

C:\Users\almado>nslookup
DNS request timed out.
    timeout was 2 seconds.
Default Server:  UnKnown
Address:  8.8.8.8

What I've already tried

  • Using another DNS server (from snippets above it's obvious I was using Google public DNS at that time). I've tried using ISP-provided DNS both statically and with automatic settings options in the IPv4 of my network adapter
  • Resetting all caches, releasing the address and renewing the lease. I've also reset the winsock catalog, the full listing would be:

    ipconfig /flushdns
    ipconfig /registerdns
    ipconfig /release
    ipconfig /renew
    netsh winsock reset catalog
    netsh int ipv4 reset reset.log
    netsh int ipv6 reset reset.log
    
  • Disabling smart name resolution / parallel requests. This is as it's described here. Important thing would be that the mentioned keys didn't exist and therefore I've added them
  • Disabling DNS Client Service (via services.msc). Disabling / enabling IPv6 in the network adapter options. These actions don't change anything.
  • Adding gpedit.msc console to the system manually (I have Home edition which doesn't have it by default) hoping to enable "Turn off smart multi-homed name resolution" there. But in the "Administrative Templates" > "Network" > "DNS Client" I do not have this option at all and more - all options which I have there have "Not configured" state.
  • Restoring default "Internet Settings". It's "Solution 5" from here.
  • Using anti-virus software to perform full scanning in case DNS is throttling me as I might have some malware. Nothing was found.

Of course I've rebooted the machine after mentioned modifications. It worth mentioning that the issues started to happen not long ago - same machine was working just fine without troubles and nothing was changed manually - but I believe issues started to occur after latest Windows update (not 100% sure about that).

I've also checked that it's not some firewall-related issues by disabling firewall completely and still observing same issue after some time.

Versions

  • System: x64
  • OS: Windows 10 Home 1607 / Build 14393.351

ipconfig /all (here I'm using my ISP LAN router as the DNS server)

Windows IP Configuration

   Host Name . . . . . . . . . . . . : Home
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : hitronhub.home

Ethernet adapter Ethernet:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
   Physical Address. . . . . . . . . : F0-79-59-81-96-65
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Local Area Connection* 3:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
   Physical Address. . . . . . . . . : E8-B1-FC-6B-AC-75
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Ethernet adapter VPN - VPN Client:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : VPN Client Adapter - VPN
   Physical Address. . . . . . . . . : 00-AD-D0-34-8B-00
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter WiFi:

   Connection-specific DNS Suffix  . : hitronhub.home
   Description . . . . . . . . . . . : Intel(R) Dual Band Wireless-AC 7260
   Physical Address. . . . . . . . . : E8-B1-FC-6B-AC-74
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.0.10(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Wednesday, November 9, 2016 7:40:10 PM
   Lease Expires . . . . . . . . . . : Wednesday, November 16, 2016 7:40:09 PM
   Default Gateway . . . . . . . . . : 192.168.0.1
   DHCP Server . . . . . . . . . . . : 192.168.0.1
   DNS Servers . . . . . . . . . . . : 192.168.0.1
   NetBIOS over Tcpip. . . . . . . . : Enabled
asked Nov 10, 2016 by Alma Do  

You are obviously using Google's public DNS server, so have you already tried utilizing a different source for DNS resolution to see if the problem persists?

Yes, I've tried ISP-provided DNS both statically and with automatic settings resolution (in the adapter settings for IPv4)

I assumed that you had probably already done that. It may be a good idea to edit your question and add that information to your section titled What I've already tried.

2 Answers

0 like 0 dislike
 
Best answer

This answer summarizes the research done by the poster and myself to analyze and fix the problem.

I describe here the sequence of actions that will (probably) fix the problem, followed by my theory why it works.

Step 1 : Stop the the DNS Client service

  1. In the Start Menu of Windows, type services and click to run on Services
  2. Find the service named DNS Client
  3. Right-click the service and do Stop to stop it

Step 2 : Do network reset

  1. In the Start Menu of Windows, click on Settings
  2. Click on Network & Internet
  3. Click on Status
  4. Click Network reset
  5. Click Yes

A detailed description can be found in this article. I believe that Network reset is probably equivalent to doing all the re-initialization commands listed above in the post.

Step 3 : Restart the DNS Client service

Repeat Step 1, but do Start instead to restart the service.
If the problem still occurs, try to reboot Windows.

My theory as to why it works

Apparently some bad setting related to the DNS Client service was introduced into Windows, which caused DNS to malfunction. Network reset is normally sufficient to bring the network to a known state, but in this case the bad setting could not be reset while the service was running. So the DNS Client service needed to be stopped for the Network reset to successfully reinitialize all the DNS settings.

answered Nov 10, 2016 by harrymc  
0 like 0 dislike
Had same issue,

from what I have tested and read, you cant disable smart name resolution and parallel requests through registry in Windows 10, these registry edits refer to Windows 8 only.

You need to enable "Turn off smart multi-homed name resolution" in Group Policy Editor (gpedit.msc)

As you have home version, you need to manually install policy editor first, takes little tweaking.
answered Nov 10, 2016 by Batchman  
...