Date: Sat, 23 Aug 2014 11:23:29 -0700 From: Burton Sampley <bsmply@yahoo.com> To: Paul Kraus <paul@kraus-haus.org> Cc: "questions@freebsd.org" <questions@freebsd.org> Subject: Re: FreeBSD 10.0-R-p7 bind9.9 starting named on boot? Message-ID: <1408818209.56025.YahooMailBasic@web120305.mail.ne1.yahoo.com> In-Reply-To: <AEC8845C-EE77-490E-9728-C5CFAA9D3339@kraus-haus.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Paul,
Thank you for your help. I installed bind 9.9 from the ports collection (i=
s there any other way???). The only changes I have made to the named.conf =
file are to add the logging section as you have suggested. To my amazement=
, after 2 consecutive reboots, named has started correctly. I'm stumped as=
to why it would not start on boot before now, but I will not complain as l=
ong as it remains consistent.
root@fbsd:/var/log/named # /usr/sbin/pkg info | /usr/bin/grep bind
bind99-9.9.5P1_2 BIND DNS suite with updated DNSSEC and DNS64
dbus-glib-0.100.2_1 GLib bindings for the D-BUS messaging system
root@fbsd:/var/log/named # /usr/bin/uname -a
FreeBSD fbsd.chicken.fish 10.0-RELEASE-p7 FreeBSD 10.0-RELEASE-p7 #0: Tue J=
ul 8 06:37:44 UTC 2014 root@amd64-builder.daemonology.net:/usr/obj/usr=
/src/sys/GENERIC amd64
root@fbsd:/var/log/named #
Regards,
-Burton
--------------------------------------------
On Thu, 8/21/14, Paul Kraus <paul@kraus-haus.org> wrote:
Subject: Re: FreeBSD 10.0-R-p7 bind9.9 starting named on boot?
To: "Burton Sampley" <bsmply@yahoo.com>
Cc: "questions@freebsd.org" <questions@freebsd.org>
Date: Thursday, August 21, 2014, 9:26 PM
=20
On Aug 21, 2014, at
21:01, Burton Sampley via freebsd-questions <freebsd-questions@freebsd.org=
>
wrote:
=20
> This issue is
still unresolved.=C2=A0 Does anyone else have any
suggestions?
=20
Did you
install bind 9.9 from ports or packages or build it yourself
?
=20
I am running 10p7 with
bind 9.10 installed from ports with no issues:
=20
root@freebsd2:~ # uname
-a
FreeBSD freebsd2 10.0-RELEASE-p7 FreeBSD
10.0-RELEASE-p7 #0: Tue Jul=C2=A0 8 06:37:44 UTC 2014=C2=A0
=C2=A0=C2=A0=C2=A0root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/=
GENERIC=C2=A0
amd64
root@freebsd2:~ # pkg
info | grep bind
bind910-9.10.0P2_3=C2=A0 =C2=A0 =C2=A0
=C2=A0 =C2=A0 =C2=A0=C2=A0=C2=A0BIND DNS suite with updated DNSSEC and
DNS64
root@freebsd2:~ # cat
/etc/rc.conf=20
hostname=3D"FreeBSD2"
ifconfig_bge0=3D"inet snip netmask
snip"
defaultrouter=3D=E2=80=9Csnip"
zfs_enable=3D"YES"
sshd_enable=3D"YES"
ntpd_enable=3D"YES"
powerd_enable=3D"YES"
dumpdev=3D"AUTO"
named_enable=3D"YES"
dhcpd_enable=3D"YES"
#
# Disable Sendmail
sendmail_enable=3D"NO"
sendmail_submit_enable=3D"NO"
sendmail_outbound_enable=3D"NO"
sendmail_msp_queue_enable=3D"NO"
# Enable Postfix
postfix_enable=3D"YES"
root@freebsd2:~ #=20
=20
I have extensive bind logging
configured (a holdover from when I used to manage DNS
servers for a medium size company, a few thousand users), so
I have detailed logs in /var/log/named. You may want to
configure logging in named.conf as I have found that syslog
does not always catch the bind startup messages you need to
troubleshoot. Try this for troubleshooting (add to
named.conf):
=20
logging {
=C2=A0 =C2=A0 =C2=A0 =C2=A0 // we define channels as locations
for logs to go ...
=C2=A0 =C2=A0 =C2=A0 =C2=A0 channel
"syslog" {
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0
syslog daemon;
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0
severity info;
=C2=A0 =C2=A0 =C2=A0 =C2=A0 };
=C2=A0 =C2=A0 =C2=A0 =C2=A0 channel "info" {
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 file
"/var/log/named/named.info" versions 10 size
1m;
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 severity
info;
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 print-category
yes;
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 print-severity
yes;
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 print-time
yes;
=C2=A0 =C2=A0 =C2=A0 =C2=A0 };
=C2=A0 =C2=A0 =C2=A0
=C2=A0 // now we define the things to log and which channel to
send them to
=C2=A0 =C2=A0 =C2=A0 =C2=A0 category
"default" {
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0
=C2=A0 syslog;
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 info;
=C2=A0 =C2=A0 =C2=A0 =C2=A0 };
};
=20
That should put everything in
both syslog and /var/log/named/named.info (make sure the
/var/log/named directory is writable by the named user). You
can crank the severity up to =E2=80=9Cdebug=E2=80=9D on the channel (I
would not do that on the syslog channel) for even more
detailed logs.
=20
You can also
try to start named with the -f -d <n> options (from
the command line). -f prevents to from detaching and
demonizing, -d sets the debug level (higher numbers are more
details debug info). I know your problem is a startup one,
but I think you might find an odd error that is not a
problem after the system has stabilized but may be an issue
during the boot process.
=20
--
Paul Kraus
paul@kraus-haus.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1408818209.56025.YahooMailBasic>