I was initially not able to get the DNS Server changed on my router, so I set up the Pihole as the DHCP Server as well and turned off DHCP on the router.
Based on what I can see in the console, queries are being logged and there are active Clients. but I don't see any ad requests being blocked, and websites are still displaying ads.
[i] Debug script running in automated mode
* Using curl for transmission.
* curl failed, contact Pi-hole support for assistance.
* Error message: curl: (6) Could not resolve host: tricorder.pi-hole.net
[✗] There was an error uploading your debug log.
Please try again or contact the Pi-hole team for assistance.
A local copy of the debug log can be found at: /var/log/pihole/pihole_debug.log
Some manually copied excerpts from log:
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✗] Failed to resolve 961.com on lo (127.0.0.1)
[✗] Failed to resolve 961.com on eth0 (192.168.0.80)
[✗] Failed to resolve 961.com on eth0 (192.168.0.243)
[✓] doubleclick.com is 142.250.65.238 via a remote, public DNS server (8.8.8.8)
*** [ DIAGNOSING ]: Name resolution (IPv6) using a random blocked domain and a known ad-serving domain
[✗] Failed to resolve edge.ayboll.com on lo (::1)
[✓] edge.ayboll.com is :: on eth0 (fdf5:3a70:da02:d639:c5dc:2b7b:43f0:f42e)
[✗] Failed to resolve edge.ayboll.com on eth0 (fe80::18a1:78b3:b792:e6c6)
[✗] Failed to resolve doubleclick.com via a remote, public DNS server (2001:4860:4860::8888)
Debug log removed by moderator
Not sure if it's related, but I am unable to finish a sudo apt get update on the Pi itself.
This percentage doesn't mean Pi-hole is blocking 2.5% of all ads.
This means Pi-hole has blocked 2.5% of all DNS queries it received.
Blocking 100% of the queries would mean no internet at all. Most queries are not ads.
Did you intend to have two different IP addresses assigned to the eth0 interface on your Pi?
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✗] Failed to resolve 961.com on lo (127.0.0.1)
[✗] Failed to resolve 961.com on eth0 (192.168.0.80)
[✗] Failed to resolve 961.com on eth0 (192.168.0.243)
[✓] doubleclick.com is 142.250.65.238 via a remote, public DNS server (8.8.8.8)
[2023-12-15 08:15:11.305 29198M] WARNING in dnsmasq core: not giving name raspberrypi.lan to the DHCP lease of 192.168.0.243 because the name exists in /etc/hosts with address 127.0.1.1
[2023-12-15 08:15:35.475 29198M] WARNING in dnsmasq core: not giving name raspberrypi to the DHCP lease of 192.168.0.243 because the name exists in /etc/hosts with address 127.0.1.1
Your Pi-hole instance isn't currently blocking anything.
-----tail of FTL.log------
[2023-12-15 08:04:01.048 29198/T29214] WARNING: Storing queries in long-term database failed: database is locked
[2023-12-15 08:04:01.048 29198/T29214] Keeping queries in memory for later new attempt
[2023-12-15 08:04:01.064 29198/T29214] SQLite3 message: database is locked in "DELETE FROM network_addresses WHERE lastSeen < 1671109441;" (5)
[2023-12-15 08:04:01.064 29198/T29214] ERROR: SQL query "DELETE FROM network_addresses WHERE lastSeen < 1671109441;" failed: database is locked (SQLITE_BUSY)
What is this nameserver? It does not appear to be responding:
-rw-r--r-- 1 root root 66 Dec 15 07:47 /etc/resolv.conf
search lan
nameserver 192.168.0.239
*** [ DIAGNOSING ]: Operating system
[i] Distro: Debian
[i] Version: 12
[✗] dig return code: 10
[✗] dig response: dig: couldn't get address for 'ns1.pi-hole.net': failure
[✗] Error: dig command failed - Unable to check OS
