Colin Vidal 11a4df7ec5 split ede24 system test into separate modules ... Because ede24 system tests require stopping/restarting server, there is always the risk that the test ends (with a failure) with server in an wrong and impredictible state. This would make the other tests to fail in a strange way as well. To avoid this problem, split the test into different modules, so if a module fails, the other module is not impacted as it uses separate server instances.		2025-11-06 15:13:29 +01:00
..
check	"named-checkconf -b" dumps built-in config	2025-11-04 09:26:33 +01:00
confgen	Change the 'isc_g_mctx' to be always available	2025-08-04 11:29:50 +02:00
delv	fix delv when using the builtin trust-anchors	2025-10-29 13:55:47 -07:00
dig	avoid retrying a server if its address is unusable	2025-11-03 19:37:09 +00:00
dnssec	cfg_parse_ functions internally handle the parser	2025-10-23 13:01:08 -07:00
include	move default configuration to common bin/include folder	2025-10-29 13:55:04 -07:00
named	don't retain the default configuration	2025-10-31 08:02:17 +01:00
nsupdate	cfg_parse_ functions internally handle the parser	2025-10-23 13:01:08 -07:00
plugins	cfg_parse_ functions internally handle the parser	2025-10-23 13:01:08 -07:00
rndc	implement "rndc showconf"	2025-10-29 23:49:49 +01:00
tests	split ede24 system test into separate modules	2025-11-06 15:13:29 +01:00
tools	Use ControlStatementsExceptControlMacros for SpaceBeforeParens	2025-08-19 07:58:33 +02:00
meson.build	replace the build system with meson	2025-06-11 10:30:12 +03:00