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

[Thomas Hood]

@Alkis: IIUC dnsmasq in bind-interfaces mode will not start to listen on
any addresses assigned to interfaces after dnsmasq has started.  So,
yes, she would have to restart standalone dnsmasq if she wants it to
listen on those newly assigned addresses.

IIUC the only way to avoid this is to run dnsmasq in non-bind-interfaces
mode.  (Simon will correct me if I'm wrong.) But that is incompatible
with running nm-dnsmasq.  So if you want dnsmasq in non-bind-interfaces
mode you will have to disable NM's dns=dnsmasq mode.

To escape the dilemma we'd have to enhance dnsmasq and/or the resolver
as we have discussed earlier.

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