DNS lookup fails after sleep – Windows 10

Issue

Since a few days, after sleeping my computer, all name lookups fail. This causes the browser to not load any pages. Only a restart fixes this, disabling and enabling my Wifi adapter does not. I see that a IPv6 nameserver appears in the output of ipconfig after sleeping that wasn’t there before, and this nameserver does not work…

I’m using an up to date Windows 10 Enterprise install, and am behind a Netgear JWNR2000T. I have an internet connection that does not require a login, just connect the ethernet cable that enters my house to the netgear and go. Client is configured through DHCP.

The only things that were installed around the time this started happening (2/3 days ago), are https://support.microsoft.com/en-us/kb/3140768, VS2015 update 2 and a few app updates. That does not appear to be relevant. The netgear’s firmware hasn’t been changed for a long time, is up to date, nor have I touched any settings.

Below are outputs from ipconfig, nslookup and ping, before and after sleeping. The DNS server 192.168.1.1 is my router.

Bonus question: where does the non-authoritative answer google.com -> 192.168.8.1 come from? Given the DNS query times out…

before sleeping

C:\Users\Diederick>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : DEE_LU
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Wireless LAN adapter Local Area Connection* 2:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
   Physical Address. . . . . . . . . : 4A-E2-44-F5-57-C5
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wi-Fi:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Dell Wireless 1830 802.11ac
   Physical Address. . . . . . . . . : 48-E2-44-F5-57-C5
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::981b:ae2e:c423:792e%11(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.3(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Saturday, 9 April, 2016 20:29:25
   Lease Expires . . . . . . . . . . : Sunday, 10 April, 2016 20:29:25
   Default Gateway . . . . . . . . . : 192.168.1.1
   DHCP Server . . . . . . . . . . . : 192.168.1.1
   DHCPv6 IAID . . . . . . . . . . . : 55108164
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1E-70-AC-97-48-E2-44-F5-57-C5
   DNS Servers . . . . . . . . . . . : 192.168.1.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Teredo Tunneling Pseudo-Interface:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2001:0:5ef5:79fb:10f0:26f9:a613:c376(Preferred)
   Link-local IPv6 Address . . . . . : fe80::10f0:26f9:a613:c376%19(Preferred)
   Default Gateway . . . . . . . . . : ::
   DHCPv6 IAID . . . . . . . . . . . : 318767104
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1E-70-AC-97-48-E2-44-F5-57-C5
   NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter isatap.{7B2BB6D5-6516-4FBD-BADE-DF08B3490226}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #4
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

C:\Users\Diederick>nslookup google.com
Server:  UnKnown
Address:  192.168.1.1

Non-authoritative answer:
Name:    google.com
Addresses:  2a00:1450:400f:804::200e
          83.140.66.19
          83.140.66.57
          83.140.66.34
          83.140.66.49
          83.140.66.38
          83.140.66.45
          83.140.66.59
          83.140.66.29
          83.140.66.53
          83.140.66.27
          83.140.66.42
          83.140.66.44
          83.140.66.30
          83.140.66.15
          83.140.66.23

C:\Users\Diederick>ping google.com

Pinging google.com [83.140.66.42] with 32 bytes of data:
Reply from 83.140.66.42: bytes=32 time=14ms TTL=54

after sleeping

C:\Users\Diederick>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : DEE_LU
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Wireless LAN adapter Local Area Connection* 2:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
   Physical Address. . . . . . . . . : 4A-E2-44-F5-57-C5
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wi-Fi:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Dell Wireless 1830 802.11ac
   Physical Address. . . . . . . . . : 48-E2-44-F5-57-C5
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::981b:ae2e:c423:792e%11(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.3(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Saturday, 9 April, 2016 20:29:25
   Lease Expires . . . . . . . . . . : Monday, 11 April, 2016 0:31:19
   Default Gateway . . . . . . . . . : 192.168.1.1
   DHCP Server . . . . . . . . . . . : 192.168.1.1
   DHCPv6 IAID . . . . . . . . . . . : 55108164
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1E-70-AC-97-48-E2-44-F5-57-C5
   DNS Servers . . . . . . . . . . . : fe80::ca51:95ff:fe9c:a949%11
                                       192.168.1.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Teredo Tunneling Pseudo-Interface:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{7B2BB6D5-6516-4FBD-BADE-DF08B3490226}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #4
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

C:\Users\Diederick>nslookup google.com
DNS request timed out.
    timeout was 2 seconds.
Server:  UnKnown
Address:  fe80::ca51:95ff:fe9c:a949

Non-authoritative answer:
DNS request timed out.
    timeout was 2 seconds.
Name:    google.com
Address:  192.168.8.1


C:\Users\Diederick>nslookup google.com 192.168.1.1
Server:  UnKnown
Address:  192.168.1.1

Non-authoritative answer:
Name:    google.com
Addresses:  2a00:1450:400f:803::200e
          83.140.66.53
          83.140.66.23
          83.140.66.19
          83.140.66.44
          83.140.66.15
          83.140.66.49
          83.140.66.27
          83.140.66.30
          83.140.66.38
          83.140.66.29
          83.140.66.45
          83.140.66.59
          83.140.66.34
          83.140.66.57
          83.140.66.42


C:\Users\Diederick>ping google.com

Pinging google.com [192.168.8.1] with 32 bytes of data:
Request timed out.

Solution

There could be plenty of reasons in this case. Some people reported problems with network after installing 1511 update.

You can try to follow steps described on Microsoft webpage: http://windows.microsoft.com/en-us/windows-10/fix-network-connection-issues

To the time you find better solution to your specific problem I suggest you a workaround:

To open Network Connections press [Windows] + S and type:

ncpa.cpl

Right click on your network connection and goto Properties.

Click the Networking tab. Under This connection uses the following items, click either Internet Protocol Version 4 (TCP/IPv4) or Internet Protocol Version 6 (TCP/IPv6), and then click Properties.

Click Use the following DNS server addresses, and then, in the Preferred DNS server and Alternate DNS server boxes, type the addresses of the primary and secondary DNS servers.
For example: 8.8.8.8 and 8.8.4.4 (Google DNS – IPv4) or any other DNS server adress http://pcsupport.about.com/od/tipstricks/a/free-public-dns-servers.htm

UPDATE

Sorry to hear that. I must say that it is unusual that DNS server adresses are not remembered. They should stay untouched after reboot or after connected to another wireless network so the problem must be in your system. This also may indicide that your computer is infected.

If previus steps didn’t help, you can also try following things:

Firstly, make sure that there is nothing in your system that could change DNS adress. Go to Network Connections again and click the Networking tab. Under This connection uses the following items double check every item. By default you should see something like this:
Connection Properties Windows

If you don’t recognise some item in your OS try disabling it and check if the problem is solved.

Probably you already did this, but I have to ask: Did you update drivers? Here is the link: http://www.dell.com/support/home/us/en/19/Drivers/DriversDetails?driverId=JKRJ9

Try disabling power saving for wireless (more described here: http://en.community.dell.com/support-forums/laptop/f/3518/t/19661197)

If you really need this done and no matter how you can create script to restore your dns settings and set it in Task Scheduler to run after system wake up or after reboot. However making a script running after sleep could be difficult. Here is the guide to create a script: https://superuser.com/questions/463096/change-dns-with-script

Answered By – Sebastian

This Answer collected from stackoverflow, is licensed under cc by-sa 2.5 , cc by-sa 3.0 and cc by-sa 4.0

Leave a Reply

(*) Required, Your email will not be published