3 ms·
I don't think that running your own router fully solves this issue. I've had this disabled from day 1 of having fiber and running pfSense behind the BWG320. I a
by hkchad 2y ago
I don't think that running your own router fully solves this issue. I've had this disabled from day 1 of having fiber and running pfSense behind the BWG320. I also have a backup TMobile connection. When the the ATT line goes down (like when the fiber is disconnected...or cut) my DNS won't resolve and just goes to the ATT DNS hijack. For failover to actually work I have to unplug the BGW320. I have posted on ATT forums and pfSense and nobody knows how to bypass this.
- epcoa 2y agoHow is that possible, if you run your own router you control DNS. Make your pfsense not use AT&T DNS?? I don’t know what to tell you but it’s your LAN, you can simply not use AT&T DNS at all. I don’t use pfsense specifically but I can tell you that you have it misconfigured.
- nirav72 2y agoYou probably need to examine your Pfsense settings carefully. I'm running OPNsense with the BGW320 , with Unbound setup as the resolver. No issues.
- RajT88 2y agoThat sounds like a failover problem. My router has dual WAN and will fail over if the WAN port fails to renew its DHCP lease. Ethernet link is still live, but no worky, so fails over.