Está en la página 1de 2

Ubuntu

5/13/2016
Community Ask! Developer Design Discourse Hardware
Having
Insights
Juju
DNS
Shop More
Issues when connected to a VPN in Ub


1 1 help

Having DNS Issues when connected to a VPN in Ubuntu 13.04

I am connecting to a Cisco VPN Server using vpnc. Once connected, my machine was unable to automatically update DNS setting from the
new VPN. I tested by temporarily changing /etc/resolv.conf with the proper nameserver and search domain, and everything worked. This is
obviously not a long term solution, so I added an additional DNS server and search domain to the VPN settings in Network manager. With
those settings in place, resolvconf does add the search domain, but not the DNS IP, and I still cannot do any lookups.

What is my next step in conguring or troubleshooting from here?

13.04 vpn dns

asked Jul 17 '13 at 3:46


etsauer
58 1 1 4

Please le a bug report against resolvconf so that we can debug this together. Use the apportbug command-
line utility or use the web interface at bugs.launchpad.net/ubuntu/+source/resolvconf/+lebug. Also please read
the existing bug #1000244: bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1000244 jdthood Jul 17 '13 at
15:06

2 Answers

First make sure that there are no lines beginning with nameserver in any les in
/etc/resolvconf/resolv.conf.d. If /etc/resolvconf/resolv.conf.d/tail is a symbolic link to target
original, make it point to /dev/null.

Second, disconnect from the VPN. Edit /etc/NetworkManager/NetworkManager.conf

$sudogedit/etc/NetworkManager/NetworkManager.conf

and comment out

dns=dnsmasq

(i.e., add a # so that it looks like the following)

#dns=dnsmasq

and then

sudorestartnetworkmanager

answered Jul 19 '13 at 11:14


jdthood
6,611 24 52

jdthood's answer worked perfect for me in 14.04 too. I also had to remove everything from my
/etc/network/interfaces except for the lo reference, and also change managed=false back to true in
/etc/NetworkManager/NetworkManager.conf. I had to reboot for changes to take eect. 00fruX Apr 25 '14 at 1:32

Try checking if your /etc/resolv.conf have symbolic link to /run/resolvconf/resolv.conf . It


solved the problem for me.

To check if it has symbolic link:

lsla/etc/resolv.conf

Sample output, if it has symbolic link:

lrwxrwxrwx1rootroot27Jun3022:22resolv.conf>/run/resolvconf/resolv.conf

Otherwise, delete or backup existing /etc/resolv.conf and then:

sudolns/run/resolvconf/resolv.conf/etc/resolv.conf

edited Jul 1 '14 at 3:37 answered Jul 1 '14 at 3:29


Parveen Kumar
13 4

This solution worked perfectly for me, thanks! PKKid Feb 5 at 15:46
5/13/2016 Having DNS Issues when connected to a VPN in Ub