shutting up logs

Mike Hoskins (michoski) michoski at cisco.com
Fri May 15 00:52:40 UTC 2015


Another option might be changing 'file' to 'syslog' then using stuff like
":msg, contains, 'skipping nameserver' stop" (or whatever pattern you want
to match) in your rsyslog configuration.

http://www.rsyslog.com/doc/rsyslog_conf_filter.html

-----Original Message-----
From: Reindl Harald <h.reindl at thelounge.net>
Organization: the lounge interactive design
Date: Thursday, May 14, 2015 at 8:44 PM
To: "bind-users at lists.isc.org" <bind-users at lists.isc.org>
Subject: Re: shutting up logs

>
>
>Am 15.05.2015 um 02:01 schrieb Nick Edwards:
>>   skipping nameserver 'ns5.concord.org' because it is a CNAME, while
>> resolving '210.128-25.119.138.63.in-addr.arpa/PTR'
>>
>> I have logs grow by about 30 megs a day with pretty much only this in
>> it (of course not always same remote server), how do I shut this up ?
>>
>> My logging statments are
>>
>> logging {
>>          category lame-servers { null; };
>>          category edns-disabled { null; };
>>          category client { null; };
>>          category dnssec { null; };
>>          //      channel log_queries { file "/tmp/debug_query.log";
>> print-category yes; };
>>          //      category queries { log_queries; };
>> };
>
>you can't shut up specific messages
>but you can limit the log file sizes
>
>logging
>{
>  channel default_log
>  {
>   file                 "data/named.log" versions 0 size 1m;
>   severity             dynamic;
>   print-time           yes;
>   print-category       yes;
>  };
>  channel transfer_log
>  {
>   file                 "data/transfer.log" versions 0 size 1m;
>   severity             dynamic;
>   print-time           yes;
>   print-category       yes;
>  };
>  channel rate_limit_log
>  {
>   file                 "data/rate_limit.log" versions 0 size 1m;
>   severity             dynamic;
>   print-time           yes;
>   print-category       yes;
>  };
>  channel lame_servers_log
>  {
>   file                 "data/lame_servers.log" versions 0 size 1m;
>   severity             dynamic;
>   print-time           yes;
>   print-category       yes;
>  };
>  channel query_errors_log
>  {
>   file                 "data/query_errors.log" versions 0 size 1m;
>   severity             dynamic;
>   print-time           yes;
>   print-category       yes;
>  };
>
>  category default      {default_log;};
>  category resolver     {default_log;};
>  category security     {default_log;};
>  category xfer-in      {transfer_log;};
>  category xfer-out     {transfer_log;};
>  category config       {default_log;};
>  category queries      {default_log;};
>  category notify       {default_log;};
>  category database     {default_log;};
>  category rate-limit   {rate_limit_log;};
>  category lame-servers {lame_servers_log;};
>  category query-errors {query_errors_log;};
>};
>



More information about the bind-users mailing list