Report information
The Basics
Id:
46251
Status:
resolved
Priority:
Low/Low
Queue:

BugTracker
Version Fixed:
9.12.0, 9.11.3, 9.10.7, 9.9.12
Version Found:
(no value)
Versions Affected:
(no value)
Versions Planned:
(no value)
Priority:
P1 High
Severity:
S1 High
CVSS Score:
(no value)
CVE ID:
(no value)
Component:
BIND Server
Area:
bug

Dates
Created:Wed, 11 Oct 2017 07:10:08 -0400
Updated:Wed, 11 Oct 2017 17:29:14 -0400
Closed:Wed, 11 Oct 2017 17:29:14 -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.

To: bind9-public@isc.org
From: michal@isc.org
Date: Wed, 11 Oct 2017 13:10:07 +0200
Subject: Automated trust anchor updates may be delayed due to cached RRsets
named ignores a DNSKEY RRset received in an RFC 5011 refresh response if there is a non-expired, validated version of that DNSKEY RRset available in the cache. In other words, any changes published on the authoritative servers for a given trust point (e.g. adding new keys, revoking ones already published) are not acted upon by named until the TTL of the relevant cache entry expires.
Branch rt46251 fixes this issue by forcing the fetched DNSKEY RRset to replace the cached one despite having a lower trust level assigned. Please review. mkeys system test will be fixed in RT #45293.
Looks fine.
Because I'd really like to have this fix in the beta and code freeze is today, I've taken the liberty of merging this. 4771. [bug] When sending RFC 5011 refresh queries, disregard cached DNSKEY rrsets. [RT #46251] 9.12.0, 9.11.3, 9.10.7, 9.9.12