BIND 10 #1938: why ZONEMGR_UNKNOWN_ZONE_NOTIFIED ?
BIND 10 Development
do-not-reply at isc.org
Mon Mar 11 07:58:46 UTC 2013
#1938: why ZONEMGR_UNKNOWN_ZONE_NOTIFIED ?
-------------------------------------+-------------------------------------
Reporter: jreed | Owner:
Type: defect | Status: new
Priority: medium | Milestone: Next-
Component: secondary | Sprint-Proposed
manager | Resolution:
Keywords: | CVSS Scoring:
Sensitive: 0 | Defect Severity: N/A
Sub-Project: DNS | Feature Depending on Ticket:
Estimated Difficulty: 5 | Add Hours to Ticket: 0
Total Hours: 0 | Internal?: 0
-------------------------------------+-------------------------------------
Changes (by shane):
* milestone: Previous-Sprint-Proposed => Next-Sprint-Proposed
Comment:
The issue with this being an ERROR is that an external user should not be
able to trivially cause an ERROR. An ERROR is something the administrator
should probably notice and do something about. A stray NOTIFY... not so
much.
So, there are two actions here:
1. Change the error level from ERROR to INFO
2. Put a check earlier (in b10-auth?) to avoid wasting system resources
and spamming up logs
--
Ticket URL: <http://bind10.isc.org/ticket/1938#comment:11>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list