[Bug 959037] Re: NM-controlled dnsmasq prevents other DNS servers from starting

[Thomas Hood]

I wrote in comment #131:
> What benefits would the nm-dns module or the enhanced
> dns module give us relative to what we have now? One is:
> the ability to run nm-dnsmasq on another port, freeing up
> port 53 for BIND named listening on ALL:53. What else? 

I just installed bind9 and was surprised to see that in its default
configuration named behaves just like dnsmasq in bind-dynamic mode. That
is, it listens on port 53 at all addresses assigned to interfaces. When
interfaces are created or configured, named starts listening on those as
well. With this behavior, it shouldn't often (ever?) be necessary to
configure named to listen on the wildcard address.

Is there any nameserver out there that does still conflict with nm-
dnsmasq listening at 127.0.1.1:53?

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

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