From owner-freebsd-questions@FreeBSD.ORG Fri Mar 31 19:18:57 2006 Return-Path: X-Original-To: freebsd-questions@FreeBSD.ORG 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 6950516A41F for ; Fri, 31 Mar 2006 19:18:57 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from mail3.sea5.speakeasy.net (mail3.sea5.speakeasy.net [69.17.117.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7DA7043D4C for ; Fri, 31 Mar 2006 19:18:43 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 25211 invoked from network); 31 Mar 2006 19:18:43 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail3.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 31 Mar 2006 19:18:42 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id 337C828426; Fri, 31 Mar 2006 14:18:42 -0500 (EST) Sender: lowell@be-well.ilk.org To: fbsd_user@a1poweruser.com, freebsd-questions@FreeBSD.ORG References: <20060331183758.66265.qmail@web52703.mail.yahoo.com> From: Lowell Gilbert Date: 31 Mar 2006 14:18:41 -0500 In-Reply-To: <20060331183758.66265.qmail@web52703.mail.yahoo.com> Message-ID: <44y7yqfmni.fsf@be-well.ilk.org> Lines: 19 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Subject: Re: DHCPD config X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-questions@FreeBSD.ORG List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Mar 2006 19:18:57 -0000 Kris Anderson writes: > I think the answer you are looking for lies in > dhclient-script. I noticed it futzes with resolv.conf. > If you happen to notice resolv.conf changing (You can > test this about by making a backup of resolv.conf, > erasing its contents and then rebooting the machine, > just for the sake of everything running properly and > seeing if the contents of resolv.conf get repopulated > with your ISPs DNS settings) then you can create a > script to grab the elements needed from the ISP and > drop them in to a file for dhcpd to read and then > SIGTERM dhcpd and restart it. Basically, "have dhclient-script rewrite the dhcpd.conf". Running your own nameserver and pointing the internal DHCP clients to it is another option, but slightly less resistant to failures. Doing both will get you the best of both worlds.