Containerized Pihole times out then resolves

Help Community Help
1

I have a fresh install of PiHole running in a container on a Mikrotik RB5009 router. It seems to resolve things fine but it is slow. Every resolution times out and then resolves:

C:\Users\david>nslookup google.com
Server: pi.hole
Address: 192.168.5.10

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
Non-authoritative answer:
Name: google.com
Addresses: 2607:f8b0:4009:804::200e
142.250.191.206

My LAN is on 192.168.4.0/24 and the container bridge in the router is 192.168.5.0/24. I can ping the PiHole's gateway (192.168.5.1) just fine, though the debug log says it can't ping the gateway. The log also says that the container doesn't have an IP address but I think that's because in Mikrotik's implementation you just assign the address to the network interface bound to the container.

Debug log:
https://tricorder.pi-hole.net/OFXXg3Ck/

Thanks for any ideas

UPDATE: unchecking the "conditional forwarding" to the DHCP server seems to have fixed it. But I don't know why - can anyone explain? It should only forward requests to the router for domains ending in my LAN domain name (which is ".elbonia"), and something like "google.com" clearly isn't.

2

What's the result of the following command:

nslookup 192.168.4.91 192.168.5.1
3

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.