DNS lookup fails after sleep - Windows 10

Question

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.

Answer 1

In case somenone else has landed up here after all this time - the original post goes back a few years:

I have an MSI motherboard with an AMD Ryzen 2400G CPU - note these are not compatible with Windows 11 so I am still using Windows 10 21H2. This is a Desktop PC in my home. My preferred OS is Linux but I need to keep up with Windows for work.

I am having this problem after the May 2022 update KB5013943. It failed to install. After a BSOD and removing the update using Startup Repair I could not get the DNS client to work at all and went through all the normal guff you get from Microsoft support. I also tried a System Restore with no benefit. So the DNS client was running but name resolution was not working. Spent a few hours to get to the bottom of it. Note - the LAN access was working normally.

Finally I tried something I am always doing in workplaces and that is to go to the Network card properties in Device manager where you can turn off Windows Power Management for the device and in the Advanced tab I disabled 'Energy Efficient Ethernet'. After those steps Name Resolution started working again after a reboot. But still after using sleep DNS fails on wake up. So Rebooting is needed. I am living with that.

In other words I have to give up using Sleep. I think these problems occur when Microsoft tweak power management and the network card is silenced during sleep. I am not an expert but would advise trying the steps I suggest before digging around in systems and the registry to make DNS work again or getting worried about your router.

Caveat - when the ethernet card was failing to resolve names I inserted a WiFi Dongle and this also could not use DNS. So the point at which things are getting messed up is in the Windows OS networking code and not at the device level. Looks like a tiny bit of code has been altered in the update and not fully tested.
Moan - this update was for Win10 and Win11 so as my computer is not comapatible for Win11 use I wonder if updates will now cause all sorts of problems. Possible temporary workaround - stick with 20H2. They want us to buy new computers that give MS more control over our equipment - the Apple Way or the highway it seems. Use Linux.