Ads should be getting blocked
Ads are not getting blocked. No queries on dashboard.
Pi-hole is acting as the dchp server, with the routers dchp server disabled, and can see all devices on the network.I'm not very experienced in this realm so if im missing a simple solution i apologise. Any help is appreciated.
Your debug log shows that Pi-Hole can resolve received DNS requests, but has received none in the last 24 hours.
After you made the DHCP server change, did you reboot the router and renew the DHCP lease on all clients?
From a connected client with a command prompt or terminal, run the following commands and post the output:
nslookup pi.hole
nslookup pi.hole 192.168.1.45
Yes i rebooted the router and renewed the dhcp lease on all clients.
nslookup pi.hole
Server: zo
Address: 192.168.1.45
Name: pi.hole
Addresses: 2605:6000:1b07:407a:7cfa:69f4:5174:a9fe
192.168.1.45
nslookup pi.hole 192.168.1.45
Server: zo
Address: 192.168.1.45
Name: pi.hole
Addresses: 2605:6000:1b07:407a:7cfa:69f4:5174:a9fe
192.168.1.45
The output of these commands shows that the client is using Pi-Hole as the DNS resolver. Let's see if queries are just not making it into the dashboard.
From the Pi terminal run the following commands (no need to post the results, we just want to get some activity into the log)
dig cbc.com
dig abc.com
dig nbc.com
After those run, then what is the output of the following command:
echo ">stats" | nc localhost 4711
sudo grep bc.com /var/log/pihole.log
$ echo ">stats" | nc localhost 4711
domains_being_blocked 1476955
dns_queries_today 0
ads_blocked_today 0
ads_percentage_today 0.000000
unique_domains 0
queries_forwarded 0
queries_cached 0
clients_ever_seen 0
unique_clients 0
dns_queries_all_types 0
reply_NODATA 0
reply_NXDOMAIN 0
reply_CNAME 0
reply_IP 0
privacy_level 4
status enabled
---EOM---
$ sudo grep bc.com /var/log/pihole.log
last one had to be screenshotted cause new users can only post 5 links
Now let's try one more step. We're going to live tail the pihole log at the same time we load a know ad-infested page on a browser on the same client that you verified was using Pi-Hole for DNS.
Run pihole -t from the Pi terminal.
Then, load cnn.com from the browser. You should see a burst of activity in the Pi-Hole log and no ads on the cnn page. For comparison purposes, this is just the first of what I see in the Pi-Hole log when I load that site:
Oct 9 22:08:16 dnsmasq[25543]: query[A] cnn.com from 192.168.0.135
Oct 9 22:08:16 dnsmasq[25543]: forwarded cnn.com to 127.0.0.1
Oct 9 22:08:16 dnsmasq[25543]: reply cnn.com is 151.101.65.67
Oct 9 22:08:16 dnsmasq[25543]: reply cnn.com is 151.101.129.67
Oct 9 22:08:16 dnsmasq[25543]: reply cnn.com is 151.101.1.67
Oct 9 22:08:16 dnsmasq[25543]: reply cnn.com is 151.101.193.67
Oct 9 22:08:16 dnsmasq[25543]: query[A] www.cnn.com from 192.168.0.135
Oct 9 22:08:16 dnsmasq[25543]: forwarded www.cnn.com to 127.0.0.1
Oct 9 22:08:16 dnsmasq[25543]: reply www.cnn.com is <CNAME>
Oct 9 22:08:16 dnsmasq[25543]: reply turner-tls.map.fastly.net is 151.101.185.67
Oct 9 22:08:16 dnsmasq[25543]: query[A] cdn.cnn.com from 192.168.0.135
Oct 9 22:08:16 dnsmasq[25543]: forwarded cdn.cnn.com to 127.0.0.1
Oct 9 22:08:16 dnsmasq[25543]: query[A] www.googletagservices.com from 192.168.0.135
Oct 9 22:08:16 dnsmasq[25543]: gravity www.googletagservices.com is 0.0.0.0
Oct 9 22:08:16 dnsmasq[25543]: query[A] c.amazon-adsystem.com from 192.168.0.135
Oct 9 22:08:16 dnsmasq[25543]: gravity c.amazon-adsystem.com is 0.0.0.0
Oct 9 22:08:16 dnsmasq[25543]: query[A] static.criteo.net from 192.168.0.135
Oct 9 22:08:16 dnsmasq[25543]: gravity static.criteo.net is 0.0.0.0
Oct 9 22:08:16 dnsmasq[25543]: query[A] www.i.cdn.cnn.com from 192.168.0.135
Oct 9 22:08:16 dnsmasq[25543]: forwarded www.i.cdn.cnn.com to 127.0.0.1
Oct 9 22:08:16 dnsmasq[25543]: query[A] agility.cnn.com from 192.168.0.135
Oct 9 22:08:16 dnsmasq[25543]: forwarded agility.cnn.com to 127.0.0.1
Oct 9 22:08:16 dnsmasq[25543]: query[A] amplify.outbrain.com from 192.168.0.135
Oct 9 22:08:16 dnsmasq[25543]: gravity amplify.outbrain.com is 0.0.0.0
Oct 9 22:08:16 dnsmasq[25543]: query[A] cdn.cookielaw.org from 192.168.0.135
Oct 9 22:08:16 dnsmasq[25543]: forwarded cdn.cookielaw.org to 127.0.0.1
before even typing in cnn.com i was immediately flooded with traffic
heres what it looked like immediately after loading cnn.com
there do not appear to be ads on cnn.com
i should probably also mention that sites like youtube.com still have ads and the dashboard still shows 0 queries.
We have established that the Pi-Hole is blocking domains as intended. The example of cnn.com is conclusive. You will continue to see ads on YouTube (and Facebook and some others) since they serve the ads from the same domains as the content. If you block those domains, you lose your content.
Looking over your debug log once again, I see that your privacy level is set to 4 - this accounts for the lack of logging. You have disabled all logging and statistics. If you want the query log and stats, you will need to select a lower privacy level (0, 1 or 2).
thanks for your help
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.
