Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 05 Aug 2011 09:15:21 -0700
From:      Drew Tomlinson <drew@mykitchentable.net>
To:        freebsd-questions@freebsd.org
Subject:   Help with Bind Weirdness & Logging
Message-ID:  <4E3C1719.7030509@mykitchentable.net>

Next in thread | Raw E-Mail | Index | Archive | Help
I'm running bind 9.3.5 and have been running some version of Bind for 
years.  The  purpose of this server is to resolve for my home LAN and to 
do regular queries for things outside my LAN.

Just recently, I noticed that my server can't resolve for some names.  
The ones I've noticed are for Microsoft domains, specifically 
go.microsoft.com and time.windows.com.  For example:

# dig go.microsoft.com

; <<>> DiG 9.3.5-P2 <<>> go.microsoft.com
;; global options:  printcmd
;; connection timed out; no servers could be reached

Yet if I ask my ISP's server, I get resolution:

# dig @66.60.130.158 go.microsoft.com

; <<>> DiG 9.3.5-P2 <<>> @66.60.130.158 go.microsoft.com
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40919
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;go.microsoft.com.              IN      A

;; ANSWER SECTION:
go.microsoft.com.       2364    IN      CNAME   www.go.microsoft.akadns.net.
www.go.microsoft.akadns.net. 462 IN     A       64.4.11.160

;; Query time: 39 msec
;; SERVER: 66.60.130.158#53(66.60.130.158)
;; WHEN: Fri Aug  5 09:02:56 2011
;; MSG SIZE  rcvd: 91

But for all other domains I've tried, DNS resolution works just fine 
from my server.  Here's an example:

# dig yahoo.com

; <<>> DiG 9.3.5-P2 <<>> yahoo.com
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 60582
;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 7, ADDITIONAL: 2

;; QUESTION SECTION:
;yahoo.com.                     IN      A

;; ANSWER SECTION:
yahoo.com.              21600   IN      A       69.147.125.65
yahoo.com.              21600   IN      A       72.30.2.43
yahoo.com.              21600   IN      A       98.137.149.56
yahoo.com.              21600   IN      A       209.191.122.70
yahoo.com.              21600   IN      A       67.195.160.76

;; AUTHORITY SECTION:
yahoo.com.              172800  IN      NS      ns5.yahoo.com.
yahoo.com.              172800  IN      NS      ns6.yahoo.com.
yahoo.com.              172800  IN      NS      ns8.yahoo.com.
yahoo.com.              172800  IN      NS      ns1.yahoo.com.
yahoo.com.              172800  IN      NS      ns2.yahoo.com.
yahoo.com.              172800  IN      NS      ns3.yahoo.com.
yahoo.com.              172800  IN      NS      ns4.yahoo.com.

;; ADDITIONAL SECTION:
ns6.yahoo.com.          172800  IN      A       202.43.223.170
ns8.yahoo.com.          172800  IN      A       202.165.104.22

;; Query time: 236 msec
;; SERVER: 192.168.1.4#53(192.168.1.4)
;; WHEN: Fri Aug  5 09:05:32 2011
;; MSG SIZE  rcvd: 265

So to try and diagnose this, I investigated logging.  My 
/var/named/etc/namedb/named.conf file had this default logging section:


logging {
         category default         { default_syslog; default_debug; };
         category security        { default_syslog; default_debug; };
         category xfer-in         { default_syslog; default_debug; };
         category xfer-out        { default_syslog; default_debug; };
         category notify          { default_syslog; default_debug; };
         category update          { default_syslog; default_debug; };
         category update-security { default_syslog; default_debug; };
         category lame-servers    { default_syslog; default_debug; };
};

But I couldn't find any logging in any of my log files like 
/var/log/messages or /var/log/all.log and there were no files in 
/var/named/var/log.  I did some Googling, commented out the above, added 
the section below, and restarted named:

logging{
   channel simple_log {
     file "/var/log/named.log" versions 3 size 5m;
     severity warning;
     print-time yes;
     print-severity yes;
     print-category yes;
   };
   category default      { simple_log; };
   category network      { simple_log; };
   category queries      { simple_log; };
   category resolver     { simple_log; };
   category general      { simple_log; };
};

This did create a log file called /var/named/var/log/named.log.  However 
I'm not getting much info in this log.  I only get this text upon restart:

05-Aug-2011 07:39:22.583 general: error: the working directory is not 
writable

What must I do to get more detailed logging that might help diagnose 
this problem?  Or better yet, what is going on with my Bind installation? ;)

Cheers,

Drew

-- 
Like card tricks?

Visit The Alchemist's Warehouse to
learn card magic secrets for free!

http://alchemistswarehouse.com





Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?4E3C1719.7030509>