On 5/3/15 7:02 pm, Vick Khera wrote:
It seems like you should figure out why your client VPN software is broken, and fix that.
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).
My personal solution was to just make the internal hostnames resolve globally. I mean, who really cares if anyone knows that my workstation IP address is 192.168.7.80?
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 :-)
Kind regards, Chris -- This email is made from 100% recycled electrons _______________________________________________ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
