[Bug 1046154] Re: Can't resolve OpenVPN DNS while using a 3G connection with resolvconf installed
1046154 at bugs.launchpad.net
Thu Sep 6 10:57:22 UTC 2012
> 1. This is my /etc/resolv.conf before connecting to the VPN (resolvconf installed):
> # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
> # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
> nameserver 220.127.116.11
> nameserver 18.104.22.168
> nameserver 127.0.0.1
This is wrong and most probably the cause of your problem. There should
not be entries before "nameserver 127.0.0.1".
We need to figure out where those entries are coming from.
Please reproduce this case (i.e., install resolvconf; reboot; connect to
Internet but not to VPN) and run the following commands in a terminal
and post the output:
ls -l /etc/resolv.conf
ls -l /run/resolvconf
ls -l /run/resolvconf/interface
for F in /run/resolvconf/interface/* ; do echo === $F === ; cat $F ; done
ls -l /etc/resolvconf/resolv.conf.d
for F in /etc/resolvconf/resolv.conf.d/* ; do echo === $F === ; cat $F ; done
dpkg -l resolvconf network-manager
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to resolvconf in Ubuntu.
Can't resolve OpenVPN DNS while using a 3G connection with resolvconf
Status in “resolvconf” package in Ubuntu:
Ubuntu version: fresh install of Ubuntu 12.04.1 LTS 64 bits (3.2.0-29-generic)
Resolvconf package version: 1.63ubuntu15
What I expected to happen: Connect through 3G (bluetooth DUN), connect
to a OpenVPN and be able to resolve the internal domain names to
access some servers.
What happened instead: I can't resolve internal hostnames.
Additional information: It only breaks when connecting through 3G.
When connecting through Wifi/Cable it works perfectly.
Workaround: Uninstalling the package resolvconf seems to solve the
Other users probably affected:
I've looked at other bug reports and tried other solutions:
* #922578. Removing "resolvconf" is a workaround that works, but I imagine this is resolvconf bug and there must be a more elegant solution.
* #994575. This looks related, but I already have the patched version and it didn't help.
* #924013. I have already checked that my OpenVPN servers are pushing the right information (DNS + DOMAIN) back to the client.
With resolvconf installed: cat /etc/resolv.conf:
With resolvconf uninstalled: cat /etc/resolv.conf
Please tell me if you need any additional information
To manage notifications about this bug go to:
More information about the foundations-bugs