Initially thought this might be to do with the fact I hadn't updated in a long time but this persists after updating. Rebooted both router and PiHole, no effect.
This has worked prior to this.
Also, https://blockads.fivefilters.org/?pihole tells me 'no adblocking detected'.
Expected Behaviour:
Queries blocked and percentage blocked increments when browsing around the internet.
Links from blocklist can still be accessed (example: I can browse to https://doubleclick.com, which should be blocked).
Actual Behaviour:
Queries blocked is always 0. Percentage blocked is always 0.0%.
Links from blocklist should not resolve.
Also, when running an nslookup on something that I know is on blacklist (adclick.g.doubleclick.net in the screengrab below) it seems to resolve still, with 'non-authoritative answer' (I don't know whether that's correct or not)
I doesn't look like you have IPv6 connectivity working:
*** [ DIAGNOSING ]: Name resolution (IPv6) using a random blocked domain and a known ad-serving domain
[✓] santaskey2recovery.com is via localhost (::1)
[✗] Failed to resolve santaskey2recovery.com via Pi-hole (fdec:40c7:7fd4:0:387f:1fbb:39a6:1421)
[✗] Failed to resolve doubleclick.com via a remote, public DNS server (2001:4860:4860::8888)
And indeed there are no blocks registered:
[2020-12-12 13:57:00.236 20139M] Imported 100288 queries from the long-term database
[2020-12-12 13:57:00.238 20139M] -> Total DNS queries: 100288
[2020-12-12 13:57:00.239 20139M] -> Cached DNS queries: 4675
[2020-12-12 13:57:00.239 20139M] -> Forwarded DNS queries: 95447
[2020-12-12 13:57:00.239 20139M] -> Blocked DNS queries: 0
[2020-12-12 13:57:00.239 20139M] -> Unknown DNS queries: 28
[2020-12-12 13:57:00.239 20139M] -> Unique domains: 2382
[2020-12-12 13:57:00.239 20139M] -> Unique clients: 20
[2020-12-12 13:57:00.240 20139M] -> Known forward destinations: 2
But you gave Pi-hole and IPv4 address inside the lease range, so that needs to be fixed. A DHCP server should not include it's own IP address in the range.
DHCPv6 is probably broken with the previous output showing that IPv6 is not working on the host.
There's also a line in your /etc/dnsmasq.d/01-pihole.conf that I've never seen before.
So trying to be smart I actually seem to have dug myself into a bit of a hole:
First of all, I've enabled IPv6 on router side. This at least did something, as I saw some blocks coming in (queries blocked: 167. Percentage blocked: 0.2%).
I then figured I'd run pihole -r so I could change the IP address to 192.168.0.2 and make it easy on myself to change the DHCP range. However, now PiHole is no longer even accessible on IPv4, I get a "site can't be reached" message. I can access it with my IPv6 IP address though. As a side effect that does seem to have gotten rid of the line in /etc/dnsmasq.d/01-pihole.conf, but it also defined 2 wlan0 interfaces in /etc/dhcpcd.conf. One with the old IP (192.168.0.48, the other with the new 192.168.0.2). However, even after uncommenting the old and rebooting, I am still not able to browse to the GUI using IPv4. Interestingly enough, uncommenting the old and commenting the new at least enables me to browse it via IPv4 again. I don't know though whether there's any other duplicate information or if the changes I made are fine. With the 192.168.0.2 address I also couldn't run pihole -r to resolve it as the network was unreachable.
I did upload a new debug log (https://tricorder.pi-hole.net/wih9gcmjp1), but the above does mean the DHCP server's IP is still included in the range... What would you recommend in terms of resolving that?
And in terms of no blocks registered - the dashboard there's 470k+ domains on the blocklists, so I'm a bit confused why that's the case?
