Bind not starting on startup on new system

Lisa Casey lisa at jellico.com
Tue Sep 20 14:54:35 PDT 2005


Hi,

I migrated my web server and DNS server from a FreeBSD 3.2 box  to a new 
FreeBSD 5.3 box last week. I think I have most of the kinks worked out but I 
just ran across a biggie.

The old box was running Bind 8.2.x. On the new box I set up Bind 8.4. I'll 
migrate to Bind 9 soon, but not now during this transition.

We shut the system down so we could move it back to our equipment closet. 
When it came back up, named did not start up automatically (I NEED that to 
happen). I looked in /etc/rc.conf on the old 3.2 box and copied the entries 
pertaining to Bind into /etc/rc.conf on the new 5.3 box. These entries in 
rc.conf are:

named_enable="YES"
named_program="/usr/sbin/named"
named_flags="-u bind -g bind -c /etc/namedb/named.conf"

(I adjusted the path in that last line, evidently on 5.3 named.conf is in 
/usr/local/etc). But named still does not restart on a reboot. What needs to 
go into /etc/rc.conf for this to happen?

I looked in /var/log/messages but saw nothing from the reboot. There are 
entries in /var/log/messages from when I manually started it after the 
server booted. It shows this:

Sep 20 17:26:59 netlink named[557]: starting (/usr/local/etc/named.conf). 
named
 8.4.4 Thu Sep 15 16:42:34 EDT 2005 
lisa at netlink.jellico.com:/usr/ports/dns/
bind84/work/src/bin/named
Sep 20 17:26:59 netlink named[557]: limit files set to fdlimit (1024)
Sep 20 17:26:59 netlink named[557]: db_load could not open: localhost.rev: 
No su
ch file or directory
Sep 20 17:26:59 netlink named[558]: Ready to answer queries.

Where should localhost.rev be?  On my 3.2 box it is in /etc/namedb and this 
is where I have it on the 5.3 box. It is obviously looking for it elsewhere.

Thanks,

Lisa CAsey



-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.344 / Virus Database: 267.11.0/103 - Release Date: 9/15/2005



More information about the freebsd-questions mailing list