[Bug 1083111] Re: network-manager doesn't configure DNS properly and name resolution fails

Cristian Măgherușan-Stanciu 1083111 at bugs.launchpad.net
Mon Nov 26 10:31:52 UTC 2012


** Also affects: network-manager
   Importance: Undecided
       Status: New

** No longer affects: resolvconf (Ubuntu)

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

Title:
  network-manager doesn't configure DNS properly and name resolution
  fails

Status in NetworkManager:
  New

Bug description:
  My network is configured in such a way that I can only exit through a
  HTTP proxy and the this it is set with proxy.pac so for getting the
  proxy configuration I also need the DNS to work...

  When using dnsmasq for DNS, dnsmasq is getting started by network-
  manager, /etc/resolv.conf is pointing to localhost, but dnsmasq is
  unable to resolv any DNS names. In my network dnsmasq should not try
  to connect directly to the DNS root servers(which it looks like it
  does), but it should just use the DNS servers I get through DHCP. But
  there is nothing telling it to use them, since both /var/run/nm-dns-
  dnsmasq.conf and /etc/NetworkManager/dnsmasq.d (which dnsmasq is set
  to use when started by network-manager) are empty.

  -when not using dnsmasq for DNS in network-manager, I get the right
  DNS servers set inside /run/resolvconf/interface/NetworkManager, but
  resolvconf just won't use them, since it keeps getting localhost from
  /run/resolvconf/interface/lo.dnsmasq. The problem goes away after
  removing this file and restarting resolvconf.

  I think the problem can be worked around in two ways:

  -if using dnsmasq, network-manager should configure the reachable name servers in /etc/NetworkManager/dnsmasq.d
  -if using just resolvconf, /run/resolvconf/interface/lo.dnsmasq should not be created.

  
  Ubuntu version: 12.10
  network-manager version: 0.9.6.0-0ubuntu7
  expected results: DNS resolution should work
  current status: DNS resolution does not work unless I do a workaround each time I connect to the network

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1083111/+subscriptions




More information about the foundations-bugs mailing list