OpenVPN Client using PIA - DNS issues when VPN is connected

Groty · Nov 27th 2016

I'm trying to get OpenVPN to connect to PIA via the client. I need it to connect at startup as well. I got this working on my Raspberry Pi OMV install without any problems immediately. After testing there, I decided to move to my production NAS and this is giving me DNS issues.

Here's the directions that worked immediately on the Pi install. I replicated them on prod.

http://cloakandcode.com/articl…envpn-openmediavault.html

I also added these lines to the OVPN/CONF files on prod in an attempt to correct the DNS issue.

http://www.softwarepassion.com…th-openvpn-on-ubuntu-box/

So basically, when I run OpenVPN with the OVPN file, it connects fine but then DNS fails immediately.

Code

Last login: Sun Nov 27 12:59:11 2016 from 192.168.X.X
root@omv:~# service openvpn stop
Stopping virtual private network daemon: nyc.
root@omv:~# curl -4 icanhazip.com
73.47.110.103
root@omv:~# cd /etc/openvpn/
root@omv:/etc/openvpn# openvpn nyc.ovpn
Sun Nov 27 13:21:42 2016 OpenVPN 2.2.1 x86_64-linux-gnu [SSL] [LZO2] [EPOLL] [PKCS11] [eurephia] [MH] [PF_INET6] [IPv6 payload 20110424-2 (2.2RC2)] built on Dec  1 2014
Sun Nov 27 13:21:42 2016 WARNING: file 'login.txt' is group or others accessible
Sun Nov 27 13:21:42 2016 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Sun Nov 27 13:21:42 2016 LZO compression initialized
Sun Nov 27 13:21:42 2016 RESOLVE: NOTE: us-newyorkcity.privateinternetaccess.com resolves to 13 addresses
Sun Nov 27 13:21:42 2016 UDPv4 link local: [undef]
Sun Nov 27 13:21:42 2016 UDPv4 link remote: [AF_INET]209.95.50.98:1198
Sun Nov 27 13:21:42 2016 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Sun Nov 27 13:21:42 2016 [e6d1c2af1d05f1e65a897825ea3f56f2] Peer Connection Initiated with [AF_INET]209.95.50.98:1198
Sun Nov 27 13:21:44 2016 TUN/TAP device tun0 opened
Sun Nov 27 13:21:44 2016 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
Sun Nov 27 13:21:44 2016 /sbin/ifconfig tun0 10.56.10.6 pointopoint 10.56.10.5 mtu 1500
Sun Nov 27 13:21:44 2016 /etc/openvpn/update-resolv-conf tun0 1500 1558 10.56.10.6 10.56.10.5 init
dhcp-option DNS 209.222.18.222
dhcp-option DNS 209.222.18.218
/etc/resolvconf/update.d/libc: Warning: /etc/resolv.conf is not a symbolic link to /etc/resolvconf/run/resolv.conf
Sun Nov 27 13:21:44 2016 Initialization Sequence Completed
^Z
[1]+  Stopped                 openvpn nyc.ovpn
root@omv:/etc/openvpn# curl -4 icanhazip.com
curl: (6) Couldn't resolve host 'icanhazip.com'
root@omv:/etc/openvpn#

Display More

I did copy the OVPN to a CONF and point to it in the /etc/default/openvpn file to autostart by name. That's another issue, but I want to focus on the DNS issue first.

Groty · Nov 27th 2016

Routing tables if it helps...

Code

VPN Service Inactive


root@omv:~# netstat -anr
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
0.0.0.0         192.168.100.1   0.0.0.0         UG        0 0          0 eth0
192.168.100.0   0.0.0.0         255.255.255.0   U         0 0          0 eth0


VPN Service Active


root@omv:/etc/openvpn# netstat -anr
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
0.0.0.0         10.64.10.5      128.0.0.0       UG        0 0          0 tun0
0.0.0.0         192.168.100.1   0.0.0.0         UG        0 0          0 eth0
10.64.10.1      10.64.10.5      255.255.255.255 UGH       0 0          0 tun0
10.64.10.5      0.0.0.0         255.255.255.255 UH        0 0          0 tun0
128.0.0.0       10.64.10.5      128.0.0.0       UG        0 0          0 tun0
192.168.100.0   0.0.0.0         255.255.255.0   U         0 0          0 eth0
209.95.50.134   192.168.100.1   255.255.255.255 UGH       0 0          0 eth0

Display More

subzero79 · Nov 28th 2016

You can find the solution using google, look at the resolv.conf symbolic link log. Dns is not able to be setup dynamically.

dpkg-reconfigure resolvconf

If it doesn't work try OpenVPN irc channel, you'll find better support there.

TaskMaster · Nov 28th 2016

On line 7 you run "openvpn nyc.ovpn" and stop it on line 25-26, no? Open another terminal to test without stopping it or run it in the background maybe?

EDIT - oop, I see subzero79's answer.

Groty · Nov 28th 2016

Quote from subzero79

You can find the solution using google, look at the resolv.conf symbolic link log. Dns is not able to be setup dynamically.

dpkg-reconfigure resolvconf

If it doesn't work try OpenVPN irc channel, you'll find better support there.

This totally did it! Thank you! I did see a reference to this, but I didn't think it applied.

Participate now!