Experience Split DNS Problem for a few weeks now

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

Tequila

Posts: 1
Joined: Thu Mar 08, 2018 8:08 am

Post by Tequila » Thu Mar 08, 2018 8:18 am
Hello,

I have the following setup:

Viscosity 1.7.7, Windows 10 1709, ESET NOD Antivirus

Several OpenVPN Connections to site networks.

If I establish a VPN connection I have massive DNS problems when trying to reach any web address. Sometimes no name resolution, sometimes very slow. If I disable the DNS connection, everything works fine again.

A nslookup gives the following:
Code: Select all
nslookup google.com 127.0.0.1
DNS request timed out.
    timeout was 2 seconds.
Server:  UnKnown
Address:  127.0.0.1

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Zeitüberschreitung bei Anforderung an UnKnown.
Nslookup through my router gives:
Code: Select all
nslookup www.google.com 10.23.21.1
Server:  fritz.box
Address:  10.23.21.1

Nicht autorisierende Antwort:
Name:    www.google.com
Addresses:  2a00:1450:400e:805::2004
          172.217.17.132
Nslookup through the remote DNS gives:
Code: Select all
nslookup www.google.com 192.168.2.3
Server:  aspire-pdc.aspire.local
Address:  192.168.2.3

Name:    www.google.com
Addresses:  2a00:1450:4005:80b::2004
          172.217.19.68
Could you help me please with this issue?

Eric

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

Post by Eric » Thu Mar 08, 2018 3:14 pm
Hi Tequila,

Could you please post a complete copy of your OpenVPN log so we can have a look how your network is setup.
https://sparklabs.com/support/kb/articl ... envpn-log/

Your also mention several connections, are these active at the same time or one at a time?

You also mention this has been happening for a few weeks. Does this mean this problem has suddenly appeared a few weeks ago? If so, were there any major updates to any other firewall or AV software you use around that time? The timeouts indicate that something might be blocking Viscosity from network requests.

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