BIND 10 #2910: RESOLVER_QUERY_DROPPED and RESOLVER_QUERY_REJECTED should not be INFO
BIND 10 Development
do-not-reply at isc.org
Thu Apr 11 16:40:29 UTC 2013
#2910: RESOLVER_QUERY_DROPPED and RESOLVER_QUERY_REJECTED should not be INFO
---------------------------------+-----------------------------------------
Reporter: jreed | Owner:
Type: defect | Status: new
Priority: medium | Milestone: New Tasks
Component: resolver | Resolution:
Keywords: | CVSS Scoring:
Sensitive: 0 | Defect Severity: N/A
Sub-Project: DNS | Feature Depending on Ticket:
Estimated Difficulty: 0 | Add Hours to Ticket: 0
Total Hours: 0 | Internal?: 0
---------------------------------+-----------------------------------------
Comment (by jinmei):
BIND 9 seems to log it at the log level:
{{{#!c
ns_client_log(client, DNS_LOGCATEGORY_SECURITY,
NS_LOGMODULE_QUERY, ISC_LOG_INFO,
"%s denied", msg);
ns_client_log(client, DNS_LOGCATEGORY_SECURITY,
NS_LOGMODULE_QUERY, ISC_LOG_INFO,
"query-on denied");
}}}
and allow the user to suppress it via the category configuration.
Not necessarily to say we should definitely do the same, but it seems
to suggest that what we should do doesn't seem to be so obvious.
--
Ticket URL: <https://bind10.isc.org/ticket/2910#comment:1>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list