[Bug 1046154] Re: Can't resolve OpenVPN DNS while using a 3G connection with resolvconf installed

[Steve Langasek]

I'm confused by your "with resolvconf" configuration.  Are you using
NetworkManager?  Do you have NetworkManager configured to not use
dnsmasq, which it will do by default?

I'm also confused as to why the *without* resolvconf config shows a
nameserver of 127.0.0.1.  That doesn't look like a value that should be
pushed by the openvpn server.  What are the DNS and DOMAIN values being
pushed by the server?

The openvpn package ships a script, /etc/openvpn/update-resolv-conf,
which is meant to integrate with resolvconf; but it must be added to
your openvpn .conf file in order to be used (as described at the top of
the script).  Have you done this?  If *not*, then I don't see anything
else in the openvpn package which handles updates to /etc/resolv.conf at
all.

** Changed in: resolvconf (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1046154

Title:
  Can't resolve OpenVPN DNS while using a 3G connection with resolvconf
  installed

Status in “resolvconf” package in Ubuntu:
  Incomplete

Bug description:
  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
  problem.

  Other users probably affected:
  http://mobilesociety.typepad.com/mobile_life/2012/07/ubuntu-1204-the-
  network-manager-3g-internet-and-vpn.html

  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:
      nameserver 195.81.137.130
      nameserver 195.81.155.194
      nameserver 192.168.163.200
      search dummy.intranet

  With resolvconf uninstalled: cat /etc/resolv.conf
      domain dummy.intranet
      search dummy.intranet
      nameserver 127.0.0.1

  Please tell me if you need any additional information

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1046154/+subscriptions