Every remaining deviation from the shared _common/controls.conf.j2
include is intentional; annotate each with a one-line grep-able
comment stating why:
- rndc/ns2 and ns5 test multi-key and read-only channels; ns4 gets a
runtime-generated multi-key channel appended by setup.sh;
- resolver/ns9 runs an IPv6-only channel, which the IPv4-only shared
template cannot express;
- shutdown/resolver lives in a non-ns<N> directory, so the template's
ns.ip variable is not injected there.
Assisted-by: Claude:claude-fable-5
algorithm @DEFAULT_HMAC@;
};
+/* deliberately not _common/controls.conf.j2: IPv6 control channel; the shared template is IPv4-only */
controls {
inet fd92:7065:b8e:ffff::9 port @CONTROLPORT@ allow { any; } keys { rndc_key; };
};
algorithm @DEFAULT_HMAC@;
};
+/* deliberately not _common/controls.conf.j2: multi-key control channel is the test subject */
controls {
inet 10.53.0.2 port @CONTROLPORT@ allow { any; } keys { rndc_key; secondkey; };
};
+/* deliberately not _common/controls.conf.j2: setup.sh appends a runtime-generated multi-key channel on EXTRAPORT7 */
options {
port @PORT@;
pid-file "named.pid";
algorithm @DEFAULT_HMAC@;
};
+/* deliberately not _common/controls.conf.j2: read-only control channel is the test subject */
controls {
inet 10.53.0.5 port @CONTROLPORT@ allow { any; } keys { rndc_key; } read-only yes;
};
algorithm @DEFAULT_HMAC@;
};
+/* deliberately not _common/controls.conf.j2: non-ns<N> directory without the ns.ip template variable */
controls {
inet 10.53.0.3 port @CONTROLPORT@ allow { any; } keys { rndc_key; };
};