Re: shutting up logs
Am 15.05.2015 um 08:56 schrieb G.W. Haywood: Hi there, On Fri, 15 May 2015, Reindl Harald wrote: 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 ? > ... you can't ... You can. If you use syslog-ng you can do anything you like, for example you can filter messages using regular expressions. If there wasn't a syslog-ng, I'd have to write one that's a completly different thing while rsyslog can do the same, but that don't stop named to produce the message, it's just thrown away by the syslog-daemon while the OP didn't say he forwards logs to syslogd signature.asc Description: OpenPGP digital signature ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: shutting up logs
Hi there, On Fri, 15 May 2015, Reindl Harald wrote: 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 ? > ... you can't ... You can. If you use syslog-ng you can do anything you like, for example you can filter messages using regular expressions. If there wasn't a syslog-ng, I'd have to write one. -- 73, Ged. ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: shutting up logs
You can silence the messages by sending category cname to null, but
have you tried contact the zone administrator postmas...@concord.org
to get the delegation fixed. One of the points of logging the
configuration error is to make it visible so it can be fixed. The
second reason is to have evidence of why a lookup is failing.
128-25.119.138.63.in-addr.arpa. 3600 IN NS ns5.concord.org.
128-25.119.138.63.in-addr.arpa. 3600 IN NS ns6.concord.org.
;; Received 106 bytes from 66.155.216.121#53(ns1.paetec.net) in 409 ms
128-25.119.138.63.in-addr.arpa. 10800 IN NS cable.concord.org.
128-25.119.138.63.in-addr.arpa. 10800 IN NS barney.concord.org.
128-25.119.138.63.in-addr.arpa. 10800 IN NS dns1-bos.paetec.net.
;; Received 144 bytes from 63.138.119.200#53(ns6.concord.org) in 407 ms
Alternatively complain the the parent zone (d...@paetec.net) about
the delegation being broken and request that it be fixed / removed
as it is causing operational issues as per RFC 1034.
Mark
In message
, Nick
Edwards writes:
> 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; };
> };
>
> TIA
> ___
> Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
> from this list
>
> bind-users mailing list
> bind-users@lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
Re: shutting up logs
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
Organization: the lounge interactive design
Date: Thursday, May 14, 2015 at 8:44 PM
To: "bind-users@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;};
>};
>
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
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;};
};
signature.asc
Description: OpenPGP digital signature
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
