From owner-freebsd-questions@FreeBSD.ORG Sat Aug 23 18:26:07 2014 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E9061133 for ; Sat, 23 Aug 2014 18:26:06 +0000 (UTC) Received: from nm19-vm5.bullet.mail.ne1.yahoo.com (nm19-vm5.bullet.mail.ne1.yahoo.com [98.138.91.241]) by mx1.freebsd.org (Postfix) with ESMTP id AEAD83F17 for ; Sat, 23 Aug 2014 18:26:06 +0000 (UTC) Received: from [98.138.100.118] by nm19.bullet.mail.ne1.yahoo.com with NNFMP; 23 Aug 2014 18:23:30 -0000 Received: from [98.138.87.6] by tm109.bullet.mail.ne1.yahoo.com with NNFMP; 23 Aug 2014 18:23:29 -0000 Received: from [127.0.0.1] by omp1006.mail.ne1.yahoo.com with NNFMP; 23 Aug 2014 18:23:29 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 805748.12252.bm@omp1006.mail.ne1.yahoo.com Received: (qmail 95155 invoked by uid 60001); 23 Aug 2014 18:23:29 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1408818209; bh=rdK5MLsHkZ9EkRkBW6tsuu4QHmiOVxY6GZtcQXb83c4=; h=Message-ID:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=yqr4gSptDcWiYLGwpFue3hJ3Scbosbbe3N59gQcIpU3njP7VLrBhW7rq8JAz1crkX6AeIJpcieDQqvifTm0HxF50AQjuSsDltJhbuC6+qy45dlWRvA7/58tObM2sGpm1dheHoScV3TIVfTbBESfy2Los2UPk+je9HarKgjoPPqw= X-YMail-OSG: 71ZJuVYVM1k24kS5jqAd7S5OxixZ4WyKNXR_UrJ7s57pq2u uwuiTz340ZmywDUT321lcbtMX7CFizS8hyE4Uo7WSKGhyI_nbMorYK5EmtNW asc2_c1Z5QOJFYWh7eUN0_LYX6mDZLYSraXl99NimLWmIi_9.fpPh2LNDU_z rujh.9saEOOqAe5mzt2XJNvk8cIXf3VGtYnrdiuecwXINPyRJOdioXTTmO8f IAcWWzdO9GzM_.qjU6E21cIKMX0Nr_KfseNYli9Q7_FJmKWO.bSXMikIufCR cu90JmmqLoIVJZX50DZvXQUlvFP32Vb9c0PavndSc4uV6Wxj5k7rgHMLbx5c Ygc6a6VgWXwGCnBHb15ajnctWOFiCvUbArTbuBPohk5OufirOxoL3pn8t4o2 iub260JLXeM3j_dZjuqrLQDybepyDVI7vMdmqNhDBVs2Z3euGYDmeAAQKkta G1L9Fbn31RoQqA0qUQO59s3VMVy6jA0l_IDBHNIeIEWrFA8GB6zj060s4Qse Sa.tiM7DD5eKSqv6sR6ePGKpYLRHzuKX6DI47tig3vhPr0HouPYXm3oM3Rmp B.Lrj5viQk4.a2M9_8.65O5msLZuSEBH.nMrg0w-- Received: from [174.57.138.2] by web120305.mail.ne1.yahoo.com via HTTP; Sat, 23 Aug 2014 11:23:29 PDT X-Rocket-MIMEInfo: 002.001, UGF1bCwNCg0KVGhhbmsgeW91IGZvciB5b3VyIGhlbHAuICBJIGluc3RhbGxlZCBiaW5kIDkuOSBmcm9tIHRoZSBwb3J0cyBjb2xsZWN0aW9uIChpcyB0aGVyZSBhbnkgb3RoZXIgd2F5Pz8_KS4gIFRoZSBvbmx5IGNoYW5nZXMgSSBoYXZlIG1hZGUgdG8gdGhlIG5hbWVkLmNvbmYgZmlsZSBhcmUgdG8gYWRkIHRoZSBsb2dnaW5nIHNlY3Rpb24gYXMgeW91IGhhdmUgc3VnZ2VzdGVkLiAgVG8gbXkgYW1hemVtZW50LCBhZnRlciAyIGNvbnNlY3V0aXZlIHJlYm9vdHMsIG5hbWVkIGhhcyBzdGFydGVkIGNvcnJlY3QBMAEBAQE- X-Mailer: YahooMailClassic/713 YahooMailWebService/0.8.201.700 Message-ID: <1408818209.56025.YahooMailBasic@web120305.mail.ne1.yahoo.com> Date: Sat, 23 Aug 2014 11:23:29 -0700 From: Burton Sampley Subject: Re: FreeBSD 10.0-R-p7 bind9.9 starting named on boot? To: Paul Kraus In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: "questions@freebsd.org" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Aug 2014 18:26:07 -0000 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 wrote: Subject: Re: FreeBSD 10.0-R-p7 bind9.9 starting named on boot? To: "Burton Sampley" Cc: "questions@freebsd.org" Date: Thursday, August 21, 2014, 9:26 PM =20 On Aug 21, 2014, at 21:01, Burton Sampley via freebsd-questions 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 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