You need to restart network-manager after changing the configuration
value.

It's unfortunate that the configuration needs to be changed, but it's
needed. I sympathize with your use case, but there is sufficient benefit
in using NM together with dnsmasq and resolvconf to solve other DNS
resolution issues to inconvenience those who use dnsmasq separately as a
standalone daemon (to have to change the config to suit their needs).

We won't be fixing this for Precise, but I've started discussion with
dnsmasq upstream to possibly deal differently with the binding and allow
running instances on other IP addresses (such as 127.0.1.1 or so). It's
still going to need sufficient amounts of work to fix dnsmasq's method
of binding to interfaces and how NM starts and interfaces with dnsmasq
(though I already have patches for NM, but they're useless without the
fixes in dnsmasq). At this point though, the simplest way to deal with
this remains to edit interfaces= to map to the relevant external
interfaces (eth0, wlan0, etc.) and let the NM-spawned instance get
started on lo.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/959037

Title:
  Don't start local resolver if a DNS server is installed

Status in “network-manager” package in Ubuntu:
  Triaged

Bug description:
  As described in
  https://blueprints.launchpad.net/ubuntu/+spec/foundations-p-dns-
  resolving, network manager now starts a dnsmasq instance for local DNS
  resolving.

  That breaks the default bind9 and dnsmasq installations, for people that 
actually want to install a DNS server.
  Having to manually comment out "#dns=dnsmasq" in 
/etc/NetworkManager/NetworkManager.conf doesn't sound good, and if it stays 
that way, it should be moved to the bind9 and dnsmasq postinst scripts.

  Please make network-manager smarter so that it checks if bind9 or
  dnsmasq are installed, so that it doesn't start the local resolver in
  that case.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to