DNS Booster is off - pull "on" after minutes it goes "off" - Domain Controller with DNS
Yes, 192.168.xx.xx is our Windows AD domain controller and the local DNS server for the whole LAN (handed out via DHCP).
That explains booster turning off.
But with booster off, Firewalla doesn't answer DNS queries from that device at all (UDP and TCP, timeout).
Tested on the DC with Resolve-DnsName example.org -Server 192.168.xx.1 (equivalent to dig): no response after ~12 s, while 1.1.1.1 answers in ~20 ms.
As soon as booster is switched on for the device, queries are answered again.
Is it expected that Firewalla drops DNS queries from a device with booster disabled?
Workaround for now: the DC forwards to 1.1.1.1/9.9.9.9 directly.
-
It is pretty dangerous turning booster off, it will disable pretty much all domain based blocks, except TLS and IP will remain. (TLS also does domains blocks)
Now, in your case, if you just turn off booster, DNS services will be bypassed, and your network should still work. If you are using a local DNS service, see if this article can help https://help.firewalla.com/hc/en-us/articles/360062551673-How-to-run-an-external-pi-hole-with-Firewalla (pi-hole is just another DNS server which is same as your domain controller)
Please sign in to leave a comment.
Comments
1 comment