If I do the same from my windows PC I get this output:
C:\Users\Bill>nslookup google.com
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 2601:196:180:7b10:a005:92bb:1d65:1bf4
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out
Note that the IPv6 IP in the output from the Pi is correct, while the IPv6 from the output from the Windows machine is not correct.
Strangely enough my internet is working perfectly fine. But what is up with the output from my windows machine?
Your Windows PC is using a DNS server at 2601:196:180:7b10:a005:92bb:1d65:1bf4.
What's the device at that IPv6?
Are you able to ping that address?
According to your debug log, this is not your RPi's public IPv6 address.
The debug log also shows that Pi-hole's DNS is operational for IPv6:
*** [ DIAGNOSING ]: Name resolution (IPv6) using a random blocked domain and a known ad-serving domain
[✓] smetrics.elkjop.no is :: via localhost (::1)
[✓] smetrics.elkjop.no is :: via Pi-hole (2601:[redacted}:7e)
[✓] doubleclick.com is 2607:f8b0:4006:80d::200e via a remote, public DNS server (2001:4860:4860::8888)
It could be that your router is still advertising an alternate IPv6 address (its own?) as DNS server, allowing your clients to by-pass Pi-hole.
As your nslookup ultimately times out, it is also possible that your Windows PC is still using an older, now deprecated IPv6 address.
So last night I found that IPv6 wasnt working at all with my PiHole. (as confirmed by a previous debug log)
The address in setupVars.conf was 2601:196:180:7b10:a005:92bb:1d65:1bf4
When I ran the debug log it told me it was expecting the IP 2607:f8b0:4006:80d::200e
So I changed the IPv6 IP in setupVars.conf to be that and IPv6 started working on my PiHole (as confirmed in the query log). I also had to change the IPv6 DNS in my router from the 1bf4 address to the 200e address.
I can confirm on my windows machine that when I run ipconfig /all I get this output:
Clearly you can see that it still is using the "old" IPv6 IP of the PiHole.
So I tried doing nslookup google.com 192.168.0.23 and this works
And I actually just figured it out. I am 100% sure I changed the IPv6 DNS address in my router last night but for some strange reason the setting didn't save .So it still had the 1bf4 address set for IPv6 DNS. I changed this to the 200e address and now everything is working correctly!
Thank you for taking the time to help me troubleshoot!
The one thing I still dont understand is how this IPv6 address mismatch happened in the first place.
Note that public IPv6 addresses (aka GUAs, range 2000::/3) may be subject to frequent changes, as both the IPv6 prefix as well as the interface identifier portion may change regularly (the former initiated by your ISP, the latter by things like IPv6 Privacy Extensions, e.g.).
If it doesn't, configuring Pi-hole's link-local IPv6 (range fe80::/10) could be also an option.
Use that with caution, though, as that address is only visible on the same network segment (or link ). So any L3 switches or VLANs, and devices connected through those won't be able to communicate with Pi-hole that way.
EDIT:
That file is not meant to edit manually.
Run pihole -r with Reconfigure to make your Pi-hole installation aware of your network configuration.