That doesn't seem to be the case:
Besides your Pi-hole, your router's DHCP server is still active in your network, distributing two public IPv4 addresses as DNS servers.
*** [ DIAGNOSING ]: Discovering active DHCP servers (takes 10 seconds)
Scanning all your interfaces for DHCP servers
* Received 548 bytes from eth0:192.168.0.1
DHCP options:
Message type: DHCPOFFER (2)
server-identifier: 192.168.0.1
router: 192.168.0.1
dns-server: 62.179.1.61
dns-server: 62.179.1.63
domain-name: "home"
--- end of options ---
* Received 300 bytes from eth0:192.168.0.100
Offered IP address: 192.168.0.238
DHCP options:
Message type: DHCPOFFER (2)
server-identifier: 192.168.0.100
dns-server: 192.168.0.100
domain-name: "home"
router: 192.168.0.1
--- end of options ---
Note that DHCP is strictly IPv4.
Since your network is not configured as expected for IPv4, I suspect your router to advertise its IPv6 address as DNS server as well.
Thank you for your reply. At some point after router reset, everything started to work. Unfortunately I don't know why but during the night the router turned on dhcp by itself.
I disabled dhcp again and it looks like everything is working for now.