conf/61811: 5.2 release no resolv.conf created after dhcp
client set up in sysinstall
Jim Allers
jallers at sbcglobal.com
Sat Jun 5 01:10:37 GMT 2004
The following reply was made to PR conf/61811; it has been noted by GNATS.
From: "Jim Allers" <jallers at sbcglobal.com>
To: <freebsd-gnats-submit at FreeBSD.org>, <santoniuk at charter.net>
Cc:
Subject: Re: conf/61811: 5.2 release no resolv.conf created after dhcp client set up in sysinstall
Date: Fri, 4 Jun 2004 20:08:32 -0500
Experienced the same problem with 5.2.1. The DLINK DI-604 router doesn't
send a non-empty domain name by default and if an empty domain name is
received by the FreeBSD client, then no /etc/resolv.conf. Even though
the DHCP client receives a domain name server, no /etc/resolv.conf is
created. Why require a non-empty new domain name be resolved to write
out name servers?
More information about the freebsd-qa
mailing list