> This assumption is, er, questionable. True, but if you don't mind, let's examine that question a bit. This is the NM-spanwed command line: /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind-interfaces --pid-file=/var/run/sendsigs.omit.d/network-manager.dnsmasq.pid --listen-address=127.0.0.1 --conf-file=/var/run/nm-dns-dnsmasq.conf --cache-size=0 --proxy-dnssec
I assume that NM can be fixed to successfully do the following: * Properly detect if dnsmasq is installed or not, * Use a different command line if it isn't, i.e. the one above, * And only include the configuration options it *really* requires in /etc/dnsmasq/nm.conf in the case that dnsmasq is installed. So let's see which are the dnsmasq configuration options needed by NM: --cache-size=0 Not needed, it won't take any effect in chained dnsmasq mode if #2 is implemented either. If the user does want that, he'd have to put it manually in the main dnsmasq configuration in both solutions (#2 and this one). --bind-interfaces Not needed, there's only one dnsmasq. --no-resolv, --keep-in-foreground, --no-hosts, --pid-file, --listen-address, --conf-file Not needed. --proxy-dnssec Do I assume correctly that this is the only configuration option needed to be dropped in /etc/dnsmasq.d/nm.conf? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
