From owner-freebsd-questions@FreeBSD.ORG Fri Aug 22 01:26:09 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 92369DBA for ; Fri, 22 Aug 2014 01:26:09 +0000 (UTC) Received: from mail-qc0-f177.google.com (mail-qc0-f177.google.com [209.85.216.177]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4D45F3153 for ; Fri, 22 Aug 2014 01:26:08 +0000 (UTC) Received: by mail-qc0-f177.google.com with SMTP id x13so10057145qcv.8 for ; Thu, 21 Aug 2014 18:26:02 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=1ay2lusA7oEwsawkpZ/vJ1oLYkE/5GLbJW/9J7RuHzI=; b=WZEyTEVaqKfe9xAxqxYck8GY66zC5TfPzzbn9u7epVg/DBHUiNoD7qugEX4zL7GZ+j ES5qcO9cwfvm7x5TFuyn+kXCtdAVTeLU1Bua92NsTt9Y7f+1Trz1dzJvqYi3O+oB/ecH FskCzwSZWxKIxjeiIxAoeKPJ14T25UxwwJdLAWEw1nzu+KT5OiUcDU205lHv+QHGwk+G nUmm+FnPo0XKqX41KK9fougHwOTceeMIK3DW23sqobs54nW1SuRGPiYkkPb9jcDGZ35f 2udKV+C1kpOgtHhP60etjGJBF0qtg5ptTGocyZUbkCSH9kr7XiEVnQnst/4DjD6W2nFA C+6w== X-Gm-Message-State: ALoCoQmg1WAwJV8ovq44D/LuaK1br4yHMHzaXZQXtnuP5QV+0bVZY1KNOAHmG7Wc/3p5oWCEMz6L X-Received: by 10.140.32.3 with SMTP id g3mr3164228qgg.13.1408670762764; Thu, 21 Aug 2014 18:26:02 -0700 (PDT) Received: from [192.168.2.65] ([96.236.21.80]) by mx.google.com with ESMTPSA id y70sm31698327qgd.3.2014.08.21.18.26.01 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 21 Aug 2014 18:26:01 -0700 (PDT) Subject: Re: FreeBSD 10.0-R-p7 bind9.9 starting named on boot? Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Content-Type: text/plain; charset=windows-1252 From: Paul Kraus In-Reply-To: <1408669306.20048.YahooMailAndroidMobile@web120306.mail.ne1.yahoo.com> Date: Thu, 21 Aug 2014 21:26:01 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: References: <1408669306.20048.YahooMailAndroidMobile@web120306.mail.ne1.yahoo.com> To: Burton Sampley X-Mailer: Apple Mail (2.1878.6) 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: Fri, 22 Aug 2014 01:26:09 -0000 On Aug 21, 2014, at 21:01, Burton Sampley via freebsd-questions = 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 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