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
..
startperf	Update the copyright information in all files in the repository	2022-01-11 09:05:02 +01:00
system	If refresh stale RRset times out, start stale-refresh-time	2022-10-05 08:20:48 +02:00
testdata/wire	move all optional tests from bin/tests to bin/tests/optional	2018-03-09 14:12:47 -08:00
.gitignore	Refactor TLSDNS module to work with libuv/ssl directly	2021-01-25 09:19:22 +01:00
convert-trs-to-junit.py	Auto-format Python files with black	2022-06-08 10:28:08 +02:00
Makefile.am	Fix JUnit test status generator for out-of-tree system tests	2022-09-22 15:20:23 +02:00
test_client.c	Update netmgr, tasks, and applications to use isc_loopmgr	2022-08-26 09:09:24 +02:00
test_server.c	Update netmgr, tasks, and applications to use isc_loopmgr	2022-08-26 09:09:24 +02:00
wire_test.c	DNS name compression does not depend on the EDNS version	2022-06-01 13:00:40 +01:00