From owner-freebsd-stable@FreeBSD.ORG Tue May 10 05:36:06 2005 Return-Path: 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 B9DB516A4EE for ; Tue, 10 May 2005 05:36:06 +0000 (GMT) Received: from pd4mo1so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 61FD743D5E for ; Tue, 10 May 2005 05:36:06 +0000 (GMT) (envelope-from cperciva@freebsd.org) Received: from pd4mr6so.prod.shaw.ca (pd4mr6so-qfe3.prod.shaw.ca [10.0.141.69])2004))freebsd-stable@freebsd.org; Mon, 09 May 2005 23:34:33 -0600 (MDT) Received: from pn2ml4so.prod.shaw.ca ([10.0.121.148]) by pd4mr6so.prod.shaw.ca (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0IG900EOGE5LDB00@pd4mr6so.prod.shaw.ca> for freebsd-stable@freebsd.org; Mon, 09 May 2005 23:34:33 -0600 (MDT) Received: from [192.168.0.60] (S0106006067227a4a.vc.shawcable.net [24.87.209.6]) by l-daemon (iPlanet Messaging Server 5.2 HotFix 1.18 (built Jul 28 2003)) with ESMTP id <0IG900DE8E5K66@l-daemon> for freebsd-stable@freebsd.org; Mon, 09 May 2005 23:34:33 -0600 (MDT) Date: Mon, 09 May 2005 22:34:18 -0700 From: Colin Percival In-reply-to: <20050510052419.54768.qmail@web54010.mail.yahoo.com> To: Rob Message-id: <428047DA.4080803@freebsd.org> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-Accept-Language: en-us, en X-Enigmail-Version: 0.91.0.0 References: <20050510052419.54768.qmail@web54010.mail.yahoo.com> User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050406) cc: FreeBSD Stable Subject: Re: Apache + Caching DNS: conflict at bootup? (DNS runs too late) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 May 2005 05:36:06 -0000 Rob wrote: > Some time ago, there was (or still is) a similar > conflict with hostname resolution at bootup when > using ntpd. Yes, but not with named -- the problem was only when using a dns cache from the ports tree, since those are started later in the boot sequence. Colin Percival