From owner-freebsd-stable@FreeBSD.ORG Mon Jun 5 13:33:49 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1E15916A6CB for ; Mon, 5 Jun 2006 13:33:49 +0000 (UTC) (envelope-from veldy@veldy.net) Received: from sccrmhc14.comcast.net (sccrmhc14.comcast.net [204.127.200.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0383643D48 for ; Mon, 5 Jun 2006 13:33:46 +0000 (GMT) (envelope-from veldy@veldy.net) Received: from veldy.net ([66.41.96.112]) by comcast.net (sccrmhc14) with ESMTP id <2006060513334201400motuke>; Mon, 5 Jun 2006 13:33:46 +0000 Received: from veldy.net (localhost [127.0.0.1]) by veldy.net (Postfix) with ESMTP id 854741CC63; Mon, 5 Jun 2006 08:33:41 -0500 (CDT) Received: from [127.0.0.1] (localhost [127.0.0.1]) by veldy.net (Postfix) with ESMTP id 0F7081CC59; Mon, 5 Jun 2006 08:33:40 -0500 (CDT) Message-ID: <448432B4.3000305@veldy.net> Date: Mon, 05 Jun 2006 08:33:40 -0500 From: "Thomas T. Veldhouse" User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: freebsd@orchid.homeunix.org References: <44842282.6050409@veldy.net> <448428D8.5030501@orchid.homeunix.org> In-Reply-To: <448428D8.5030501@orchid.homeunix.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-stable@freebsd.org Subject: Re: resolv.conf and dhclient X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Jun 2006 13:33:58 -0000 Karol Kwiatkowski wrote: > On 05/06/2006 14:24, Thomas T. Veldhouse wrote: > >> What is the best approach to keep dhclient from overwriting >> /etc/resolv.conf every time it gets a new lease on an IP address? This >> has been a frustrating search as Google has turned up next to nothing on >> the issue other than a hack into a script file which should be >> overwritten when world is rebuilt. >> > > If I'm getting your question right - isn't 'supersede' option in > dhclient.conf(5) what you want? Something like: > > interface "int0" { > supersede domain-name "example.com" > supersede domain-name-servers "127.0.0.1" > } > > Indeed ... this seems to be what I am looking for. Thanks! Tom Veldhouse