> 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 Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/959037 Title: NM-controlled dnsmasq prevents other DNS servers from starting Status in “djbdns” package in Ubuntu: New Status in “dnsmasq” package in Ubuntu: Confirmed Status in “network-manager” package in Ubuntu: Triaged Bug description: As described in https://blueprints.launchpad.net/ubuntu/+spec/foundations-p-dns- resolving, network manager now starts a dnsmasq instance for local DNS resolving. That breaks the default bind9 and dnsmasq installations, for people that actually want to install a DNS server. Having to manually comment out "#dns=dnsmasq" in /etc/NetworkManager/NetworkManager.conf doesn't sound good, and if it stays that way, it should be moved to the bind9 and dnsmasq postinst scripts. Please make network-manager smarter so that it checks if bind9 or dnsmasq are installed, so that it doesn't start the local resolver in that case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/djbdns/+bug/959037/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
