I have set up the pi hole, and can see that the adblock works on the raspberry pi itself (although it only scores about 68/100 on https://adblock-tester.com/). I’ve set a static IP address for the raspberry pi on my router and set it as the DNS server for my router as well. Or at least that’s what I think.
I have attached a few screen shots of my router configurations:
Your debug log shows your router to advertise two public IPv6 addresses as nameservers, besides your Pi-hole machine's private IPv4:
*** [ DIAGNOSING ]: contents of /etc
-rw-r--r-- 1 root root 130 Dec 5 12:53 /etc/resolv.conf
search home
nameserver 192.168.1.45
nameserver 2001:1620:2777:1::10
nameserver 2001:1620:2777:2::20
Your failing nslookup has used the first of those IPv6s that seem to belong to the ns10 and ns20 nameservers of init7.net.
Likely, your router is advertising your ISP's DNS server, allowing your clients to by-pass Pi-hole.
You'd have to find a way to configure your router to stop advertising its own IPv6 as DNS server, or to advertise your Pi-hole host machine's IPv6.
You'd have to consult your router's documentation sources on further details for its IPv6 configuration options.
That said, what's the contents of the DNS Query Scenario drop down list towards the bottom of your last screenshot?
Would that perhaps have an entry labeled like 'IPv4 DNS servers only'?
If so, you may want to give that a try.
I can only make some assumptions here, so you really want to check with your router's documentation and support.
My guess is that by picking 'IPv4 DNS server only', you router may just distribute IPv4 DNS nameserver addresses to your network clients.
If that's the case, you'd force dual stack clients to use only that IPv4 for DNS, while IPv4 only clients would obviously ever only been able to use IPv4 anyway. Since your devices will then only appear with their IPv4 addresses in Pi-hole's Query Log, it'll have the additional benefit of making that easier to read, and IPv4 adresses are also easier to associate with a name.
IPv4 and dual stack clients would still be able to request A as well as AAAA DNS records, so it won't limit your clients ability to talk to other servers via IPv4 or IPv6 at their own discretion.
If I'm guessing correctly, there should be no IPv6 nameservers in your /etc/resolv.conf shortly after you applied that change.
On the other hand, it could well be that DNS Query Scenario would configure how the router itself should send its DNS queries.
Again, you really want to consult your router's documentation sources on details for its IPv6 configuration options.
Okay I will try to look into it. My router is notoriously badly documented, so I'll see what I can find.
I noticed that after I disabled IPv6, my internet connection from client devices broke a few times, where I had to manually reconnect. And at some point, my router seemed to restart and went back to using a dynamic DNS. I don't know what the implications are, but it seems a bit wrong having to disable IPv6 for this to work. Am I missing something?
You could try play with those settings and check results with below?
If you want to post the output here, redact the later part of IPv6 addresses displayed and also the "link layer address" which is a MAC address!
EDIT: Oh above is for 64 bit Pi-OS!
For 32 bit and depending Pi model, you need to down the appropriate version.
For below example (armhf is 32 bit OS):
$ dpkg --print-architecture
armhf
$ arch
armv6l
You would need to wget the pihole-FTL-armv6 binary from below:
