Client not creating resolv.conf

[Andrew Sweger]

I've concluded that there is a problem with dhcp3 passing over the
domain-name-server and root-path attributes which is triggering the
symptoms described below. Reverting back to the dhcp package fixes this.
And for some reason I am now seeing the FAI options being passed from the
dhcp server to the client. Who knows what I screwed up before. But my
particular issue on resolv.conf is solved. Since dhcp3 isn't in the woody
release right now, this shouldn't be biting others.

On Wed, 24 Apr 2002, Andrew Sweger wrote:

> For some reason, my client host is not creating resolv.conf. So far, I've
> traced this to the fact $DNSSRVS is not being set. $DNSSRVS is set by
> dhclient-perl which should be mapped from the new_domain_name_servers
> variable set in the dhclient environment. I _do_ have 'option
> domain-name-servers x.x.x.x;' in my dhcpd.conf on the server.  I'm using
> the dhcp3 package as it was the only way I found to pass the fai options
> (170, etc.) to the client.
> 
> A dhcpdump seems to reveal that my dhcp server is never returning the DNS
> servers (option 6) to the client, even when it's being explicitly
> requested.

-- 
Andrew B. Sweger -- The great thing about multitasking is that several
                                things can go wrong at once.