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

Thomas Hood 1046154 at bugs.launchpad.net
Wed Sep 5 09:47:39 UTC 2012


Hi there iox.

Your system is probably misconfigured in one or more ways.

If you are using NetworkManager and dnsmasq and resolvconf then
/etc/resolv.conf will list only "nameserver 127.0.0.1". But you say that
you are using  NetworkManager and dnsmasq and with resolvconf installed
you had

    nameserver 195.81.137.130
    nameserver 195.81.155.194
    nameserver 192.168.163.200
    search dummy.intranet

Here 127.0.0.1 is not listed.  It looks as if dnsmasq is not really
activated.   The internal nameserver is, I take it, 192.168.163.200.
This should be listed first, not last.

If you are using NetworkManager to establish openvpn connections then
you don't need to change any scripts.  NetworkManager receives the
nameserver addresses from openvpn and submits them to resolvconf.

Your original problem may have been due to bug #1003842. The fact that
the connection type (and thus speed) was a factor makes it more probable
that #1003842 was the problem.

In your initial attempts to solve the original problem it is possible
that you changed the NetworkManager, resolvconf, etc., configurations.
These should be returned to their original state.  The workaround for
#1003842 is to comment out the line

    dns=dnsmasq

in /etc/NetworkManager/NetworkManager.conf.

-- 
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




More information about the foundations-bugs mailing list