Turning log on bind for troubleshooting

michoski michoski at cisco.com
Tue Nov 15 21:19:19 UTC 2011


Grab the BIND ARM for your version:

http://www.isc.org/software/bind/documentation

There it indirectly calls out that logging is it's own section (e.g. It
doesn't say "this is valid in options or views" like it does for many other
things)...  It is it's own stanza:

options {
};

controls {
};

acl {
};

[...]

logging {
        channel "config" {
                file "/var/log/config" versions 3 size 10485760;
                print-time yes;
                print-category yes;
        };
        channel "messages" {
                file "/var/log/messages" versions 3 size 10485760;
                print-time yes;
                print-category yes;
        };
        channel "security" {
                file "/var/log/security" versions 3 size 10485760;
                print-time yes;
                print-category yes;
        };
        channel "xfer" {
                file "/var/log/xfer" versions 3 size 10485760;
                print-time yes;
                print-category yes;
        };
        category "default" {
                "messages";
        };
        category "general" {
                "messages";
        };

[...]

};

On 11/15/11 11:49 AM, "Eduardo Bonsi" <beartcom at pacbell.net> wrote:

> Sebastian;
> 
> Thanks! I was looking at this log statement last night. I found two
> statements: Not sure what is the best one to debug.
> They are also not clear where to insert these statements:
> On options or some place else in the end of named.conf.
> 
> http://www.zytrax.com/books/dns/ch7/logging.html
> 
> logging{
>    channel simple_log {
>      file "/var/log/named/bind.log" versions 3 size 5m;
>      severity warning;
>      print-time yes;
>      print-severity yes;
>      print-category yes;
>    };
>    category default{
>      simple_log;
>    };
> };
> 
> ********************************************************
> http://www.netadmintools.com/art233.html
> 
> logging {
> category "default" { "debug"; };
> category "general" { "debug"; };
> category "database" { "debug"; };
> category "security" { "debug"; };
> category "config" { "debug"; };
> category "resolver" { "debug"; };
> category "xfer-in" { "debug"; };
> category "xfer-out" { "debug"; };
> category "notify" { "debug"; };
> category "client" { "debug"; };
> category "unmatched" { "debug"; };
> category "network" { "debug"; };
> category "update" { "debug"; };
> category "queries" { "debug"; };
> category "dispatch" { "debug"; };
> category "dnssec" { "debug"; };
> category "lame-servers" { "debug"; };
> channel "debug" {
> file "/tmp/nameddbg" versions 2 size 50m;
> print-time yes;
> print-category yes;
> };
> };
> 
> 
> 
> On 11/15/11 12:42 AM, Sebastian Tymków wrote:
>> Hi,
>> 
>> Look at this : http://www.zytrax.com/books/dns/ch7/logging.html
>> For troubleshooting I suggest using debug mode.
>> 
>> Best regards,
>> Sebastian
>> 
>> On Tue, Nov 15, 2011 at 9:13 AM, Eduardo Bonsi<beartcom at pacbell.net>  wrote:
>>> What is the best statement to insert on name.conf to generate logs for
>>> troubleshooting bind 9.x?
>>> 
>>> Thanks!
>>> 
>>> 
>>> 
>>> --
>>> BEARTCOMMUNICATIONS
>>> Eduardo Bonsi
>>> System - Network Admin
>>> beartcom at pacbell.net
>>> webmaster at beart.com
>>> _______________________________________________
>>> Please visit https://lists.isc.org/mailman/listinfo/bind-users to
>>> unsubscribe from this list
>>> 
>>> bind-users mailing list
>>> bind-users at lists.isc.org
>>> https://lists.isc.org/mailman/listinfo/bind-users
>>> 
>> 
> 

-- 
By nature, men are nearly alike;
by practice, they get to be wide apart.
        -- Confucius

https://opswiki.ironport.com/bin/view/Main/CoreServices
https://opswiki.ironport.com/bin/view/Main/IPv6OpsStrategy




More information about the bind-users mailing list