1827197 Members
2676 Online
109716 Solutions
New Discussion

Filter named logs

 
SOLVED
Go to solution
Diego Balgera
Frequent Advisor

Filter named logs

Hi,

in bind 8.2.5 I set up a zone preventing anyone from accessing it (with the allow-query option), as follows:

zone "bogus" {
type master;
file "db.bogus";
allow-query { none; };
};

It works ok, but at every query an entry like the following appears in the syslog:

hostname named[17210]: denied query from [10.3.5.87].49371 for "xxxx.bogus"
IN

There are a lot of them, filling the file system very quickly. Do you know how can I stop producing such outputs for this entries, since I'm not interested in them?

Thank you in advance.
Best regards.
Diego.
3 REPLIES 3
Vijaya Kumar_3
Respected Contributor
Solution

Re: Filter named logs

I think bind has a logging and channel commands in named.conf file

logging {
category default { default_syslog; default_debug; };
category panic { default_syslog; default_stderr; };
category packet { default_debug; };
category eventlib { default_debug; };
};


You may need to change the default category to null channel.

Check it out here:

http://triton.process.com/bind-docs/logging.html

Vijay
Known is a drop, unknown is ocean - visit me at http://vijay.theunixplace.com
Kevin Wright
Honored Contributor

Re: Filter named logs

For Bind 8, your logging category is security I think. You will have to redefine this category in named.conf.
Diego Balgera
Frequent Advisor

Re: Filter named logs

Thank you to everyone for your valuable suggestions.
The issue was solved configuring logging as follows:

logging {
category security { null; };
};

Thank you again!
Diego.