Comment 7 for bug 933723
Revision history for this message
| Peter Lemieux (seijisensei) wrote Re: resolvconf creating bogus resolv.conf file | #7 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
I get the exact same behavior on the Kubuntu Precise desktop beta, though bind9 is not installed. I end up with the resolv.conf posted by the OP with 127.0.0.1 as the nameserver. I cannot override this even with static DNS settings in Kubuntu's network configuration. When the network starts, the manager ignores both the DNS settings on my DHCP-serving router and any static nameserver and search list entries I provide via network configuration.
The notion that bind9 would be installed by default on ordinary client machines is ludicrous.