Mark Andrews afc4413862 Handle example3.db being modified in upforwd system test ... The zone file for example3 (ns1/example3.db) can be modified in the upforwd test as example3 is updated as part of the test. Whether the zone is written out or not by the end of the test is timing dependent. Rename ns1/example3.db to ns1/example3.db.in and copy it to ns1/example3.db in setup so we don't trigger post test changes checks.		2025-02-25 12:28:58 +11:00
..
ans4	Check read value in upforwd/ans4	2024-09-24 05:33:06 +00:00
CA	Add new upforwd system test	2022-10-27 12:22:23 +02:00
ns1	Handle example3.db being modified in upforwd system test	2025-02-25 12:28:58 +11:00
ns2	change allow-transfer default to "none"	2024-06-05 10:50:06 -07:00
ns3	Test that named checks maximum two keys for SIG(0)-signed messages	2024-06-10 17:35:39 +02:00
knowngood.after1	542. [func] Add allow-update-forwarding support.	2000-11-06 08:33:10 +00:00
knowngood.after1.example3	Add new upforwd system test	2022-10-27 12:22:23 +02:00
knowngood.after2	Test dynamic update forwarding when using a TLS-enabled primary	2022-09-28 09:36:24 +00:00
knowngood.after3	Test dynamic update forwarding when using a TLS-enabled primary	2022-09-28 09:36:24 +00:00
knowngood.before	542. [func] Add allow-update-forwarding support.	2000-11-06 08:33:10 +00:00
knowngood.before.example3	Add new upforwd system test	2022-10-27 12:22:23 +02:00
knowngood.ns2.before	checkpoint	2000-09-08 06:27:35 +00:00
prereq.sh	Reformat shell scripts with shfmt	2023-10-26 10:23:50 +02:00
setup.sh	Handle example3.db being modified in upforwd system test	2025-02-25 12:28:58 +11:00
tests.sh	Implement sig0key-checks-limit and sig0message-checks-limit	2025-02-20 13:35:14 +00:00
tests_sh_upforwd.py	Handle example3.db being modified in upforwd system test	2025-02-25 12:28:58 +11:00