Date: Thu, 21 Aug 2014 21:26:01 -0400 From: Paul Kraus <paul@kraus-haus.org> To: Burton Sampley <bsmply@yahoo.com> Cc: "questions@freebsd.org" <questions@freebsd.org> Subject: Re: FreeBSD 10.0-R-p7 bind9.9 starting named on boot? Message-ID: <AEC8845C-EE77-490E-9728-C5CFAA9D3339@kraus-haus.org> In-Reply-To: <1408669306.20048.YahooMailAndroidMobile@web120306.mail.ne1.yahoo.com> References: <1408669306.20048.YahooMailAndroidMobile@web120306.mail.ne1.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Aug 21, 2014, at 21:01, Burton Sampley via freebsd-questions =
<freebsd-questions@freebsd.org> wrote:
> This issue is still unresolved. Does anyone else have any =
suggestions?
Did you install bind 9.9 from ports or packages or build it yourself ?
I am running 10p7 with bind 9.10 installed from ports with no issues:
root@freebsd2:~ # uname -a
FreeBSD freebsd2 10.0-RELEASE-p7 FreeBSD 10.0-RELEASE-p7 #0: Tue Jul 8 =
06:37:44 UTC 2014 =
root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64
root@freebsd2:~ # pkg info | grep bind
bind910-9.10.0P2_3 BIND 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=93snip"
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
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):
logging {
// we define channels as locations for logs to go ...
channel "syslog" {
syslog daemon;
severity info;
};
channel "info" {
file "/var/log/named/named.info" versions 10 size 1m;
severity info;
print-category yes;
print-severity yes;
print-time yes;
};
// now we define the things to log and which channel to send =
them to
category "default" {
syslog;
info;
};
};
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 =93debug=94 on the channel (I would not =
do that on the syslog channel) for even more detailed logs.
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.
--
Paul Kraus
paul@kraus-haus.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AEC8845C-EE77-490E-9728-C5CFAA9D3339>