Split DNS - DNS remains as 127.0.0.1 after crash

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

btherl

Posts: 7
Joined: Thu Dec 12, 2013 11:01 am

Post by btherl » Fri Nov 04, 2016 11:45 am
As the subject line says, I'm using Split DNS, and everything works nicely. The only exception is when my laptop crashes with Viscosity running. When it starts up again, the DNS remains set to 127.0.0.1 but of course Viscosity is not listening on that IP any more. I have to manually change DNS back to use DHCP, then I'm able to re-establish the VPN.

This is not a major issue now that I know how to resolve it, but it did cause some confusion the first time I experienced it.

I'm using Windows 10 Home 1607 build 14393.351 x64.

Thanks,
Brian

Eric

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

Post by Eric » Fri Nov 04, 2016 12:11 pm
Hi btherl,

There has been some changes to the current beta stream to try and harden Viscosity to recover in the case of a bluescreen/crash. Please give it a go and see if it helps - http://sparklabs.com/support/kb/article ... -versions/

Regards,
Eric
Eric Thorpe
Viscosity Developer

Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs

btherl

Posts: 7
Joined: Thu Dec 12, 2013 11:01 am

Post by btherl » Mon Nov 21, 2016 11:21 am
Thankyou Eric!

I won't try it just yet as I'm a bit hesitant to use a beta version, and the workaround is fairly easy. When I do try it and my laptop crashes (which is too often unfortunately) I'll let you know how it goes!

Brian

Eric

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

Post by Eric » Mon Nov 21, 2016 11:22 am
Hi Brian,

Viscosity 1.6.7 was released last week which includes the aforementioned fix.

Regards,
Eri2c
Eric Thorpe
Viscosity Developer

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