![]() ![]() The active NextDNS app or profile will work without switching it off and on again. Here, compared to the provider app option mentioned above, VPN connection drops and reconnects won't result in issues. ![]() The first option is to just use Viscosity together with the NextDNS app or profile.The Viscosity app is an OpenVPN client that can be used with OpenVPN config files that most providers offer for downloading. This option can lead to some unexpected behaviors that will have to be tested for the specific VPN service/app in use. This can override the VPN DNS, but if the VPN connection drops and reconnects, the VPN DNS will be used from this point on. Sometimes however it works to just enable the VPN connection first and then to enable the NextDNS connection afterwards (via app or activating the profile). Most VPN apps/providers obviously push their own DNS servers to prevent leaks, this is expected. VPN Provider App & NextDNS App / Profile (Mac) Tested on macOS 11.6 and iOS 15.1 beta (should be just fine on iOS 14). Here are my experiences on this for Mac and iOS with several working options. There are many posts of people trying to use VPNs and NextDNS together, but this usually doesn't work well. VPN Provider App & NextDNS App / Profile (Mac).Make the Windows client work the same way as the Mac client and allow up to 2 levels of subdomain matching. Direct DNS lookups for any number of subdomains to VPN provided DNS servers since this makes the most sense for a split DNS configuration (I have no idea what the use case is for not wanting it to work this way).Ģ. This is a plea to consider one of the following options (ranked best to worst):ġ. ![]() Unfortinately the Windows behavior is different and makes Split DNS useless in our case. I'm personally on a Mac, so I assumed Split DNS was working correctly when I was able to resolve most of my b.a. lookups through the VPN (verified by packet capture). With the current implementation this almost forces me to use Full DNS instead of Split DNS which is unfortunate. b.a. or c.b.a.) and the number of domains used would mean pushing down nearly 100 domains which I would rather not do. In our case we have a domain structure that means most domains are 2 or 3 levels deep (e.g. I disagree with the implementation decision that you've made to not direct any and all subdomain lookups for a domain pushed through the VPN in split DNS mode to VPN DNS servers since if that functionality were not desired the easy solution would be to only specify the individual subdomains. I've also tried the 1.6.2 beta and no luck. ![]() Split DNS seems to work in OS X for a. and b.a. but on Windows 10 only a. works (not a.b.). Just to mention, in the Viscosity connection settings I already tried setting "DNS" from "Automatic" to "Disabled", but of course this doesn't help as well. The same will appear after every re-connection, and as I have so switch between VPNs kind of often, this is TERRIBLY annoying.Ĭan you please advise how to fix this? Manipulating DNS wasn't necessary before, can't see why this behaviour popped up now. I always have to put my DNS servers (8.8.8.8 / 8.8.4.4) here again manually to fix my Internet connection. So I'll go and edit my LAN adapters settings, IPv4 settings and will find that where my DNS settings have been, Viscosity placed either an empty setting or localhost (127.0.0.1). When connecting to VPN using Viscosity, the connection will work, however any other software like my browser will throw errors that the DNS resolution isn't possible. Since one of the last updates, Viscosity is manipulating my Windows DNS settings all the time. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |