Fritzbox sometimes messes up hostnames and IP addresses if devices of the same name have been assigned different IP addresseover time, and it could also be confused if additional routing equipment would be active in your network (your switch wouldn't be of a smart/managed variant that would have limited routing/layer-3-switching capabilities?).
If that happens, you could end up speaking to a different device than you want if you access a device by name.
It cannot explain why nslookups to Pi-hole's IP address times out, though.
This would reinforce that something is interfering with DNS, preventing DNS requests to reach your Pi-hole.
As mentioned, the usual suspects here would be firewalls or antivirus DNS features.
Not quite - the debug log shows that DNS resolution via Docker's internal virtual network interfaces fails.
This is expected and shouldn't be harmful, unless other containers under the same Docker daemon's control would require to send DNS requests to Pi-hole via Docker's internal network.
Just to clarify:
The linked configuration does not disable IPv6 - it just stops your router from propagating an IPv6 address as DNS server.
This should at least have resulted in no global scope IPv6 addresses on your Pi-hole host machine's enp2s0
interface.
However, your debug log shows the exact same set of IPv6 addresses as before, including GUAs:
*** [ DIAGNOSING ]: Networking
[✓] IPv6 address(es) bound to the enp2s0 interface:
2003:<redacted>87/64
2003:<redacted>fb/64
2003:<redacted>52/64
fe80::<redacted>ca/64
Also, the IPv6 DNS servers learned by your host machine did not change at all
*** [ DIAGNOSING ]: contents of /etc
-rw-r--r-- 1 root root 998 Nov 28 13:11 /etc/resolv.conf
nameserver 10.0.50.50
nameserver fd00::<redacted>70
nameserver 2003:<redacted>70
nameserver 2003:<redacted>87
search fritz.box
I'm not sure what you refer to here.
I did not recommend to disable IPv6, and there's no reason to do so in your case.
Your FB supports to stop propagation of IPv6 DNS server addresses, and I'd still recommend to configure it in that way.
However, your Pi-hole host seems to be slow in picking up your Fritzbox IPv6 configuration changes, or perhaps to ignore them altogether.
Did you perhaps manually apply a static IPv6 address configuration on the machine hosting Pi-hole?
Does your Pi-hole host pick up IPv6 changes if you reboot it?