To clarify, this is running on a raspberry pi 3b+. For now, I only want ONE client (my desktop PC) to go through pihole for DNS resolution, not my entire network. Therefore, I have not pointed my router to the pihole, but rather only my desktop win10 client. In my ip4 settings I add my pihole ip address (static through router) but it won't resolve DNS.
I do see in the debug that the networking says it can't find any ip addresses and the gateway isn't responding.
@Jawbone Sorry, as a regular forum member I'm not able to read your Pi-hole diagnostics report ... so, if you don't mind, start a SSH session to your Pi-hole and try these two commands and post back the results:
On your Windows 10 client, how is the TCP/IP v4 protocol configured?
Also, after setting the Windows 10 client DNS server to the Pi-Hole, could you try and clear the DNS cache on the W10 by opening command promt as administrator and run:
I go to the ipv4 settings, hit advanced, and add my pi address to the DNS server (as primary, alternate is blank)
I ran CMD as admin, ran that flush cmd and it said cleared DNS cache successfully. Still same symptoms, however. I am able to post this while it is still having the issues though, so I know I still have network connectivity, just issues resolving DNS
The only entries on the query log on the pi-hole admin page is from the pi-hole itself presumably since the client says "localhost" otherwise no other entries.
This is my admin page on pi-hole. This is the correct IP address for my desktop that I'm having issues with so the DNS requests from my desktop aren't even making it to the pihole for some reason
@Jawbone One thing I see is that the interface shows as wlan0, Is your Pi-hole connected to the network by Ethernet or by wireless? If the latter, try connecting by Ethernet. On the Pi-hole Settings > DNS tab what is your Interface Listening Behavior set to?
Let's try two more commands: dig pi-hole.net @127.0.0.1 -p 5353 << this should test the Pi-hole DNS from the perspective of the Pi-hole. Success is a DNS ANSWER with an IP address
dig pi-hole.net @ -p 53 . << this should test the Pi-hole from your PC's perspective. Again, success is a DNS ANSWER with the same IP address as the first test.
So oddly enough I just came across those settings and was replying when I saw yours come across!
I changed to "Listen on all interfaces" and it works!! It does not work if it only listens on eth0. Why should it only be on this setting? Is it a security issue? My pi-hole is connected wifi (eth0) and my desktop is lan to my router.
The first command returns this:
pi@raspberrypi:~ $ dig pi-hole.net @127.0.0.1 -p 5353
; <<>> DiG 9.10.3-P4-Raspbian <<>> pi-hole.net @127.0.0.1 -p 5353
;; global options: +cmd
;; connection timed out; no servers could be reached
The second command i think i entered wrong as it returns:
pi@raspberrypi:~ $ dig pi-hole.net @ -p 53
dig: couldn't get address for '': not found
Ok, that's what I would expect for the first test. On the second test, you need to enter the IP address of your Pi-hole device. Something like this: dig pi-hole.net @XXX.XXX.XXX.XXX -p 53
Ok, those results are telling us that your Pi-hole is working from the perspective of the Pi-hole. Now run the exact same command from a Command Prompt window on your Windows client.
Also I am thinking perhaps I want to reconfigure my pi-hole to be LAN anyway, just better connectivity I suppose. So this might all be moot since I think the discrepancy was between the pihole being configured to ETH and my desktop being LAN. Why is it bad to have the listen option on all?
dig is the BIND DNS lookup utility available on Macs and Linux boxes. I'm not sure what the equivalent command for Windows would be. I do know that BIND has a dig utility for Windows that may work for this. Maybe someone who is more Windows-literate may chime in to help.
The bottom line is that it appears that Pi-hole is working ... just not from this PC.
