Skip to content
Split DNS broken with 1.7.3?
Got a problem with Viscosity or need help? Ask here!
- Posts: 1
- Joined: Mon Jun 26, 2017 10:16 pm
Since I updated to 1.7.3 my Split DNS config stopped working with the following error:
"Server is not reachable and will not be used"
If I rollback to 1.7.1 it works flawlessly
"Server is not reachable and will not be used"
If I rollback to 1.7.1 it works flawlessly
Hi vFondevilla,
We're not aware of any issues. Do you mean 1.7.2, which is the current Windows version? Or are you referring to the Mac version (which is currently at 1.7.3)?
If you're using the Windows version, a copy of your log and routing table (the output from the "route print" command) while connected with version 1.7.2 would be greatly appreciated so we can debug the issue. Please feel free to censor out any sensitive details before posting them here, or you can send them to our support email address instead.
http://www.sparklabs.com/support/kb/art ... envpn-log/
http://www.sparklabs.com/support/kb/art ... ng-problem
Cheers,
James
We're not aware of any issues. Do you mean 1.7.2, which is the current Windows version? Or are you referring to the Mac version (which is currently at 1.7.3)?
If you're using the Windows version, a copy of your log and routing table (the output from the "route print" command) while connected with version 1.7.2 would be greatly appreciated so we can debug the issue. Please feel free to censor out any sensitive details before posting them here, or you can send them to our support email address instead.
http://www.sparklabs.com/support/kb/art ... envpn-log/
http://www.sparklabs.com/support/kb/art ... ng-problem
Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
Hi,
I can confirm the trouble with DNS resolving. It's definitely not the routing. I can ping the hosts in the VPN-Lan just fine.
DNS is set to split. report follows:
Server ...; Lookup Type - Split; Domains xxxx.; Server is not reachable and will not be used.
</log>
In this log there are also to local dns-entries from the host-Lan listed. Those are also listed with the same error.
Hope this helps.
regards
kollaesch
I can confirm the trouble with DNS resolving. It's definitely not the routing. I can ping the hosts in the VPN-Lan just fine.
Code: Select all
returns
nslookup 'hostname.domain'
Code: Select all
<log>Server:Viscocity
Address: ::1
DNS is set to split. report follows:
Server ...; Lookup Type - Split; Domains xxxx.; Server is not reachable and will not be used.
</log>
In this log there are also to local dns-entries from the host-Lan listed. Those are also listed with the same error.
Hope this helps.
regards
kollaesch
Hi All,
We believe we have found the issue and just released a new beta. Could you please give the latest beta a go (1.7.3 Beta 2) and let us know if the problem is resolved or if you continue to experience issues with Split DNS - http://sparklabs.com/support/kb/article ... -versions/
Regards,
Eric
We believe we have found the issue and just released a new beta. Could you please give the latest beta a go (1.7.3 Beta 2) and let us know if the problem is resolved or if you continue to experience issues with Split DNS - 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
Viscosity Developer
Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs
Hi All,
Thank you for your feedback, we do appreciate it!
1.7.3 has now been released with this fix and is available on our downloads page or via updating.
Regards,
Eric
Thank you for your feedback, we do appreciate it!
1.7.3 has now been released with this fix and is available on our downloads page or via updating.
Regards,
Eric
Eric Thorpe
Viscosity Developer
Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs
Viscosity Developer
Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs
- Posts: 18
- Joined: Thu Sep 24, 2020 2:16 am
This issue seems to be in 1.9.2 now. Once connected the two DNS servers I use in Split DNS are reachable by ping. Might need to look into this again.
Hi Chris,
Are you able to do an nslookup against your server directly? e.g. if you server is 1.1.1.1:
nslookup sparklabs.com. 1.1.1.1
Are you able to post a copy of your log and some details on what is going on and we can look into it?
https://sparklabs.com/support/kb/articl ... envpn-log/
1.9.2 has been out for a while now and this is the first report we've had of split DNS issues, you may have a configuration or firewall issue we can help you with instead here.
As this is a public forum, you may wish to email us your log/results instead - https://sparklabs.com/support/#contact
Regards,
Eric
Are you able to do an nslookup against your server directly? e.g. if you server is 1.1.1.1:
nslookup sparklabs.com. 1.1.1.1
Are you able to post a copy of your log and some details on what is going on and we can look into it?
https://sparklabs.com/support/kb/articl ... envpn-log/
1.9.2 has been out for a while now and this is the first report we've had of split DNS issues, you may have a configuration or firewall issue we can help you with instead here.
As this is a public forum, you may wish to email us your log/results instead - https://sparklabs.com/support/#contact
Regards,
Eric
Eric Thorpe
Viscosity Developer
Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs
Viscosity Developer
Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs