[Bug 959037] Re: NM-controlled dnsmasq prevents other DNS servers from running, yet network-manager doesn't Conflict with their packages

[Simon Kelley]

On 11/06/12 19:57, Thomas Hood wrote:

> But, second, there is a problem connecting the resolver to the NM-
> controlled dnsmasq such that the latter stays out of the way of the
> general local nameserver which currently wants to listen on the IPv4
> wildcard address.  Using address ::1 for nm-dnsmasq is a quick hack
> which might work without further ado
>
> But even if it works it clearly isn't a permanent solution.  More
> satisfactory would be to use an another port than 53 for the special
> purpose of connecting the resolver with nm-dnsmasq.
>

Another option is to use another address in 127.0.0.0/8, any will work. 
You'll need dnsmasq 2.61 or later for this to be a viable option.

You could have the nm-dnsmasq run with --bind-interfaces 
--listen-address=127.0.100.1 and put 127.0.100.1 in /etc/resolv.conf.

Another instance of dnsmasq will run without interfering with that, 
providing only that --bind-interfaces is set.


Simon.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/959037

Title:
  NM-controlled dnsmasq prevents other DNS servers from running, yet
  network-manager doesn't Conflict with their packages

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