From owner-freebsd-current@FreeBSD.ORG  Tue Jul  8 15:26:29 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 575DB37B401
	for <freebsd-current@freebsd.org>;
	Tue,  8 Jul 2003 15:26:29 -0700 (PDT)
Received: from ms-smtp-02.nyroc.rr.com (ms-smtp-02.nyroc.rr.com
	[24.92.226.49])	by mx1.FreeBSD.org (Postfix) with ESMTP id 7950243FA3
	for <freebsd-current@freebsd.org>;
	Tue,  8 Jul 2003 15:26:28 -0700 (PDT)
	(envelope-from tparquet@twcny.rr.com)
Received: from twcny.rr.com (syr-24-169-89-160.twcny.rr.com [24.169.89.160])
	h68MQRiY023538	for <freebsd-current@freebsd.org>;
	Tue, 8 Jul 2003 18:26:27 -0400 (EDT)
Message-ID: <3F0B4513.2050808@twcny.rr.com>
Date: Tue, 08 Jul 2003 18:26:27 -0400
From: Tom Parquette <tparquet@twcny.rr.com>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030518
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: freebsd-current@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: /etc/rc: WARNING: domainname(1) is not set.
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jul 2003 22:26:29 -0000

Hi,
I have been getting the message "/etc/rc: WARNING: domainname(1) is not 
set" every time I boot one of my machines.
It is a 5.1-CURRENT system but I have not updated since June 15.

I have been ignoring this for some time because I have been trying to 
get DDNS to work.
I thought it was related to my DDNS problem.  Now that I have DDNS 
working (finally) I was supprised to see the message still appearing.

I couldn't find anything in the archives.
Suggestions?

I know it is protocol but please CC me on any replies.  I subscribe to 
CURRENT as a digest.  Replying via the digest is a pain.
TIA.