New DNS seems to fail when there is more than 2 subdomains

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

kfow35

Posts: 2
Joined: Wed Aug 05, 2015 2:59 am

Post by kfow35 » Wed Feb 24, 2016 9:41 am
With the most recent update, I'm no longer able to resolve VPN addresses that have more than 2 subdomains.

Example:
Hitting test.admin.internal.domain.com will not resolve, but hitting admin.internal.domain.com will resolve.

The workaround seems to be making all DNS go through the VPN tunnel. This works but slows down everything.

I might start another topic for this one, but it gets indefinitely into a reconnecting state when waking up from sleep mode. Have to explicitly disconnect/connect to recover.

Eric

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

Post by Eric » Wed Feb 24, 2016 4:08 pm
Hi kfow35,

This is by design. Viscosity will only match host names to their immediate parent domain. This is done for both security reasons and it has been the default behaviour of linux type systems for some time. You will either need to set extra domains where they are needed or continue to use Full DNS mode.

In regards to Viscosity not reconnecting, the log might show what is going on - http://sparklabs.com/support/kb/article ... 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