[Bug 1045616] Re: DHCP server handing out DNS server but DHCP client not loading DNS settings to client
launchpad at numble.net
Wed Sep 5 05:54:43 UTC 2012
I'm going to assign this to resolvconf. I'm not 100% sure that's where
it will end up, but might not get looked at when it's just assigned to
** Package changed: ubuntu => resolvconf (Ubuntu)
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to resolvconf in Ubuntu.
DHCP server handing out DNS server but DHCP client not loading DNS
settings to client
Status in “resolvconf” package in Ubuntu:
ARGH!!!!! Every release causes new problems >:(
If you have:
linux DHCP server on the network with options:
option domain-name "xyz.com";
option domain-name-servers 126.96.36.199, 188.8.131.52;
In Ubuntu 10.x it works fine and pulls the DHCP client pulls the DNS
servers from the DHCP fine.
Ubuntu 12.x - It's broken.
Trying to fix with: adding to /etc/network/interfaces
dns-nameservers 184.108.40.206 220.127.116.11
FAIL. Because you have iface eth0 inet dhcp that option isn't read
Try and configure with Network Manager from commandline because your running a server.
NOPE, network manager doesn't run from CLI commandline only GUI
Can't manually specify the DNS server in /etc/resolv.conf because it's
always getting overwritten.
What's the best option here? I think this might be a bug. Only option
I haven't tried is using the head file from this description:
Resolvconf has a /etc/resolvconf/resolv.conf.d/ directory that can contain “base”, “head”, “original” and “tail” files. All in resolv.conf format.
base: Used when no other data can be found
head: Used for the header of resolv.conf, can be used to ensure a DNS server is always the first one in the list
original: Just a backup of your resolv.conf at the time of resolvconf installation
tail: Any entry in tail is appended at the end of the resulting resolv.conf. In some cases, upgrading from a previous Ubuntu release, will make tail a symlink to original (when we think you manually modified resolv.conf in the past)
To manage notifications about this bug go to:
More information about the foundations-bugs