Matthijs Mekking 0d47f9f20f Use stale TTL as RRset TTL in dumpdb ...

It is more intuitive to have the countdown 'max-stale-ttl' as the
RRset TTL, instead of 0 TTL. This information was already available
in a comment "; stale (will be retained for x more seconds", but
Support suggested to put it in the TTL field instead.

(cherry picked from commit a83c8cb0af)

2021-04-13 10:59:17 +02:00

..

ans2

Add test for serve-stale /w fetch-limits

2021-02-08 16:07:43 +01:00

ns1

Change default stale-answer-client-timeout to off

2021-04-07 14:46:55 +02:00

ns3

Change default stale-answer-client-timeout to off

2021-04-07 14:46:55 +02:00

ns4

further tidying of primary/secondary terminology in system tests

2021-01-12 15:21:14 +01:00

ns5

Minor changes to serve-stale tests

2020-09-25 08:20:17 +02:00

.gitignore

…

clean.sh

Add system tests for stale-answer-client-timeout

2021-01-29 10:39:20 +01:00

prereq.sh

Ensure use of "echo_i" where possible

2020-10-22 12:15:15 +02:00

setup.sh

update all copyright headers to eliminate the typo

2020-09-14 16:50:58 -07:00

tests.sh

Use stale TTL as RRset TTL in dumpdb

2021-04-13 10:59:17 +02:00