HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Filter named logs
Operating System - HP-UX
1827204
Members
2498
Online
109716
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-15-2004 09:27 PM
02-15-2004 09:27 PM
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.
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.
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-15-2004 09:35 PM
02-15-2004 09:35 PM
Solution
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
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-16-2004 08:06 AM
02-16-2004 08:06 AM
Re: Filter named logs
For Bind 8, your logging category is security I think. You will have to redefine this category in named.conf.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-16-2004 08:36 PM
02-16-2004 08:36 PM
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.
The issue was solved configuring logging as follows:
logging {
category security { null; };
};
Thank you again!
Diego.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP