Please follow the below template, it will help us to help you!
Expected Behaviour:
LAN devices should use the device for filtering
Actual Behaviour:
Installed fine, system is active, no queries
Debug Token:
cyesffpey4
Have you specified the device of the Pi as your DNS on your clients?
There's no way for them to pick it up unless specified ...
Yes, I have set the primary dns in my router to the static ip of my pi, with a secondary to 1.1.1.1 as a backup.
When using a secondary DNS queries will slip though it (the secondary DNS does NOT kick in ONLY when DNS1 has an outage).
Run a nslookup flurry.com on a client and the same command on the pi-hole device.
What is the output ?
I didnt realize that. let me issue that lookup
This looks good. You should see a blocked entry in your query log now.
What about the same command executed on a client device (computer).
same thing on a client device, and unfortunately nothing on the blocked. i did also remove secondary dns entry too.
Based on the above nslookup, the query was intercepted and router to the raspberry pi.
Your web interface shows no queries ?
Try clearing cache and cookies.
It should show.
What's the output of pihole -v and dnsmasq -v ?
pihole -v
Pi-hole version is v3.2.1 (Latest: v3.3.1)
AdminLTE version is v3.2.1 (Latest: v3.3)
FTL version is v3.0 (Latest: v3.0)
Dnsmasq version 2.72 Copyright (c) 2000-2014 Simon Kelley
Compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect
This software comes with ABSOLUTELY NO WARRANTY.
Dnsmasq is free software, and you are welcome to redistribute it
under the terms of the GNU General Public License, version 2 or 3.
what about curl http://192.168.7.15/admin/api.php
{"domains_being_blocked":122096,"dns_queries_today":0,"ads_blocked_today":0,"ads_percentage_today":0,"unique_domains":0,"queries_forwarded":0,"queries_cached":0,"clients_ever_seen":0,"unique_clients":0,"status":"enabled"}
what happens when you try to open flurry.com on the device? Do you get a Pi-hole splash page like this:
Interesting, i receive a blocked message just as you show, however the dashboard still shows 0.
Tried this via gui on the pi, and a windows client with the same result.
Ok. I think this will fix your issue:
Try it in one line:
sudo service pihole-FTL stop && sudo mv /etc/pihole/pihole-FTL.db /etc/pihole/pihole-FTL.db.old && sudo service pihole-FTL start
Back online, but still 0's in the dashboard.
I thought we had it that time =)