Opened 4 years ago

Closed 4 years ago

#1311 closed Bug / Defect (invalid)

OpenVPN verses Windows Registry DNS Parameters

Reported by: tct Owned by:
Priority: major Milestone:
Component: Generic / unclassified Version:
Severity: Not set (select this one, unless your'e a OpenVPN developer) Keywords:
Cc: tct


Possible OpenVPN bug.

OpenVPN Forum:
Sometimes, after an unexpected reboot, there is a chance that the windows computer will stop resolving any dns names on any network other than the organization's network. When connecting, the system writes the message "No internet" in the connection status. This is possible with both domain computers and off-domain computers, with windows 10 and 8 (possibly others too). This problem cannot be solved by resetting network settings, manually naming the dns server, reinstalling the openvpn connect client.
Delete the hive in the registry at HKLM:
SYSTEM \ ControlSet001 \ Services \ Dnscache \ Parameters \ DnsPolicyConfig? \ OpenVPNDNSRouting-0

Hope this helps someone

Change History (4)

comment:1 Changed 4 years ago by tct

Cc: tct added

comment:2 Changed 4 years ago by Gert Döring

Google finds an older forum posts for that as well:

and this suggests that this is something OpenVPN Connect does, not Community OpenVPN (it's the first time I hear about this).

comment:3 Changed 4 years ago by stipa

This is indeed about OpenVPN Connect. Its service code has a logic which removes those keys on startup.

comment:4 Changed 4 years ago by stipa

Resolution: invalid
Status: newclosed

Closing since this is not about open source project, you can get support for OpenVPN connect here

Note: See TracTickets for help on using tickets.