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

[Alkis Georgopoulos]

What if NM always dropped whatever configuration file it needs in /etc/dnsmasq.d/nm.conf,
and when NM was started, it would check if /etc/init.d/dnsmasq exists,
 * if yes, dnsmasq is installed, so it read the configuration file and there's no need to do anything,
 * if not, dnsmasq-base is installed, so spawn `dnsmasq -C /etc/dnsmasq.d/nm.conf`.

A nice side effect is that if the user did install dnsmasq but disabled it in /etc/default/dnsmasq or rc.* or wherever, then the local resolver would be automatically disabled as well.
And, using a configuration file rather than a hardcoded command line would be appreciated by many users.
Finally, a single dnsmasq instance would be used in all cases, saving resources.

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