From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 22:03:40 2006 Return-Path: X-Original-To: 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 5C41F16A403 for ; Thu, 6 Apr 2006 22:03:40 +0000 (UTC) (envelope-from lyndon@orthanc.ca) Received: from orthanc.ca (orthanc.ca [209.89.70.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id B92A343D79 for ; Thu, 6 Apr 2006 22:03:35 +0000 (GMT) (envelope-from lyndon@orthanc.ca) Received: from localhost (localhost [127.0.0.1]) (authenticated bits=0) by orthanc.ca (8.13.4/8.13.4) with ESMTP id k36M3Up0079497 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 6 Apr 2006 16:03:33 -0600 (MDT) (envelope-from lyndon@orthanc.ca) Date: Thu, 6 Apr 2006 16:03:30 -0600 (MDT) From: Lyndon Nerenberg To: Ulrich Spoerlein In-Reply-To: <20060405152718.GA1003@roadrunner.q.local> Message-ID: <20060406153938.C78654@orthanc.ca> References: <20060405152718.GA1003@roadrunner.q.local> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on orthanc.ca Cc: stable@freebsd.org Subject: Re: resolver doesn't see resolv.conf changes 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: Thu, 06 Apr 2006 22:03:40 -0000 > Is the resolver supposed to periodically check for updates to the > resolv.conf, or are the applications somehow caching the IP of the DNS > server? No, resolv.conf is only read once when the resolver routines initialize. The solution is to run a local caching nameserver instance. You should do this anyway, for performance reasons. Add 'named_enable="YES"' to /etc/rc.conf, and modify your /etc/dhclient.conf as follows: interface "ath0" { supersede domain-name "orthanc.ca"; supersede domain-name-servers 127.0.0.1; } interface "bge0" { supersede domain-name "orthanc.ca"; supersede domain-name-servers 127.0.0.1; } Change the domain string to something more appropriate, and adjust the interface names to match your laptop. You'll need to start named and restart the dhclient instances (in that order) for the changes to take effect. --lyndon