Matthijs Mekking 0681b15225 If refresh stale RRset times out, start stale-refresh-time ... The previous commit failed some tests because we expect that if a fetch fails and we have stale candidates in cache, the stale-refresh-time window is started. This means that if we hit a stale entry in cache and answering stale data is allowed, we don't bother resolving it again for as long we are within the stale-refresh-time window. This is useful for two reasons: - If we failed to fetch the RRset that we are looking for, we are not hammering the authoritative servers. - Successor clients don't need to wait for stale-answer-client-timeout to get their DNS response, only the first one to query will take the latency penalty. The latter is not useful when stale-answer-client-timeout is 0 though. So this exception code only to make sure we don't try to refresh the RRset again if it failed to do so recently.		2022-10-05 08:20:48 +02:00
..
bind9	Add extended DNS error configuration option for RPZ zones	2022-08-31 08:56:03 +00:00
dns	Add a case-insensitive option directly to siphash 2-4 implementation	2022-10-04 10:32:40 +02:00
irs	Move all the unit tests to /tests/<libname>/	2022-05-28 14:53:02 -07:00
isc	Add a case-insensitive option directly to siphash 2-4 implementation	2022-10-04 10:32:40 +02:00
isccc	Convert DST_ALG defines to enum and group HMAC algorithms	2022-09-27 16:54:36 +02:00
isccfg	flag "random-device" as ancient	2022-09-14 09:36:58 -07:00
ns	If refresh stale RRset times out, start stale-refresh-time	2022-10-05 08:20:48 +02: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