From owner-freebsd-questions@FreeBSD.ORG Sun May 8 20:13:32 2005 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 A7C0F16A4E6 for ; Sun, 8 May 2005 20:13:32 +0000 (GMT) Received: from cobalt.antimatter.net (cobalt.antimatter.net [69.55.224.239]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7CFDE43D6B for ; Sun, 8 May 2005 20:13:32 +0000 (GMT) (envelope-from glenn@antimatter.net) Received: from glenn-mobile.antimatter.net (cpe-66-27-94-59.san.res.rr.com [66.27.94.59]) (authenticated bits=0)j48KDHAH010532 (version=TLSv1/SSLv3 cipher=DES-CBC3-SHA bits=168 verify=NO); Sun, 8 May 2005 13:13:17 -0700 Message-Id: <6.1.0.6.2.20050508130759.06479e20@cobalt.antimatter.net> X-Sender: lists@cobalt.antimatter.net X-Mailer: QUALCOMM Windows Eudora Version 6.1.0.6 Date: Sun, 08 May 2005 13:11:56 -0700 To: Forrest Aldrich , freebsd-questions@freebsd.org From: Glenn Dawson In-Reply-To: <427E6D50.2040003@forrie.com> References: <427E6D50.2040003@forrie.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: Re: /etc/resolv.conf and your ISP 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: Sun, 08 May 2005 20:13:32 -0000 At 12:49 PM 5/8/2005, Forrest Aldrich wrote: >I can think of a few ways to resolve this, but I thought to ask here. > >I have Comcast for my ISP, and of course DHCP changes /etc/resolv.conf >during each update -- lately, they've been screwing things up bigtime, >such that I simply use my own "named" instance. > >My question is: how to reliably keep your own nameserver in >/etc/resolv.conf, and get around the frequent protocol updates that >change/nullify your mods to /etc/resolv.conf. > >Perhaps just a regular script that does a diff and patch of it, or >simply copies over the file you want regularly. Not elegant but it >would work. According to dhclient.conf(5): supersede [ option declaration ] ; If for some option the client should always use a locally-configured value or values rather than whatever is supplied by the server, these values can be defined in the supersede statement. I've never had to use this myself, but I would expect that something like: interface "foo" { ... supersede domain-name-servers 127.0.0.1; ... } would do the trick in your case. -Glenn >I also wonder about creating a dhclient-exit script that would update >certain services automatically when your IP changes. > > >Thx. > >_______________________________________________ >freebsd-questions@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-questions >To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"