On Thu, Mar 5, 2015 at 9:16 PM, Chris Bagnall <[email protected]> wrote:
> > This. Out of interest, is there a particular reason why you need to use > Google's public DNS at all - especially now that pfSense 2.2 has a 'proper' > DNS resolver (rather than just a cache) I hadn't seen this, thanks for pointing that out. I'm going to use this resolver instead of forwarding from dnsmasq to google. But the reason I wanted to use Google's public DNS on our workstations is that many of our staff are connecting from remote locations, like home, clients offices etc. > But that doesn't always work, especially if (for example) > mail.yourdomain.com resolves to 192.168.10.20 locally, but 1.2.3.4 > externally :-) > I have the same issue with some hosts. Thanks, Marc
_______________________________________________ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
