Report information
The Basics
Id:
46277
Status:
new
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:
9.12.0b1
Versions Affected:
(no value)
Versions Planned:
9.12.1
Priority:
P2 Normal
Severity:
S3 Low
CVSS Score:
(no value)
CVE ID:
(no value)
Component:
BIND Server
Area:
test

Dates
Created:Fri, 13 Oct 2017 12:39:45 -0400
Updated:Thu, 11 Jan 2018 14:12:31 -0500
Closed:Not set



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: Extend serve-stale system test
To: bind9-public@isc.org
From: stephen@isc.org
Date: Fri, 13 Oct 2017 16:39:45 +0000
The serve-stale system test should be extended to: 1. Check that if "serve-stale-enabled" is explicitly set to "no" in the configuration file, the serving of stale records is disabled. (At present, the tests check 'serve-stale-enabled yes" and the default when serve-stale-enabled is not specified). 2. Check that if a record is stale, then before the stale record is returned, upstream queries are made. 3. Check that the TTL of the record returned is that set by the stale-answer-ttl parameter. (This should check that the stale-answer-ttl value is used regardless of whether the TTL of the record is less than greater than this value). 4. Check that the max-stale-ttl value does cap the amount of time for which the stale record is served. 5. Check that if a record is stale (and is served) then if the authoritative server subsequently comes back but the record is changed, the new value is returned. This should check that an appropriate response is returned for: a) A different RDATA b) An NXDOMAIN response from the server c) A NODATA response from the server