Meanwhile my laptop has been working fine with two dnsmasq instances running in cascade. I'll try to subject this arrangement to more severe tests in the coming weeks.
# netstat -nl46p | grep :53 tcp 0 0 127.0.0.2:53 0.0.0.0:* LISTEN 7928/dnsmasq tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 1256/dnsmasq tcp6 0 0 ::1:53 :::* LISTEN 1256/dnsmasq udp 0 0 127.0.0.2:53 0.0.0.0:* 7928/dnsmasq udp 0 0 127.0.0.1:53 0.0.0.0:* 1256/dnsmasq udp 0 0 0.0.0.0:5353 0.0.0.0:* 1097/avahi-daemon: udp6 0 0 ::1:53 :::* 1256/dnsmasq udp6 0 0 :::5353 :::* 1097/avahi-daemon: # ps -elf|grep dnsmasq|grep -v grep 5 S dnsmasq 1256 1 0 80 0 - 8265 poll_s 10:03 ? 00:00:00 /usr/sbin/dnsmasq -x /var/run/dnsmasq/dnsmasq.pid -u dnsmasq -r /var/run/dnsmasq/resolv.conf -7 /etc/dnsmasq.d,.dpkg-dist,.dpkg-old,.dpkg-new 4 S nobody 7928 1090 0 80 0 - 8265 poll_s 12:13 ? 00:00:00 /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.2 --conf-file=/var/run/nm-dns-dnsmasq.conf --cache-size=0 --proxy-dnssec # 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 # cat /var/run/dnsmasq/resolv.conf nameserver 127.0.0.2 # cat /var/run/nm-dns-dnsmasq.conf server=<LAN nameserver address> server=<LAN nameserver address> -- 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 : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
