Ads are not blocked.

#1

Hello,

Just installed Pi-hole on a Pi Zero W.
Pi-Hole admin console is reachable and I can connect, but it seems no ads are blocked.
Setup on the router seems correct, LAN DNS is set to Pi-hole’s IP: 192.168.1.2
pihole -t command shows only connections from 127.0.0.1, as the LAN uses 192.168.1.x
Debug token is: bmam6mwr79

Thanks.

0 Likes

#2

Your debug log shows that Pi-Hole is working properly, responding to DNS queries.

This section tests Pi-Hole from the loopback address of the Pi and from its LAN IP, and verifies that Pi-Hole can reach an upstream DNS server.

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] ad.doubleclick.net.34923.9239.302br.net is 0.0.0.0 via localhost (127.0.0.1)
[✓] ad.doubleclick.net.34923.9239.302br.net is 0.0.0.0 via Pi-hole (192.168.1.2)
[✓] doubleclick.com is 172.217.16.110 via a remote, public DNS server (8.8.8.8)

For the client on which are seeing ads, are you seeing matching client activity in Pi-Hole when you tail the Pi-Hole log at /var/log/pihole.log. For example, if you load cnn.com, you should see a query for cnn.com in the pihole log, followed by queries for a number of other domains for that web site.

This indicates that your clients are not sending DNS queries through Pi-Hole.

0 Likes

#3

No matching activity on pihole.log:

Feb 15 15:18:01 dnsmasq[13068]: started, version pi-hole-2.80 cachesize 10000
Feb 15 15:18:01 dnsmasq[13068]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth DNSSEC loop-detect inotify dumpfile
Feb 15 15:18:01 dnsmasq[13068]: using nameserver 8.8.4.4#53
Feb 15 15:18:01 dnsmasq[13068]: using nameserver 8.8.8.8#53
Feb 15 15:18:01 dnsmasq[13068]: read /etc/hosts - 5 addresses
Feb 15 15:18:01 dnsmasq[13068]: failed to load names from /etc/pihole/local.list: No such file or directory
Feb 15 15:18:01 dnsmasq[13068]: failed to load names from /etc/pihole/black.list: No such file or directory
Feb 15 15:18:01 dnsmasq[13068]: failed to load names from /etc/pihole/gravity.list: No such file or directory
Feb 15 15:18:02 dnsmasq[13068]: query[AAAA] raw.githubusercontent.com from 127.0.0.1
Feb 15 15:18:02 dnsmasq[13068]: forwarded raw.githubusercontent.com to 8.8.4.4
Feb 15 15:18:02 dnsmasq[13068]: forwarded raw.githubusercontent.com to 8.8.8.8
Feb 15 15:18:02 dnsmasq[13068]: reply raw.githubusercontent.com is <CNAME>
Feb 15 15:18:02 dnsmasq[13068]: reply github.map.fastly.net is NODATA-IPv6
Feb 15 15:18:02 dnsmasq[13068]: query[A] raw.githubusercontent.com from 127.0.0.1
Feb 15 15:18:02 dnsmasq[13068]: cached raw.githubusercontent.com is <CNAME>
Feb 15 15:18:02 dnsmasq[13068]: forwarded raw.githubusercontent.com to 8.8.4.4
Feb 15 15:18:02 dnsmasq[13068]: reply raw.githubusercontent.com is <CNAME>
Feb 15 15:18:02 dnsmasq[13068]: reply github.map.fastly.net is 151.101.16.133
Feb 15 15:18:02 dnsmasq[13068]: query[A] raw.githubusercontent.com from 127.0.0.1
Feb 15 15:18:02 dnsmasq[13068]: cached raw.githubusercontent.com is <CNAME>
Feb 15 15:18:02 dnsmasq[13068]: cached github.map.fastly.net is 151.101.16.133
Feb 15 15:18:02 dnsmasq[13068]: query[A] raw.githubusercontent.com from 127.0.0.1
Feb 15 15:18:02 dnsmasq[13068]: cached raw.githubusercontent.com is <CNAME>
Feb 15 15:18:02 dnsmasq[13068]: cached github.map.fastly.net is 151.101.16.133
Feb 15 15:18:02 dnsmasq[13068]: query[AAAA] raw.githubusercontent.com from 127.0.0.1
Feb 15 15:18:02 dnsmasq[13068]: cached raw.githubusercontent.com is <CNAME>
Feb 15 15:18:02 dnsmasq[13068]: cached github.map.fastly.net is NODATA-IPv6
Feb 15 15:18:03 dnsmasq[13068]: query[A] mirror1.malwaredomains.com from 127.0.0.1
Feb 15 15:18:03 dnsmasq[13068]: forwarded mirror1.malwaredomains.com to 8.8.4.4
Feb 15 15:18:03 dnsmasq[13068]: reply mirror1.malwaredomains.com is 74.63.222.170
Feb 15 15:18:04 dnsmasq[13068]: query[A] mirror1.malwaredomains.com from 127.0.0.1
Feb 15 15:18:04 dnsmasq[13068]: cached mirror1.malwaredomains.com is 74.63.222.170
Feb 15 15:18:04 dnsmasq[13068]: query[AAAA] mirror1.malwaredomains.com from 127.0.0.1
Feb 15 15:18:04 dnsmasq[13068]: forwarded mirror1.malwaredomains.com to 8.8.4.4
Feb 15 15:18:04 dnsmasq[13068]: reply mirror1.malwaredomains.com is NODATA-IPv6
Feb 15 15:18:06 dnsmasq[13068]: query[A] sysctl.org from 127.0.0.1
Feb 15 15:18:06 dnsmasq[13068]: forwarded sysctl.org to 8.8.4.4
Feb 15 15:18:06 dnsmasq[13068]: reply sysctl.org is 213.186.34.12
Feb 15 15:18:06 dnsmasq[13068]: query[A] sysctl.org from 127.0.0.1
Feb 15 15:18:06 dnsmasq[13068]: cached sysctl.org is 213.186.34.12
Feb 15 15:18:06 dnsmasq[13068]: query[AAAA] sysctl.org from 127.0.0.1
Feb 15 15:18:06 dnsmasq[13068]: forwarded sysctl.org to 8.8.4.4
Feb 15 15:18:07 dnsmasq[13068]: reply sysctl.org is NODATA-IPv6
Feb 15 15:18:09 dnsmasq[13068]: query[A] zeustracker.abuse.ch from 127.0.0.1
Feb 15 15:18:09 dnsmasq[13068]: forwarded zeustracker.abuse.ch to 8.8.4.4
Feb 15 15:18:09 dnsmasq[13068]: reply zeustracker.abuse.ch is <CNAME>
Feb 15 15:18:09 dnsmasq[13068]: reply p2.shared.global.fastly.net is 151.101.38.49
Feb 15 15:18:09 dnsmasq[13068]: query[A] zeustracker.abuse.ch from 127.0.0.1
Feb 15 15:18:09 dnsmasq[13068]: cached zeustracker.abuse.ch is <CNAME>
Feb 15 15:18:09 dnsmasq[13068]: cached p2.shared.global.fastly.net is 151.101.38.49
Feb 15 15:18:09 dnsmasq[13068]: query[AAAA] zeustracker.abuse.ch from 127.0.0.1
Feb 15 15:18:09 dnsmasq[13068]: cached zeustracker.abuse.ch is <CNAME>
Feb 15 15:18:09 dnsmasq[13068]: forwarded zeustracker.abuse.ch to 8.8.4.4
Feb 15 15:18:09 dnsmasq[13068]: reply zeustracker.abuse.ch is <CNAME>
Feb 15 15:18:09 dnsmasq[13068]: reply p2.shared.global.fastly.net is NODATA-IPv6
Feb 15 15:18:10 dnsmasq[13068]: query[A] s3.amazonaws.com from 127.0.0.1
Feb 15 15:18:10 dnsmasq[13068]: forwarded s3.amazonaws.com to 8.8.4.4
Feb 15 15:18:10 dnsmasq[13068]: reply s3.amazonaws.com is <CNAME>

pihole-t commands shows only:

17:22:30 dnsmasq[7110]: query[AAAA] pi-hole from 127.0.0.1
17:22:30 dnsmasq[7110]: config pi-hole is NODATA-IPv6
17:25:27 dnsmasq[7110]: query[A] pi-hole from 127.0.0.1
17:25:27 dnsmasq[7110]: /etc/pihole/local.list pi-hole is 192.168.1.2
17:25:27 dnsmasq[7110]: query[AAAA] pi-hole from 127.0.0.1
17:25:27 dnsmasq[7110]: config pi-hole is NODATA-IPv6
17:29:38 dnsmasq[7110]: query[A] pi-hole from 127.0.0.1
17:29:38 dnsmasq[7110]: /etc/pihole/local.list pi-hole is 192.168.1.2
17:29:38 dnsmasq[7110]: query[AAAA] pi-hole from 127.0.0.1
17:29:38 dnsmasq[7110]: config pi-hole is NODATA-IPv6

no matter the activity on internal network

Also, Tail pihole.log from admin console shows only:

Feb 15 17:25:27 dnsmasq[7110]: query[A] pi-hole from 127.0.0.1
Feb 15 17:25:27 dnsmasq[7110]: /etc/pihole/local.list pi-hole is 192.168.1.2
Feb 15 17:25:27 dnsmasq[7110]: query[AAAA] pi-hole from 127.0.0.1
Feb 15 17:25:27 dnsmasq[7110]: config pi-hole is NODATA-IPv6
Feb 15 17:29:38 dnsmasq[7110]: query[A] pi-hole from 127.0.0.1
Feb 15 17:29:38 dnsmasq[7110]: /etc/pihole/local.list pi-hole is 192.168.1.2
Feb 15 17:29:38 dnsmasq[7110]: query[AAAA] pi-hole from 127.0.0.1
Feb 15 17:29:38 dnsmasq[7110]: config pi-hole is NODATA-IPv6
0 Likes

#4

This is showing that your clients are not using Pi-Hole for DNS.

I would start with manually assigning Pi-Hole DNS on one client and verify that works, then work on hte router problem.

0 Likes

#8

The router the user was using (Synology RT2600), was intercepting and preventing DNS relaying within the local network. The DNS requests were always answered by the router (DNS rebind?).

He switched to an Asus router (AC56U) and the issue was resolved with it.

0 Likes

closed #11

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

0 Likes