Report information
The Basics
Id:
45354
Status:
resolved
Priority:
Medium/Medium
Queue:

People
BugTracker
Version Fixed:
9.9.11, 9.10.6, 9.10.6-S1, 9.11.2, 9.12.0
Version Found:
(no value)
Versions Affected:
(no value)
Versions Planned:
9.9.11, 9.10.6, 9.11.2, 9.9.11-S1, 9.10.6-S1
Priority:
P2 Normal
Severity:
S3 Low
CVSS Score:
(no value)
CVE ID:
(no value)
Component:
(no value)
Area:
feature

Dates
Created:Wed, 07 Jun 2017 17:51:24 -0400
Updated:Sat, 29 Jul 2017 00:01:41 -0400
Closed:Tue, 27 Jun 2017 13:54:47 -0400



This bug tracker is no longer active.

Please go to our Gitlab to submit issues (both feature requests and bug reports) for active projects maintained by Internet Systems Consortium (ISC).

Due to security and confidentiality requirements, full access is limited to the primary maintainers.

Subject: improve logging of 5011 events
From https://wiki.isc.org/bin/view/Main/RootKeyRollImprovements: BIND should log all relevant events related to managed key rollovers, including: - Detection of new keys - Keys being added to the Trust Anchor set (i.e. after hold-time timer) - Key deletions Minimize logging of missing keys: IANA plan to temporarily publish the new KSK and leave it published for the RFC 5011 “add” hold-down time period (30 days) and then remove it from the zone again without revoking it. BIND will add the key to the list of trust anchors, and leave it there, but warns that there is a mismatch between the zone contents and the trust anchor list. Instead, this should be considered “business as usual” and not generate excessive warning messages.