Note: the dnsmasq.d file included in the new n-m release includes both "bind-interfaces" and "except-interface=lo".
This is already a big improvement. It allows standalone dnsmasq to run on a system with NM and nm-dnsmasq: standalone dnsmasq listens on interfaces other than lo and forwards queries to nm-dnsmasq at 127.0.0.1. $ dpkg -l dnsmasq network-manager|grep ^ii ii dnsmasq 2.62-3 Small caching DNS proxy and DHCP/TFTP server ii network-manager 0.9.6.0~git201207161259.00297f4-0ubuntu1 network management framework (daemon and userspace tools) $ cat /etc/dnsmasq.d/network-manager # Tell any system-wide dnsmasq instance to not bind to the loopback interface. # WARNING: changes to this file will get lost if network-manager is removed. bind-interfaces except-interface=lo $ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 127.0.0.1 search [redacted] $ cat /var/run/dnsmasq/resolv.conf nameserver 127.0.0.1 $ cat /var/run/nm-dns-dnsmasq.conf server=192.168.1.254 server=195.241.76.55 server=195.241.76.58 $ sudo netstat -nl4p |grep :53 tcp 0 0 192.168.1.20:53 0.0.0.0:* LISTEN 7039/dnsmasq tcp 0 0 192.168.1.21:53 0.0.0.0:* LISTEN 7039/dnsmasq tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 6282/dnsmasq udp 0 0 192.168.1.20:53 0.0.0.0:* 7039/dnsmasq udp 0 0 192.168.1.21:53 0.0.0.0:* 7039/dnsmasq udp 0 0 127.0.0.1:53 0.0.0.0:* 6282/dnsmasq udp 0 0 0.0.0.0:5353 0.0.0.0:* 1103/avahi-daemon: -- 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: Fix Released Status in “pdns-recursor” package in Ubuntu: Invalid Status in “pdnsd” package in Ubuntu: Invalid Status in “djbdns” source package in Precise: New Status in “dnsmasq” source package in Precise: Confirmed Status in “network-manager” source package in Precise: Triaged Status in “pdns-recursor” source package in Precise: Invalid Status in “pdnsd” source package in Precise: Invalid 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
