On Fri, May 21, 2010 at 12:07 PM, Chris Bagnall <[email protected]> wrote: >> 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. >
In 1.2.3 and newer, the DNS forwarder queries all configured DNS servers simultaneously and takes the first response. So if you set it up so one goes out each WAN, you'll get that benefit automatically, plus the benefit that if the other WAN responds faster, it'll take that response. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] Commercial support available - https://portal.pfsense.org
