Simon: > If you can make #2 happen without breaking things, that would seem to be > worth doing
Indeed, primum non nocere. Standalone dnsmasq works fine in the absence of NM+dnsmasq and vice versa and this must continue to be the case when we are done. :) > I guess the main problem is that you need dnsmasq 2.61 As this issue has low importance I imagine it will only be fixed in quantal? Simon: > Further to #2 and getting dnsmasq support. I found a bug last night > that means that dnsmasq --listen-address=<ip addr> where <ip addr> > is not on an interface, will listen on port 69 of <ip addr> even if > tftp is not enabled I just changed the lines in NetworkManager C code: s/127.0.0.1/127.0.0.2/. With this change nm-dnsmasq does indeed not listen... unless address 127.0.0.2 is added to lo. But then standalone "dnsmasq --bind-interfaces" won't start unless that address is removed from lo again. Once they have both been started in this way they both work --- standalone dnsmasq forwarding to nm-dnsmasq and the latter forwarding to the upstream nameservers. The reason they cascade in this order is that dnsmasq registers 127.0.0.1 under the name "lo.dnsmasq" which has a high priority according to /etc/resolvconf/interface-order; it thus appears in resolv.conf. NM registers 127.0.0.2 with resolvconf and this is given to standalone dnsmasq by /etc/resolvconf/update.d/dnsmasq as its forwarding address. Nm-dnsmasq is given the addresses of the upstream nameservers by NM in /var/run/nm-dns-dnsmasq.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 running, yet network-manager doesn't Conflict with their packages 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 : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
