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.
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
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):
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:
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.
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.