All the indications are that there is a connectivity problem between the Pi and the router. In this section of the debug log, Pi-hole is checking to see if it can resolve a known blocked domain using the outward facing IP of the Pi, and it is failing. I don't think this is a Pi-hole issue, it's a network issue. Neither the Pi-hole nor the Mac can access the Pi-hole at that IP, and the indications are that that IP isn't processing the traffic.
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] pksbialapodlaska.pl is 0.0.0.0 via localhost (127.0.0.1)
[✗] Failed to resolve pksbialapodlaska.pl via Pi-hole (192.168.1.11)
[✓] doubleclick.com is 172.217.7.14 via a remote, public DNS server (8.8.8.8)