Xbox and Windows lose DNS ~every 2 days


#1

Please follow the below template, it will help us to help you!

Expected Behaviour:

Pi-hole works as usual as with other clients on my network

Actual Behaviour:

Xbox One and Windows 10 client occasionally lose DNS resolution, about every other day. When I reset my router, which is a Linksys router running Tomato firmware, DNS starts working again. Any thoughts what to troubleshoot next when it stops working (either on the router or possible pi-hole config)? On the Windows client I tried ipconfig /flushdns which worked one time to get things going again but now a router reset is the only thing that seems to solve the issue when it happens for both Windows and Xbox One.

I have these commonly whitelisted domains added to the pi-hole for Windows and Xbox:
https://discourse.pi-hole.net/t/commonly-whitelisted-domains/212

Also this is added to the router in the dnsmasq custom config section (192.168.1.18 is the pi-hole IP):
dhcp-option=6,192.168.1.18

FWIW, this is the same Windows client I mention in this post (where I changed NIC settings to not go to sleep): https://discourse.pi-hole.net/t/dns-timeout-failures-from-windows-10-client-after-sleeping/7692/4

Debug Token:

hgb072bvwa


#2

On the Windows client, check if it actualy receives correct IP details with below one:

ipconfig /all

The DHCP Server” and DNS Servers” section should both point to the Pi-hole IP address and Pi-hole should be the only DNS server displayed!!!

Below an example on one of my client PC’s with 10.0.0.1 being my router and 10.0.0.2 being Pi-hole with Pi-hole configured to do DHCP for my LAN:

C:\>ipconfig /all

Ethernet adapter Local Area Connection:

   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 10.0.0.11(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : woensdag 21 maart 2018 16:45:05
   Lease Expires . . . . . . . . . . : donderdag 22 maart 2018 16:45:05
   Default Gateway . . . . . . . . . : 10.0.0.1
   DHCP Server . . . . . . . . . . . : 10.0.0.2
   DNS Servers . . . . . . . . . . . : 10.0.0.2

EDIT: How have you determined that you “lose DNS resolution” ?


#3

Thank you - yes, here is the output of my ipconfig /all (below). My router and DHCP are at 192.168.1.1 and Pi-hole (DNS) is at 192.168.1.18.

I’m experiencing the issue right now (as a workaround to post this reply, I manually changed the DNS server to 8.8.8.8) - when I try to go to www.google.com using Firefox I get the error: “we can’t seem to find that site”. I can ping both the router and Pi-hole without issue.

When I try to use nslookup I get the following error:

DNS request timed out.
    timeout was 2 seconds.
Default Server:  UnKnown
Address:  192.168.1.18

Result of ipconfig /all:

Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . : lan
   Description . . . . . . . . . . . : Intel(R) Ethernet Connection (4) I219-V
   Physical Address. . . . . . . . . : F4-4D-30-6F-C0-0B
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::8d0d:98db:e9b6:e30b%5(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.51(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Wednesday, March 21, 2018 12:28:46 PM
   Lease Expires . . . . . . . . . . : Thursday, March 22, 2018 12:28:46 PM
   Default Gateway . . . . . . . . . : 192.168.1.1
   DHCP Server . . . . . . . . . . . : 192.168.1.1
   DHCPv6 IAID . . . . . . . . . . . : 267668784
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-21-45-E0-13-F4-4D-30-6F-C0-0B
   DNS Servers . . . . . . . . . . . : 192.168.1.18
   NetBIOS over Tcpip. . . . . . . . : Enabled

#4

Can you log into the Pi-hole via SSH when the DNS is down?


#5

Yes, I can login ok and also ping both the Pi-hole and router. Here is a new debug token from running pihole-d:
t603x1oxe0

Also, for reference and FWIW, here is an ipconfig /all from another windows 10 client on my network for which DNS is working (still broken on the other windows client):

Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . : lan
   Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
   Physical Address. . . . . . . . . : D4-3D-7E-28-F4-04
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::b04b:a4b0:de0e:10c2%10(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.111(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Tuesday, March 13, 2018 5:58:39 PM
   Lease Expires . . . . . . . . . . : Thursday, March 22, 2018 12:06:14 PM
   Default Gateway . . . . . . . . . : 192.168.1.1
   DHCP Server . . . . . . . . . . . : 192.168.1.1
   DHCPv6 IAID . . . . . . . . . . . : 315899262
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-5D-59-57-D4-3D-7E-28-F4-04
   DNS Servers . . . . . . . . . . . : 192.168.1.18
   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:4137:9e76:344d:1247:bc57:d036(Preferred)
   Link-local IPv6 Address . . . . . : fe80::344d:1247:bc57:d036%13(Preferred)
   Default Gateway . . . . . . . . . : ::
   DHCPv6 IAID . . . . . . . . . . . : 134217728
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-5D-59-57-D4-3D-7E-28-F4-04
   NetBIOS over Tcpip. . . . . . . . : Disabled

#6

When the DNS is down, what is the output of these commands on the Pi-hole and on the Windows client?

nslookup pi.hole
nslookup google.com
nslookup doubleclick.com

#7

Sorry for the delay -

On the Pi-hole, the results are:
192.168.1.18 (pi.hole)
216.58.193.78 (google.com)
192.168.1.18 (doubleclick.com)

On the Windows client, all results time out:
“DNS request timed out.”

Two other data points:

  1. On the xbox one, all the networking information appears correct when DNS is unavailable (when running the xbox network troubleshooter it recognizes that xbox sites can’t be resolved). The default gateway is correct however at 192.168.1.1 and DNS server at 192.168.1.18.

  2. The issue hasn’t reproduced in the past 2 days since I installed the FTL DNS beta, so it may hopefully be moot at this point. I’ll continue to monitor.


closed #8

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.