From owner-freebsd-questions@FreeBSD.ORG Tue Aug 1 15:53:16 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 EFC0E16A4DD for ; Tue, 1 Aug 2006 15:53:16 +0000 (UTC) (envelope-from list-freebsd-2004@morbius.sent.com) Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5BEAA43D6D for ; Tue, 1 Aug 2006 15:53:16 +0000 (GMT) (envelope-from list-freebsd-2004@morbius.sent.com) Received: from frontend3.internal (frontend3.internal [10.202.2.152]) by frontend1.messagingengine.com (Postfix) with ESMTP id D5731D92B4F for ; Tue, 1 Aug 2006 11:53:14 -0400 (EDT) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by frontend3.internal (MEProxy); Tue, 01 Aug 2006 11:53:18 -0400 X-Sasl-enc: rOvTCCKchGY89xGHqZS8q4Rqo6ppCtQLABxVGqCIloVk 1154447598 Received: from [192.168.1.2] (bb-87-81-140-128.ukonline.co.uk [87.81.140.128]) by mail.messagingengine.com (Postfix) with ESMTP id 42E23785F for ; Tue, 1 Aug 2006 11:53:18 -0400 (EDT) From: RW To: freebsd-questions@freebsd.org Date: Tue, 1 Aug 2006 16:53:10 +0100 User-Agent: KMail/1.9.3 References: <20060801133245.B9668@rust.salford.ac.uk> In-Reply-To: <20060801133245.B9668@rust.salford.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200608011653.12446.list-freebsd-2004@morbius.sent.com> Subject: Re: Using dnscache locally with FBSD 6.x X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Aug 2006 15:53:17 -0000 On Tuesday 01 August 2006 13:41, Mark Powell wrote: > That means I need to replace resolv.conf early in the boot with the > addresses of remote dns caches: >... > and then in dnscache's svscan startup file I can then put it back to: > > ----- > nameserver 127.0.0.1 The nameservers in resolv.conf are tried in order. You can simply put 127.0.0.1 first, followed by the other servers. This only adds a few seconds to the startup, it not like the timeouts of several minutes that you get when no nameserver is available. If your problem is that the external nameservers come from dhcp then just add the line prepend domain-name-servers 127.0.0.1; to /etc/dhclient.conf