Antwort: logging on bind 9

[holger.honert at signal-iduna.de]

I'm happy with the following loggin statements in named.conf (BIND 9.3.0):
logging {
        channel named_log {
                file "/var/log/named.log" versions 5 size 5m;
                severity dynamic;
                print-category yes;
                print-severity yes;
                print-time yes;
                };
        channel query_log {
                file "/var/log/query.log" versions 5 size 5m;
                severity debug ;
                print-category yes;
                print-severity yes;
                print-time yes;
                };
        category default {
                named_log;
                };
        category queries {
                query_log;
                };
        category lame-servers {
                null;
                };
};

Maybe you adopt or change this to your needs!
 
Kind Regards/Freundlichen Gruß
 
Holger Honert
 
KOMN-97851
 
SIGNAL IDUNA Gruppe
Joseph-Scherer-Str. 3
 
44139 Dortmund
 
Phone: +49 231/135-4043
FAX: +49 231/135-2959
 
mailto: holger.honert at signal-iduna.de






Jim Pazarena <bind at ccstores.com>
Gesendet von: bind-users-bounce at isc.org
22.02.2005 00:40
 
An:           bind-users at isc.org
Kopie: 
Thema:        logging on bind 9


what command/directive can I place in my conf file so that
each and every dns request gets logged?

and further, is it possible to also log when a particular view
has been offered to the requester?

I want to determine both if (a) my two views are being
distributed correctly, and (b) determine why an internal request
for an internal FQDN  takes several seconds where an internal
request for an external address gets resolved instantly. I would
like to try and see what is happening to my internal request.

Thanks!
Jim