I don't have v13.1 on my unit yet, and I have some crazy ideas that might work around this little catch but without v13.1 to play with yet I cannot test, and I don't want to send you off on some wild goose chases. So Untangle is just going to use whatever DNS server the resolver decides to use. So all that does is add the VPN provider's DNS to the list. but the way the DNS resolver works on most OS's is that any and all DNS servers can be used. If you leave External aimed at the ISP, Untangle will use the ISP DNS, assuming the VPN provider adds another DNS when the VPN connection is made, that's great. This may also permanently disable the tunnel if the tunnel itself uses a DNS name. You can override your External interface DNS to the IP address of the DNS server at the VPN host, however should you do so DNS resolution when the tunnel is down dies. Note once again, it doesn't prevent access to Untangle, or Untangle's ability to access remote DNS servers. That won't impact Untangle at all, but it will prevent anything from getting to a DNS server through Untangle. For starters you're going to need to create a firewall rule that blocks everything destined to port 53.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |