Colin Vidal 7ff1b7ef21 introduce default config builtin-root-anchors ... Since the effective configuration tree is a "merged" configuration tree from the user and the default configurations, the effective configuration provides a unique configuration tree used by apply_confiuration() to configure the server. However, there is one specific case where the configuration code needs to differentiate whether the configuration originally came from the default or the user configuration: the trust-anchors. This is because the default trust-anchors _have_ to be those for the root zone, and the one provided by the user can be for any zone. A check enforces this. In order to keep this difference visible from the configuration code, with a unique configuration tree, we now introduce a default-only `builtin-trust-anchors` statement which holds the builtin root trust-anchors. It can't be used from the user configuration (this would raise an error), hence it is not documented.		2025-10-29 13:55:47 -07:00
..
startperf	Reformat shell scripts with shfmt	2023-10-26 10:23:50 +02:00
system	introduce default config builtin-root-anchors	2025-10-29 13:55:47 -07:00
testdata/wire
.gitignore	Move environment variables from conf.sh to pytest	2024-05-09 17:08:08 +02:00
meson.build	replace the build system with meson	2025-06-11 10:30:12 +03:00
test_client.c	Add and use global memory context called isc_g_mctx	2025-08-04 11:29:26 +02:00
test_server.c	Add and use global memory context called isc_g_mctx	2025-08-04 11:29:26 +02:00