Pi-hole stopped working from Client

Help
1

I tested pihole on a vm and got it working - or so I thought - with DNS-Over-HTTPS on Pi-hole.
I then installed pihole DNS-Over-HTTPS on Pi-hole on an old lenovo laptop and removed the pihole vm. It looked like pihole was working from the client as I could see the client ip on the client list on the pihole dashboard.

Since I was going out of town for a week I shut down pihole as well as the client PC. Upon return I booted up pihole the client and even the router. However the client can now not get pihole to do any dns queries although everything works fine from the pihole itself. I can ping 8.8.8.8 for example from the client but I cannot reach google.com.

I tried restarting the systemd services:
sudo systemctl enable cloudflared
sudo systemctl start cloudflared
sudo systemctl status cloudflared

The command dig @127.0.0.1 -p 5053 google.com looks good as well but that is being generated from the pihole which again, works just fine.

2

If you run nslookup (or dig) pi.hole, do you get the IP address of the Pi-Hole?

And can you ping the Pi-Hole from a client? ping -c5 pi.hole

Also, run a debug log, upload it and post the token. That may avoid some back and forth questions.

3

I ran the first two commands - first with 1.1.1.1 set as my DNS in the client and got:

nslookup (or dig) pi.hole - Server: 127.0.0.53
Address 127.0.0.53#53
** server can't find pi.hole NXDOMAIN

ping -c5 pi.hole - ping pi.hole: Name or service not known

[✓] Your debug token is: 99fhvcm06e

6

Your debug log shows Pi-hole is resolving DNS as expected:

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] www.pc-breach-1n6w3h.online is 0.0.0.0 via localhost (127.0.0.1)
[✓] www.pc-breach-1n6w3h.online is 0.0.0.0 via Pi-hole (192.168.46.101)
[✓] doubleclick.com is 216.58.218.238 via a remote, public DNS server (8.8.8.8)

And is working for one other client (which could be localhost):

[2018-10-16 15:52:34.360] Imported 620 queries from the long-term database
   [2018-10-16 15:52:34.360]  -> Total DNS queries: 620
   [2018-10-16 15:52:34.360]  -> Cached DNS queries: 101
   [2018-10-16 15:52:34.360]  -> Forwarded DNS queries: 373
   [2018-10-16 15:52:34.360]  -> Exactly blocked DNS queries: 146
   [2018-10-16 15:52:34.360]  -> Unknown DNS queries: 0
   [2018-10-16 15:52:34.360]  -> Unique domains: 95
   [2018-10-16 15:52:34.360]  -> Unique clients: 1
   [2018-10-16 15:52:34.360]  -> Known forward destinations: 1

From a client, run this command to see if the client can connect to the Pi-Hole DNS via the Pi-Hole IP.

dig pi.hole @192.168.46.101

7

dig pi.hole @192.168.46.101 from the client
;; global options +cmd
;; connection timed out; no servers could be reached

The strange thing is it worked from the client when I first set it up and only broke after I shut everything down and powered everything back up upon my return from being out of town a week later.

I know it's not the IPs because when I set it up I made sure both the client as well as the pihole had static IPs and that the IPs were reserved in the router.

8

Check your router and see if the Pi is connected and at the reserved IP address.

9

Yep Pi is connected at the reserved IP

However what I now realize is that I can simply put an instance of Pi-hole on each client (4) using cloudflared DoH since I run Debian/Ubuntu based Mint as my OS. Kind of overkill but is working on this rather limited resource laptop (2 core 4G RAM) it should be no issue on the bigger rigs (i7s and AMD Bulldozer with 16G RAM)

Not the preferred solution so I will start from scratch one more time but if that does not work then I will go to plan B above.

10

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