Render always writes the secret ddi-suite-keys.conf (only a comment without keys). Primary zones of a cluster get "notify explicit", "also-notify" and "allow-transfer" with the transfer key; secondary zones transfer from their primaries with the key into <zone_dir>/secondary/ and have no artifact. Dynamic zones accept the update keys in their ACL. Keys are validated (name, algorithm whitelist, canonical base64) and every referenced key must exist. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
21 lines
686 B
Plaintext
21 lines
686 B
Plaintext
// Generated by DDI Suite (revision 11). Do not edit: the DNS agent
|
|
// overwrites this file. Include it at the top level of named.conf.
|
|
|
|
zone "2.0.192.in-addr.arpa" {
|
|
type primary;
|
|
file "/etc/bind/ddi-suite/zones/db.2.0.192.in-addr.arpa";
|
|
notify explicit;
|
|
also-notify { 192.0.2.3 key "xfer.dns-a"; 2001:db8::2 key "xfer.dns-a"; };
|
|
allow-transfer { key "xfer.dns-a"; };
|
|
allow-update { none; };
|
|
};
|
|
|
|
zone "office.test" {
|
|
type primary;
|
|
file "/etc/bind/ddi-suite/zones/db.office.test";
|
|
notify explicit;
|
|
also-notify { 192.0.2.3 key "xfer.dns-a"; 2001:db8::2 key "xfer.dns-a"; };
|
|
allow-transfer { key "xfer.dns-a"; };
|
|
allow-update { none; };
|
|
};
|