OpenVPN Support Forum

Hey, so the VPN is working great, our company mainly uses Macs and they are all sitting on Mountain Lion, except for one, which is running just Lion, 10.7.

So, before connecting, "cat /etc/resolv.conf" will display my current DNS(192.168.2.1), which is fine.

After connecting to the VPN, the resolv.conf file shows the DNS server that the VPN pushed to me. (192.168.40.28)

After disconnecting the resolve.conf file shows the DNS is still the VPN given address of 192.168.40.28

Obviously I am unable to reach that address to resolve queries as I am no longer connected to the VPN. Why does the OpenVPN Connect client change DNS when connecting but does not revert back after disconnect? Our users must disable and re-enable network services everytime they want to disconnect and use their home internet again.

Is there a solution for this? It seems it's a mountain lion specific issue, Lion works fine.

Ew. Here is my workaround for this problem..

I set the VPN to push 2 DNS servers
Primary: Our internal DNS 192.168.40.28
Secondary: Googles public DNS 8.8.8.8

When disconnecting, the DNS servers will both remain, but when the first one fails to connect it will fall back to googles public DNS..

Is there any other solution for this?

I am demoing the product before buying a license and I have run into the same issue.

The option of providing public dns servers is unacceptable. We have users who will need to return to their own private dns servers after disconnecting. Has anyone determined a fix for this?

Hello people,

I am updating this topic because it appears to be a hot-spot for people to find out about this issue, instead of asking us on the live support chat or the ticketing system.

If you're using OpenVPN Access Server with the OpenVPN Connect Client, and you are having the issue that on Mac OS X Mountain Lion 10.8.something not releasing the DNS server after a disconnect event, then you can solve it by upgrading to our intermediate release 1.8.4.200, which includes a new version of the OpenVPN Connect Client and some changes in the Access Server to ensure that this will now function properly again. If you have an Access Server of version 1.8.0 or higher, upgrade using the package below and then do a reinstall of the OpenVPN Connect Client on the Mac OS X computer that is affected by this issue.

http://staging.openvpn.net/as/1.8.4.200/

If you have any questions or problems with the Access Server product, use the live support chat channel or the support ticket system found on http://support.openvpn.net/.

I have installed 1.8.4.400 OpenVPN Access server and still facing issue of DNS on Mountain Lion OS. After disconnecting the openvpn I hv to renew the IP lease to get the internet access.


As you have mention issue was resolved on 1.8.4.200 is there something I need to change.

Same problem for me... and I'm on 1.8.4.400