I personally use OpenDNS for everything since theyre outside of what the ISP handles. only "downside" is that if it cannot resolve a domain for HTTP, it pulls up their search page instead. -Sean
> From: [EMAIL PROTECTED]> To: support@pfsense.com> Date: Fri, 26 Oct 2007 > 09:20:52 -0400> Subject: Re: [pfSense Support] DNS Issues with 1.2 RC2> > I > will try this later to see what the result is. Scott's suggestion of using > > a static route worked perfectly. The trouble seemed to come from using OPT1 > > and OPT2 DNS servers as the default. The pfsense machine was trying to > > resolve with those DNS servers using the WAN interface. I added entries for > > the LAN section of the firewall rules. This set the correct outbound > > interface for machines on the LAN but did not seem to help the pfsense > > machine itself. If the ISP used on the WAN interface did not has lousy DNS > > servers, I would never have noticed this issue. > > Robert> > On Friday 26 > October 2007 05:36, Paul M wrote:> > Robert Goley wrote:> > > based routing. > DNS refuses to work. This is because the pfsense machine> > > can> >> > I > have no answer for you, but an idea to try.> >> > run "tcpdump -l -n -i xxx > udp and port 53" on the firewall for each> > interface xxx in turn whilst > trying to resolve and see if any packets> > are seen.> >> >> >> >> > > ---------------------------------------------------------------------> > To > unsubscribe, e-mail: [EMAIL PROTECTED]> > For additional commands, e-mail: > [EMAIL PROTECTED]> > > ---------------------------------------------------------------------> To > unsubscribe, e-mail: [EMAIL PROTECTED]> For additional commands, e-mail: > [EMAIL PROTECTED]> _________________________________________________________________ Help yourself to FREE treats served up daily at the Messenger Café. Stop by today. http://www.cafemessenger.com/info/info_sweetstuff2.html?ocid=TXT_TAGLM_OctWLtagline
