> For such multi-WAN setups, I would recommend hard coding your DNS... > ...Then add a static route for one of them so it always goes > out your second WAN
I agree with this entirely. It's perhaps worth mentioning here that you can improve the *perceived* speed of browsing from your users' perspective quite a bit by routing DNS queries out on a less-saturated WAN link. For example, most of the clients to whom we've supplied pfSense-based routers have at least two ADSL connections - one (or more) for general net use, and one for VoIP traffic. DNS traffic is usually sufficiently small that it doesn't affect VoIP quality, so, sending DNS queries out via the less-saturated VoIP ADSL can result in a reasonable improvement to perceived page load times. Might be of benefit to someone on the list in the future... Regards, Chris -- For full contact details visit http://www.minotaur.it This email is made from 100% recycled electrons --------------------------------------------------------------------- To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
