Matthijs Mekking 271bc20b1c Consider non-stale data when in serve-stale mode ... With 'stale-answer-enable yes;' and 'stale-answer-client-timeout off;', consider the following situation: A CNAME record and its target record are in the cache, then the CNAME record expires, but the target record is still valid. When a new query for the CNAME record arrives, and the query fails, the stale record is used, and then the query "restarts" to follow the CNAME target. The problem is that the query's multiple stale options (like DNS_DBFIND_STALEOK) are not reset, so 'query_lookup()' treats the restarted query as a lookup following a failed lookup, and returns a SERVFAIL answer when there is no stale data found in the cache, even if there is valid non-stale data there available. With this change, query_lookup() now considers non-stale data in the cache in the first place, and returns it if it is available. (cherry picked from commit 91a1a8efc5)		2023-01-09 14:26:02 +01:00
..
bind9	Update sources to Clang 15 formatting	2022-11-29 09:14:07 +01:00
dns	Consider non-stale data when in serve-stale mode	2023-01-09 14:26:02 +01:00
irs	Move all the unit tests to /tests/<libname>/	2022-05-31 12:06:00 +02:00
isc	tlsctx_client_session_cache_new() -> tlsctx_client_session_create()	2022-12-23 13:58:14 +02:00
isccc	Update sources to Clang 15 formatting	2022-11-29 09:14:07 +01:00
isccfg	Deprecate alt-transfer-source and companions	2022-12-01 08:14:42 +01:00
ns	Consider non-stale data when in serve-stale mode	2023-01-09 14:26:02 +01:00
.gitignore	The isc/platform.h header has been completely removed	2021-07-06 05:33:48 +00:00
Makefile.am	move samples/resolve.c to bin/tests/system	2021-04-16 14:29:43 +02:00