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

People
Owner:
Nobody in particular
Requestors:
Stephen Morris <stephen@isc.org>(email delivery suspended)
Cc:
AdminCc:

BugTracker
Version Fixed:
(no value)
Version Found:
(no value)
Versions Affected:
(no value)
Versions Planned:
(no value)
Priority:
P2 Normal
Severity:
S3 Low
CVSS Score:
(no value)
CVE ID:
(no value)
Component:
BIND Server
Area:
test

Dates
Created:Fri, 20 Oct 2017 11:15:15 -0400
Updated:Tue, 31 Oct 2017 11:19:22 -0400
Closed:Tue, 31 Oct 2017 11:19:22 -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.

Date: Fri, 20 Oct 2017 15:15:15 +0000
From: stephen@isc.org
To: bind9-public@isc.org
I've reviewed the system tests for #40138: aggressive negative caching and feel that the following additional tests are required: * A check that "synth-from-dnssec no" disables the feature. * A check that "synth-fron-dnssec yes" in the configuration file enables the feature (none of configuration files in the test specify "synth-from-dnssec" - the all assume that the feature is enabled by default). * A check that the TTL of the cached NSEC records follow the recommendations in section 5.4 of RFC 8198, i.e. that the TTL of NSEC and NSEC3 records to match the SOA.MINIMUM field in the authority section of a negative response, if SOA.MINIMUM is smaller (if implemented: the recommendation is a SHOULD.) Also... * Please add a comment to the test (at the "sleep 1") explaining that the method by which the test checks that the answer is coming from cache is that after the sleep, it is expecting the TTL of the answers to be less than 3600. This is not immediately clear from the script.
Looks fine.
4778. [test] Improve synth-from-dnssec testing. [RT #46352]