Files
bind9/bin/tests/system/kasp
Matthijs Mekking a36257ea60 Fix some intermittent kasp failures
When calling "rndc dnssec -checkds", it may take some milliseconds
before the appropriate changes have been written to the state file.
Add retry_quiet mechanisms to allow the write operation to finish.

Also retry_quiet the check for the next key event. A "rndc dnssec"
command may trigger a zone_rekey event and this will write out
a new "next key event" log line, but it may take a bit longer than
than expected in the tests.

(cherry picked from commit 82d667e1d5)
2021-03-22 15:35:22 +01:00
..
2021-03-17 11:12:48 +01:00
2021-02-03 08:41:00 +01:00
2020-10-07 14:14:14 +02:00
2021-03-22 15:35:22 +01:00

Copyright (C) Internet Systems Consortium, Inc. ("ISC")

See COPYRIGHT in the source root or https://isc.org/copyright.html for terms.

The test setup for the KASP tests.

ns1 is reserved for the root server.

ns2 is running primary service for ns3.

ns3 is an authoritative server for the various test domains.

ns4 and ns5 are authoritative servers for various test domains related to views.

ns6 is an authoritative server that tests changes in dnssec-policy (algorithm
rollover).