Thomas, you were right about the dnsmasq parameters: strainu@emily:~$ ps -elf|grep dnsmasq 4 S nobody 6849 6764 0 80 0 - 7573 poll_s 08:24 ? 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.1 --conf-file=/var/run/nm-dns-dnsmasq.conf --cache-size=0 --proxy-dnssec
As to the dig bug, I consider it as being a common sense behavior, as it does not find any IPv6 servers in /etc/resolv.conf and it has to use IPv6 to connect. I will comment further in #1011307. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1010724 Title: NM fails to start dnsmasq such that it listens on ::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1010724/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
