From owner-freebsd-qa@FreeBSD.ORG  Fri Jun  4 18:10:37 2004
Return-Path: <owner-freebsd-qa@FreeBSD.ORG>
Delivered-To: freebsd-qa@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 9BC2F16A4CE
	for <freebsd-qa@hub.freebsd.org>;
	Fri,  4 Jun 2004 18:10:37 -0700 (PDT)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 95ED243D2F
	for <freebsd-qa@hub.freebsd.org>;
	Fri,  4 Jun 2004 18:10:37 -0700 (PDT)
	(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1])
	i551AP25037245	for <freebsd-qa@freefall.freebsd.org>;
	Fri, 4 Jun 2004 18:10:25 -0700 (PDT)
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i551AODJ037244;
	Fri, 4 Jun 2004 18:10:24 -0700 (PDT)
	(envelope-from gnats)
Date: Fri, 4 Jun 2004 18:10:24 -0700 (PDT)
Message-Id: <200406050110.i551AODJ037244@freefall.freebsd.org>
To: freebsd-qa@FreeBSD.org
From: "Jim Allers" <jallers@sbcglobal.com>
Subject: Re: conf/61811: 5.2 release no resolv.conf created after dhcp
	client set up in sysinstall
X-BeenThere: freebsd-qa@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: Jim Allers <jallers@sbcglobal.com>
List-Id: FreeBSD Quality Assurance <freebsd-qa.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-qa>,
	<mailto:freebsd-qa-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-qa>
List-Post: <mailto:freebsd-qa@freebsd.org>
List-Help: <mailto:freebsd-qa-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-qa>,
	<mailto:freebsd-qa-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Jun 2004 01:10:37 -0000

The following reply was made to PR conf/61811; it has been noted by GNATS.

From: "Jim Allers" <jallers@sbcglobal.com>
To: <freebsd-gnats-submit@FreeBSD.org>, <santoniuk@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?