I assign this back to bind9 only because, so far as I can tell, I inadvertently de-assigned it from bind9 a while back. I don't mean to imply that I think that there is a problem with bind9.
I'll go further. Now that the NetworkManager-controlled dnsmasq process listens at 127.0.1.1, it's an advantage that named doesn't listen at 127.0.1.1. Because of this, bind9 doesn't conflict with nm-dnsmasq. To check that there is no conflict I just installed bind9 alongside nm- dnsmasq on Ubuntu 12.10 and ran "netstat -nl4p". udp 0 0 127.0.1.1:53 0.0.0.0:* 7365/dnsmasq udp 0 0 127.0.0.1:53 0.0.0.0:* 8898/named [...] Named listens at all addresses assigned to interfaces but not on the wildcard address. Now, I know that dnsmasq has a new mode of operation called "bind- dynamic" which is like "bind-interfaces" mode except that it updates its listen addresses when network interfaces get configured and deconfigured. It appears that bind9 operates in the same way. I added a virtual interface eth0:0 with a bogus address and named started listening on that without being restarted. I brought up a wireless interface and named started listening on that, too. Nice. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/604283 Title: Certain services do not listen on 127.0.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/604283/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs