Windows 10: Split DNS - request timed out (no IPv6 DNS) ..

Got a problem with Viscosity or need help? Ask here!

rum

Posts: 1
Joined: Fri Apr 15, 2016 10:04 pm

Post by rum » Fri Apr 15, 2016 11:07 pm
Hi!

I am using Windows 10 and Viscosity 1.6.2 (1434). There are no IPv6 DNS servers at the local net or behind the tunnel.

The "Full DNS" mode is working as expected.

If "Split DNS" is activated, any dns request timed out. It seems that only ::1 will be queried, but not the IPv4 DNS server(s).

nslookup directly to 127.0.0.1 -> works fine with the local dns server and a dns server behind the tunnel.
nslookup directly to ::1 -> request timed out (as expected - no IPv6 DNS server)
nslookup without DNS server to use in commandline -> request timed out

ipconfig lists following dns server:
"Split DNS" active:
::1
127.0.0.1
no tunnel active:
192.168.0.1 (local IPv4 dns server)


So i had to switch back to "Full DNS" mode.


Regards,
rum

Eric

User avatar
Posts: 1146
Joined: Sun Jan 03, 2010 3:27 am

Post by Eric » Mon Apr 18, 2016 8:46 am
Hi rum,

::1 is the IPv6 version of 127.0.0.1. Viscosity will listen on both these addresses so it shouldn't matter if you have IPv6 DNS servers or not. Do you have IPv6 disabled on your computer, or have you gone through a process to forcefully disable or block IPv6? What happens if you ping ::1?

Are you able to post the exact nslookups you are doing and their results, as well as a complete copy of your log after you have connected?
https://www.sparklabs.com/support/kb/ar ... envpn-log/

Regards,
Eric
Eric Thorpe
Viscosity Developer

Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs
2 posts Page 1 of 1