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 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
