From owner-freebsd-questions@FreeBSD.ORG Mon Jan 19 12:47:10 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AD23D16A4CE for ; Mon, 19 Jan 2004 12:47:10 -0800 (PST) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 73E7743D39 for ; Mon, 19 Jan 2004 12:47:04 -0800 (PST) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from be-well.no-ip.com ([66.30.196.44]) by comcast.net (rwcrmhc13) with ESMTP id <2004011920470301500kcf3se>; Mon, 19 Jan 2004 20:47:04 +0000 Received: by be-well.no-ip.com (Postfix, from userid 1147) id 7FB25F; Mon, 19 Jan 2004 15:47:03 -0500 (EST) Sender: lowell@be-well.ilk.org To: John References: <20040112230938.A62891@starfire.mn.org> <20040113121623.GB57681@ei.bzerk.org> <20040114214637.GA814@tuatara.fishballoon.org> <400695E0.4030105@romat.com> <20040115075720.A57650@starfire.mn.org> From: Lowell Gilbert Date: 19 Jan 2004 15:47:03 -0500 In-Reply-To: <20040115075720.A57650@starfire.mn.org> Message-ID: <44vfn7eke0.fsf@be-well.ilk.org> Lines: 24 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-questions@freebsd.org Subject: Re: Updating DNS after DHCP X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jan 2004 20:47:10 -0000 John writes: > Thanks, but I'm still missing a piece for my ideal scenario. This > requires the DCP server to know to whom it is handing out the > address, doesn't it? How would it know that? Does the DHCP request > include the host name? Or do you have to somehow bind a NIC/MAC > address to a name for isc-dhcp? The DHCP request usually contains a "client identifier", which you can configure dhcpd to use as the host name. You can also use the MAC address to identify machines (and associate a name) if you want. > Clearly, the BIND configuration is already set up to accept updates, > since the Windows system is successful in doing so. I think that client update can be enabled with a dhclient.conf parameter, described in the manual for dhclient.conf(5) under "DYNAMIC DNS", but I prefer to do it from my DHCP server instead... -- Lowell Gilbert, embedded/networking software engineer, Boston area: resume/CV at http://be-well.ilk.org:8088/~lowell/resume/ username/password "public"