Bug 115244

Summary: Do not start named after booting FreeBSD
Product: Base System Reporter: vladislav V. Prodan <universite>
Component: i386Assignee: freebsd-i386 (Nobody) <i386>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 7.0-CURRENT   
Hardware: Any   
OS: Any   

Description vladislav V. Prodan 2007-08-06 12:40:20 UTC 
# cat /etc/rc.conf | grep named
named_enable="YES"
named_program="/usr/sbin/named"
named_flags="-c /etc/namedb/named.conf"

&#1054;nly manual helps make the /etc/rc.d/named start

#cat /etc/namedb/named.conf
<SKIP ACL>
options {
        directory       "/etc/namedb";
        pid-file        "/var/run/named/pid";
        dump-file       "/var/dump/named_dump.db";
        statistics-file "/var/stats/named.stats";
        zone-statistics yes;
        version         "named 8.4.2-c2600-js-mz.120-2.XC2";

##      listen-on       { 127.0.0.1; };
        listen-on       { any; };
        listen-on-v6    { ::1; };

        forwarders {
                87.XXX.YYY.130;
                87.XXX.YYY.1;
                };

        allow-query {
                localnet;
                ns_server;
                };

        allow-transfer {
                ns_server;
                };

##      New record, against recursion
        allow-recursion {
                localnet;
                ns_server;
                };


};

include "named-log.conf";
include "named-zone-master.conf";
include "named-zone-slave.conf";
include "named-zone-dynamic.conf";

Fix: 

echo "/etc/rc.d/named start" >> /etc/rc.local
Comment 1 Remko Lodder freebsd_committer freebsd_triage 2007-08-06 13:29:09 UTC 
State Changed
From-To: open->closed

Hello, this seems more like a general support question then a Problem 
Report. If this was a real problem, then we would have had multiple 
complaints about this. I myself run various nameservers that are being 
started the way you are mentioning. please check whether you have indeed 
up to date configuration files; ran mergemaster, check the logfiles to 
see what is being reported there, try to issue a /etc/rc.d/named 
faststart (Which is used by the startup script as far as I can remember) 
etc. Otherwise ask around on the questions@ mailinglist, for more 
information find that at the 
http://lists.freebsd.org/mailman/listinfo/freebsd-questions/