Matthijs Mekking e6e13c3e62 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 86a80e723f)		2022-12-06 13:51:07 +00:00
..
bind9	Update sources to Clang 15 formatting	2022-11-29 10:30:34 +01:00
dns	Don't log "final reference detached" on INFO level	2022-11-30 11:51:29 +01:00
irs	Update sources to Clang 15 formatting	2022-11-29 10:30:34 +01:00
isc	Update sources to Clang 15 formatting	2022-11-29 10:30:34 +01:00
isccc	Update sources to Clang 15 formatting	2022-11-29 10:30:34 +01:00
isccfg	Update sources to Clang 15 formatting	2022-11-29 10:30:34 +01:00
ns	Consider non-stale data when in serve-stale mode	2022-12-06 13:51:07 +00:00
win32/bindevt	Update the copyright information in all files in the repository	2022-01-11 12:22:09 +01:00
.gitignore	added gitignore, removed cvsignore	2012-03-03 23:10:05 -08:00
Kyuafile	Update the copyright information in all files in the repository	2022-01-11 12:22:09 +01:00
Makefile.in	Update the copyright information in all files in the repository	2022-01-11 12:22:09 +01:00