So, installed resolvconf and with a bit more determination than just "WTF that's wrong" I rebooted, logged in and netstat -lnp showed that named was listening on port 53. Of course it is, I fiddle with DNS now and again (http://www.amazon.co.uk/The-Concise-Guide-BIND- guides/dp/0789722739/ref=sr_1_3) and it is _very_ handy if I suddenly find myself in a place with broken DNS-resolution. Which still happens.
So, my local resolver uses the default root hints file and therefore bypasses the local network firewalls dnsmasq server which serves up the addresses to be used for the mail-server and other things at home. But mostly I don't need it so I use the DNS-server provided by DHCP and this is what I want unless I find myself somewhere where it is needed to override it. So the use of resolvconf short-circuits this setup, sends the queries to the local BIND and it in turn buypasses the helpfull firewall dnsmasq. Resulting in bypassing the DHCP given DNS-server. I guess bind9 satisfies some "resolver" dependency in resolvconf but then _still_ overrides the already configured named.conf on the host breaking the admins assumptions about where to resolve things. This will break on ubuntu servers that authoritative non-recursive name servers. I think resolvconf should only step in in this way if dnsmasq is running and not if BIND is running since BIND could very well be non-recursive. Or at the very least have a installation time question about this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1001881 Title: "nameserver 127.0.0.1" in resolv.conf causes failure of name resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1001881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
