Raspberry Pi Zero W running Raspberry Pi OS Lite (Raspbian 10 Buster) on Linux 5.10.11+ kernel connected via wifi to TP-Link Archer 10 Pro router
I am located in Japan and my ISP (Docomo Hikari/OCN) provides the usual IPv4 as well as something they call V6Plus (which is apparently an IPv6 IPoE connection unique to Japan? I think it's similar to IPv4 over IPv6? I'm not really sure how it works exactly). I had attempted to install the pihole on my home network using the NEC wifi router provided by my ISP but it did not allow for setting the primary/secondary DNS on the router and other useful settings so I ended up purchasing a TP-Link Archer 10 Pro (a Japan-only model of the Archer 10 made to handle the aforementioned Japan-specific IPv6). I switched out the NEC router for the TP-Link router which allowed me to set up all the traffic to be redirected to the pihole from my router (without pointing each device to it manually) using primary/secondary DNS in the DHCP settings. However, this left my pihole from being able to connect to the new router (since the IP addresses had changed). I fixed this by popping the SD card into my linux system, manually editing the wpa_supplicant.conf file for the new SSID/pwd, and assigning the pihole a static IP in the new router's range from inside the router's admin panel. This allowed the pihole to work and blocked around 13% of all queries using the default list (including everything on speedtest.net). So far, so good but I wanted to get more out of my pihole and decided to try to implement DNS over HTTPS using cloudflared. Everything seemed to install and setup fine but did not work in practice. Not only did it not successfully implement DNS over HTTPS according to 220.127.116.11/help, my pihole was suddenly no longer blocking ads on speedtest.net. I also noticed some others ads were still getting through so I tried to add a bunch of recommended adlists to no avail. I don't now for sure whether this was the fault of a botched cloudflared install or not.
Either way, I got fed up and unplugged the Pi Zero W, wiped the SD card, and did a clean reinstall of the OS and pihole.This time it was connected to the new router from the start and all setup was done with my current network settings (no changing routers in the middle). Everything seemed to install and setup fine but, whereas the last installation of the pihole was blocking 13% of ads out of the box, this one was blocking 0% before a
pihole -d revealed that neither of the IPv6 addresses bound to the wlan0 interface matched the setupVars.conf file. I manually edited the file to change the last four digits from ":1001" to ":1002" which caused the first of the two addresses to then match. Afterwards, the pihole began to block 2% of queries... better but still far from what had worked before with no tinkering.
As far as I can tell as a complete novice, everything else in the diagnostic report is coming up as it should be but I'm getting very poor results. After a day of use it's now blocking 6%. Any ideas what could be causing this or how I can fix it?
My debug token is: https://tricorder.pi-hole.net/rgci2lpqab
Not sure if It will be useful but an
nslookup example.com returns:
Server: 18.104.22.168 Address: 22.214.171.124#53 Non-authoritative answer: Name: example.com Address: 126.96.36.199 Name: example.com Address: 2606:2800:220:1:248:1893:25c8:1946