I think bug #1000244 is just describing the same issue in another way for sure. I'd be happy to work with someone with commit privileges in a virtual machine virgin install in my server cluster to reproduce the issue.
I'm not savvy enough to try and determine if the problem comes from: resolvconf, default config in network stack for ubuntu, or some interaction when bind gets installed from the repo. I just know how to hard/code fix and work around the issue. IMHO, it definitely needs to be permanently fixed because whatever happens after a default install or upgrade, DNS resolution should just work, not require changes to get it working. FYI I was installing a centos 6.x system, and saw a similar interaction which would lead me towards a resolvconf or bind interaction. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1045616 Title: DHCP server handing out DNS server addresses but DHCP client does not write these to resolv.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1045616/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
