freebsd stable - May 2005 - Apache + Caching DNS: conflict at bootup? (DNS runs too late)

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

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

In the last episode (May 09), Colin Percival said:
> 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.
I always put two nameserver lines in my resolv.conf, even on machines
running bind (where the first line is 127.0.0.1).  That way if programs
are started before bind, they can still do DNs lookups.

-- 
	Dan Nelson
	dnelson@allantgroup.com