Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 30 Jul 2014 14:28:06 -0700
From:      Burton Sampley <>
Subject:   FreeBSD 10.0-R-p7 bind9.9 starting named on boot?
Message-ID:  <>

Next in thread | Raw E-Mail | Index | Archive | Help


After a very long absence, I have returned to FBSD for a project at home.  I started learning FBSD with 2.1.5R and moved on to other OS's around the 4.x-R days.

I have installed 10.0-R and updated to p-7.  I have installed Bind9.9 from ports and have configured a local domain (, which is doing exactly what I want/need it to do ... until I reboot.  It will not start automagically on reboot.  I have added and confirmed 'named_enable="YES" ' in /etc/rc.conf, but named is not running after a reboot.  I checked dmesg and /var/log/messages, but did not see any error messages for named. I can manually start named with "/usr/sbin/service named start" and it will run without issue, until I reboot.

I've followed the instructions in the handbook in sections 12.4 "Managing Services in FreeBSD" and 28.7 "Domain Name System (DNS)", which is clear-as-mud for FBSD-10 and Bind99 (not using unbound).  I also followed the instructions in section 28.8 "Apache HTTP Server", which successfully starts automagically on reboot.  I have also search the mail archives and have yet to find the magic combination of search terms.

At this point, I have exhausted all the resources I can think of, so it's time to try  I am officially stumped.  What am I missing???

Here's some of the things I've looked at:

root@fbsd:~ # /usr/bin/uname -a
FreeBSD 10.0-RELEASE-p7 FreeBSD 10.0-RELEASE-p7 #0: Tue Jul  8 06:37:44 UTC 2014  amd64
root@fbsd:~ #
root@fbsd:~ # /usr/sbin/service -e
root@fbsd:~ # /usr/sbin/service named rcvar
# named
#   (default: "")

root@fbsd:~ # /usr/sbin/service local_unbound rcvar
# local_unbound : local caching forwarding resolver
#   (default: "")

root@fbsd:~ # /usr/bin/more /etc/rc.conf
ifconfig_em0="inet <MY IP> netmask"
defaultrouter="<MY ROUTER>"
# Set dumpdev to "AUTO" to enable crash dumps, "NO" to disable
root@fbsd:~ #



Want to link to this message? Use this URL: <>