A lot of Queries, but 0% getting blocked

For a long time I was happy to run pihole standalone but now I want to run multiple applications in a container.
I installed pihole via docker/portainer on my rpi 3 using this link https://homenetworkguy.com/how-to/install-pihole-on-raspberry-pi-with-docker-and-portainer/
I have the following settings in portainer:
network ports:
53/tcp
80/tcp
443/tcp
53/udp
volume:
/etc/dnsmasq.d
/home/pi/pihole/dnsmasq.d
/etc/pihole
/home/pi/pihole/pihole
network:
network: bridge
hostname: rpi3
env:
TZ: europe/amsterdam
DNS1: 192.168.0.155
DNS2: no
WEBPASSWORD: xxxxxxxxx
Restart policy:
unless stopped

No error messages in portainer but unfortunately 0% blocked :smirk:



pihole_debug.log.txt (7.0 KB)

Does this correlate with you seeing ads on some clients?

Your Pi-hole seems to be operational.

I can think of two possible explanations:
(1) Only some of your clients are using Pi-hole for DNS, and those that do are simply not requesting any blocked domains.

From a client that doesn't seem to be filtered, what's the output of

nslookup pi.hole
nslookup flurry.com

(2) You are using Pi-hole's Group Management, and most clients are in a group that applies little or no filtering.

Check your Pi-hole's Group Management if that is the case.

Does this correlate with you seeing ads on some clients? Yes

All clients have this problem!

nslookup pi.hole
Server: 127.0.0.1
Address: 127.0.0.1#53

Name: pi.hole
Address: 0.0.0.0
;; connection timed out; no servers could be reached

nslookup flurry.com
Server: 127.0.0.1
Address: 127.0.0.1#53

Name: flurry.com
Address: 0.0.0.0
Name: flurry.com
Address: ::

I haven't done anything with the group management

Please run nslookup on the clients which have ad problems, not on the server.

It is btw not advised that the Pi-hole host resolves queries for itself, but better to make it use an upstream DNS directly instead. You usually don't browse the web from a server :wink:. But probably the docker container still ships with this setup, not sure.

Excuse me but I hope this is what you mean.


This client is not using Pi-hole for DNS. It is using a different DNS.