On Sat, 2004-12-18 at 11:15, Charles-Henri Collin wrote:i should put a /etc/resolv.conf.... but i dont want, for "dark reasons" ;)
I've got the following problem with linux 188.8.131.52:
I'm nfs-rooting a diskless client with kernel parameter ip=dhcp.
My dhcpd.conf has a "option domain-name-servers X.X.X.X;" statement and "get-lease-hostnames true;"
Now when the diskless clients boot, no name-server configured and they cant resolv.
dmesg gives me, for instance:
IP Config: Complete:
device=eth0, addr=192.168.0.237, mask=255.255.255.0, gw=192.168.0.1,
host=clientFSB-237.fsb.net, domain=fsb.net, nis-domain=FSBnis,
boot-server=192.168.0.254, rootserver=184.108.40.206, rootpath=
So as you can see, everything is almost set up, except a nameserver!
Has anyone heard about that problem before? Are there any fixes?
The fix is to make sure you have a nameserver in your /etc/resolv.conf
The kernel has no idea how to resolve names into addresses. That's a
userspace thing. I'm not sure if you can extract the dhcp info from the
kernel after the boot, otherwise you'll just have to run a userspace
dhcp client, I use dhclient.