I've got the following problem with linux 184.108.40.206:
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=220.127.116.11, 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?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/