Pi-hole DNS seems to be working, but not blocking any ads (using Podman/Docker on UDM router)

Help Community Help
1

The issue I am facing:

  • When I go to the pi-hole Dashboard, I can see 100k domains in the block list, but 0 queries that have been blocked.
  • Additionally, the client-list graph only has 2 clients listed: localhost (which I think is the pi-hole itself) and 192.168.99.1 (which is the dns VLAN’s Gateway IP)
  • I don’t seem to be blocking any domains from my Macbook, which is connected to 192.168.0.244 and is using the pi-hole as the name server (192.168.99.3). And my Macbook’s IP is not showing up on the client-list graph on the dashboard.
  • In the query log, I can’t see any queries that would reflect my browsing history (e.g. theage.com.au). Instead I see queries related to my router (e.g. ping.ubnt.com), the pi-hole (reading the adlist URL from github), and my local domain name

In summary, it seems like pi-hole is working as a DNS correctly, but devices on my network are not querying it properly? It’s really odd. I’m not sure if the VLAN setup is interfering in the normal operation of pi-hole, either.

Details about my system:

  • Pi-hole on my router (UDM) with IP address 192.168.99.3 (which is on it’s own “dns” VLAN 192.168.99.0/24), inside a Docker container (described here)
  • Pi-hole uses Cloudflare for upstream DNS resolution
  • Router has name server set to 192.169.99.3 for the main LAN (192.168.0.0/24)
  • Name resolution is working for all devices on the network

What I have changed since installing Pi-hole:

Nothing

Debug token is: https://tricorder.pi-hole.net/NKrkasdG/

2

From your debug log, no apparent interface for the Pi-hole:

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] www.fit-poradnik.pl is 0.0.0.0 on lo (127.0.0.1)
[✓] No IPv4 address available on eth0@if183

   PIHOLE_INTERFACE=eth0

[✓] IPv4 address(es) bound to the eth0 interface:
    192.168.99.3/24

What provisions in your VLAN management have you made to pass DNS traffic between VLANs?

3

Pi-hole is installed inside a Docker container (as described here). I'm not very familiar with Docker or Pi-hole, but because there is a "✓" next to those items, doesn't that mean there is no problem with that configuration?

I've made no provisions in the VLAN management to pass DNS traffic, other than not enabling "Device isolation" on both the main LAN and the "dns" VLAN. I'm using a Ubiquiti Dream Machine as the router, and I haven't setup firewall rules explictly before.

4

I've just tried setting up a local Docker instance (on my computer) according to GitHub - pi-hole/docker-pi-hole: Pi-hole in a docker container , and can see that dig @localhost google.com queries are showing up in the local-pi-hole query log. So it must be something to do with the VLAN setup / router setup. I'm going to try re-installing this on my "main" network instead of on a VLAN, and see what happens (in lieu of other advice)/

5

Facing the same issue. Pi-Hole has been running fine for a long time, but stopped blocking ads since recently. Haven't changes anything on the network or router settings.
Any solutions that were identified in the meantime?

6

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