logging

BOG junk at 1command.com
Tue Aug 10 09:22:35 UTC 2004


Greetings to all the previous logging posts,

The following should answer all those questions:

options {
	directory "/path/to/log/file";
	statistics-file "logfile.name";
	memstatistics-file "logfile.name";
	datasize 5M;
};

logging {
	channel specific_debug {
		file "logfile.name";
		severity debug 3;
		print-time yes;
		print-category yes;
		print-severity yes;
};

category default { specific_debug; };
category update { specific_debug; };
category packet { specific_debug; };
category notify { specific_debug; };
category default { specific_debug; };
category queries { specific_debug; };
category xfer-in { specific_debug; };
category xfer-out { specific_debug; };
category security { specific_debug; };
category os { specific_debug; };


Please note that /path/to/log/file should be something like:
/etc/namedb (for UNIXish OS) and something like:
c:\winnt\system32\dns (for WinNT systems). These are NOT absolute. You
can pretty much place your log files anywhere. However, you will probably
wish to keep it somewhere near your zone files. Also note that: log.file
(noted above) should be replaced by whatever name you wish to call your
Log File. I simply used that name so as to be easy to understand.

Best wishes,
 Chris


phn at icke-reklam.ipsec.nu wrote in message news:<cdouql$10e7$1 at sf1.isc.org>...
> Bryan Irvine <sparctacus at gmail.com> wrote:
> > I'm switching over to a new primary DNS server at another location and
> > I want to log all the dns requests to a .txt style log file (at least
> > for now) so I can monitor who and how many connections are being moved
> > over to it.
>  
> > Is there a way to log that detailed?
> 
> rndc querylog
> 
> Your normal log rotation will take care of wrapping logfiles.
> 
> > --Bryan


More information about the bind-users mailing list