DNS Resolution on Debian

Business solution to host your own OpenVPN server with web management interface and bundled clients.
Post Reply
CranialBlaze
OpenVpn Newbie
Posts: 3
Joined: Sat Jun 08, 2013 5:34 pm

DNS Resolution on Debian

Post by CranialBlaze » Sat Jun 08, 2013 5:42 pm

I am using slickvpn with OVPN on my rapsberry pi debain box.

If I use my account on my phone all is well, but on the pi I cannot resolve any DNS addresses, had the same problem with VPNBook.

After some searching online I found a solution to be adding push "dhcp-option DNS 192.168.0.1" to the ovpn file, however that is not working, not really sure why though. If I ping external IP address then all is fine, if I connect directly using the ip same thing, its just specifically the resolution.

Is there perhaps a specific point in the file where it needs to be included, I assume its not depreciated as I confirmed this include on the OVPN site, so I can safely assume the problem is with me and/or how I am doing it.

Any assistance would be greatly appreciated

User avatar
janjust
Forum Team
Posts: 2703
Joined: Fri Aug 20, 2010 2:57 pm
Location: Amsterdam
Contact:

Re: DNS Resolution on Debian

Post by janjust » Tue Jun 11, 2013 8:42 am

on the raspberry, check the contents of

Code: Select all

/etc/resolv.conf
after the VPN is up; and then try pinging '8.8.8.8' ; next step is to use 'nslookup' to see if you can reach the DNS server on the remote end.

CranialBlaze
OpenVpn Newbie
Posts: 3
Joined: Sat Jun 08, 2013 5:34 pm

Re: DNS Resolution on Debian

Post by CranialBlaze » Mon Jun 17, 2013 6:16 am

Thanks for the assist, managed to get that all sorted out, but now just noticed something else. With the VPN connected my DDNS is no longer working.

I have already added the exclusion for ddns
route checkip.dyndns.com 255.255.255.255 net_gateway
SO the correct IP address is being reported over to the ddns, but I cannot get into the machine remotely using it, if I stop openvpn then its all fine again, tried adding the exclusion for my ddns host name, but unsurprisingly thats not working.

Is it possible to exclude incoming connection requests or more importantly just this one?

Post Reply