From owner-freebsd-stable@FreeBSD.ORG Tue May 10 05:24:20 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 B173A16A4EF for ; Tue, 10 May 2005 05:24:20 +0000 (GMT) Received: from web54010.mail.yahoo.com (web54010.mail.yahoo.com [206.190.36.234]) by mx1.FreeBSD.org (Postfix) with SMTP id 2733943D68 for ; Tue, 10 May 2005 05:24:20 +0000 (GMT) (envelope-from spamrefuse@yahoo.com) Received: (qmail 54770 invoked by uid 60001); 10 May 2005 05:24:19 -0000 Message-ID: <20050510052419.54768.qmail@web54010.mail.yahoo.com> Received: from [147.46.44.181] by web54010.mail.yahoo.com via HTTP; Mon, 09 May 2005 22:24:19 PDT Date: Mon, 9 May 2005 22:24:19 -0700 (PDT) From: Rob To: FreeBSD Stable MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: 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:24:20 -0000 Hi, I'm running 5-Stable as of today. The PC is a dual-homed gateway to a local network, a caching nameserver, httpd server, firewall etc. In /etc/rc.conf, I have: named_enable="YES" apache2_enable="YES" The nameserver works fine after bootup, so I suppose that the named.conf is properly configured as a caching nameserver. After bootup, there's no httpd running, so I have to start it manually. During the bootup, following line occurs in httpd-error logs: hostname nor servname provided, or not known: mod_unique_id: unable to find IPv4 address of "my.host.name" (I faked "my.host.name" in this email, but it is an officially registered hostname + IP) I solved the problem, by commenting out the line LoadModule unique_id_module libexec/apache2/mod_unique_id.so in httpd.conf. But I think the actual problem is that there's a conflict in bootup order of the caching nameserver and the apache server. ---------------------------------------- Some time ago, there was (or still is) a similar conflict with hostname resolution at bootup when using ntpd. Somehow the caching nameserver seems to get up and working too late in the boot process. Is that possible? Regards, Rob. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com