


The only change is that ISP on my unrelated request allocated static IP address for the second WAN, previously it was yeah set it to just localhost, that is what I use. That said, I can't reproduce the issue right now, but it was happening for many hours before and I tried different options with no luck. That seems to be what happens, but I didn't add/change any rules for Pi-hole specifically, just modified general egress rule on LAN to send everything through Multi-WAN gateway group. I presume, you have configured at least one.Ĭheck if DNS access to external DNS is allowed for the Pi-hole.

If it doesn't the Pi-hole probably cannot access public DNS servers. DHCP tells everyone to use pfSense's DNS server (192.168.1.1) that resolves local names of machines and forwards the rest to Pi-hole. Maybe, but it works without Multi-WAN and has issues with it Multi-WAN has nothing to do with an internal DNS server at all. Said in Multi-WAN with local DNS server (Pi-hole):
