"It queries every configured DNS server simultaneously[…]"
Is there a way of forcing pfSense to only use DNS servers configured for a specific WAN/OPT2/OPT3 that is being used in a WAN failover group?
As it works today it sends DNS requests on all WAN links(inluding a 3G connection, OPT3) even though primary WAN is up.
DNS 184.108.40.206 is used for WAN.
DNS 220.127.116.11 is used for WAN.
DNS 18.104.22.168 is used for OPT2.
DNS 22.214.171.124 is used for OPT3.
WAN is up, DNS 126.96.36.199 or 188.8.131.52 are used.
WAN is down, DNS 184.108.40.206 is used.
WAN AND OPT2 are down, DNS 220.127.116.11 is used.
I have tried using the option "Allow DNS server list to be overridden by DHCP/PPP on WAN", but at one point after a complete fail-back(to WAN) from a fail-over
i stil only showed up DNS servers from the slowest 3G connection(the last+slowest fail-over WAN) on the status page.
The queries do not contain much data but it feels like a waste of 3G resource(any money) when quering something that is slower than WAN
even though WAN is up.
check that :
it might be related to your issue.
After some reading it sounds that this is the normal behavior of dnsclient, to query every assigned DNS server :P.
Is there a failover group configured(could be a checkbox and/or autosense)?
If no, then use normal behaviour.
Only query servers manually configured for this active interface or only query servers automatically configured through DHCP assigned from this active interface.
That would take quite a bit of extra logic (prone to extra breakage!) to pull off, if it's even possible.
Most people have always-on WANs so it's beneficial to query them all at once. 3G is the obvious exception to that, and I think someone already has a feature/todo ticket open for 2.1 so we can have a more sensible dial-on-demand mode for 3G WANs since not just DNS but the connection monitoring traffic can add up over some time. People without unlimited data plans might be surprised at the usage.