]> git.ipfire.org Git - thirdparty/bind9.git/commit
Test sending NOTIFY(CDS) messages
authorMatthijs Mekking <matthijs@isc.org>
Tue, 25 Nov 2025 07:56:32 +0000 (08:56 +0100)
committerMatthijs Mekking <matthijs@isc.org>
Fri, 19 Dec 2025 14:01:36 +0000 (15:01 +0100)
commite344fe18bcc8ca2204470717ddfe70dbba293c8e
tree700d072aba73fd7c42a1d033dbcf9213474e7b97
parentc8253a0a7a3e6c2ee93ff1eeeed654e95603a358
Test sending NOTIFY(CDS) messages

When starting up the services, send notifies for the existing CDS RRset.
This requires setting up a chain of trust for the test, so the DSYNC
records can be retrieved and validated.

This feature requires enabling 'notify-cds' and 'dnssec-validation'.

In this test, the scanner is pointed to ns2. Since there is no code
for receiving NOTIFY(CDS) messages for delegations, this is treated
as "not authoritative". Checking for this log message ensures us that
the NOTIFY(CDS) message was actually sent.
14 files changed:
bin/tests/system/multisigner/ns1/named.conf.j2 [new file with mode: 0644]
bin/tests/system/multisigner/ns1/root.db.in [new file with mode: 0644]
bin/tests/system/multisigner/ns1/setup.sh [new file with mode: 0644]
bin/tests/system/multisigner/ns2/multisigner.db.in.j2 [new file with mode: 0644]
bin/tests/system/multisigner/ns2/named.conf.j2 [new file with mode: 0644]
bin/tests/system/multisigner/ns2/secondary.db.in.j2 [new file with mode: 0644]
bin/tests/system/multisigner/ns2/setup.sh [new file with mode: 0644]
bin/tests/system/multisigner/ns3/named.conf.j2
bin/tests/system/multisigner/ns3/setup.sh
bin/tests/system/multisigner/ns4/named.conf.j2
bin/tests/system/multisigner/ns4/setup.sh
bin/tests/system/multisigner/ns5/named.conf.j2
bin/tests/system/multisigner/setup.sh
bin/tests/system/multisigner/tests_multisigner.py