Aram Sargsyan 797d865121 Fix the notify system test after the newly applied timeout value ... Since notify messages now use the configured 'tcp-initial-timeout' connect timeout value, the existing "checking notify retries expire within 30 seconds" check in the "notify" system test is failing. Set the 'tcp-initial-timeout' option for ns3 to the previously hardcoded value of 15 seconds for the test to pass successfully.		2025-04-23 17:03:05 +00:00
..
CA	Use correct certificates for TLS notify tests	2024-10-24 13:39:59 +11:00
ns1	check behaviour with invalid notify-source-v6 address	2024-04-24 10:12:42 +10:00
ns2	Unify parental-agents, primaries to remote-servers	2024-12-13 08:50:02 +01:00
ns3	Fix the notify system test after the newly applied timeout value	2025-04-23 17:03:05 +00:00
ns4	change allow-transfer default to "none"	2024-06-05 10:50:06 -07:00
ns5	change allow-transfer default to "none"	2024-06-05 10:50:06 -07:00
.gitignore	Add system tests for notify over TLS	2024-10-24 12:55:01 +11:00
dhparam3072.pem	Use FIPS compatible DH-param files	2024-12-04 18:08:51 +02:00
setup.sh	Add system tests for notify over TLS	2024-10-24 12:55:01 +11:00
tests.sh	Adjust number of zones to those in FIPS mode	2025-01-02 14:38:24 +00:00
tests_sh_notify.py	Replace clean.sh files with extra_artifacts mark	2024-11-08 10:54:24 +01:00