Your debug log suggests you've configured a DNS loop somehow:
*** [ DIAGNOSING ]: Pi-hole log
-rw-r--r-- 1 pihole pihole 13M Oct 31 07:46 /var/log/pihole.log
-----head of pihole.log------
Oct 31 00:00:07 dnsmasq[31744]: query[PTR] 1.20.168.192.in-addr.arpa from 192.168.20.1
Oct 31 00:00:07 dnsmasq[31744]: forwarded 1.20.168.192.in-addr.arpa to 192.168.20.1
Oct 31 00:00:07 dnsmasq[31744]: query[PTR] 1.20.168.192.in-addr.arpa from 192.168.20.1
Oct 31 00:00:07 dnsmasq[31744]: forwarded 1.20.168.192.in-addr.arpa to 192.168.20.1
Oct 31 00:00:07 dnsmasq[31744]: query[PTR] 1.20.168.192.in-addr.arpa from 192.168.20.1
Oct 31 00:00:07 dnsmasq[31744]: forwarded 1.20.168.192.in-addr.arpa to 192.168.20.1
Your device at 192.168.20.1 (presumably your router) is sending a reverse lookup for its own IP address to your Pi-hole. Conditional Forwarding then sends that request back to 192.168.20.1, which in turn sends it to Pi-hole and so on ad infinitum or until timeout.
So your router is using Pi-hole for DNS, which contradicts:
You'd have to find out why your router would send DNS requests to Pi-hole.