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

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

Re: shutting up logs

...@thelounge.net Organization: the lounge interactive design Date: Thursday, May 14, 2015 at 8:44 PM To: bind-users@lists.isc.org 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

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

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

shutting up logs

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 {