]> git.ipfire.org Git - thirdparty/bind9.git/commit
test named remote-servers `key` usage
authorColin Vidal <colin@isc.org>
Fri, 21 Nov 2025 16:05:15 +0000 (17:05 +0100)
committerColin Vidal <colin@isc.org>
Fri, 28 Nov 2025 08:10:53 +0000 (09:10 +0100)
commit32a4aa95aed294a28da8abfabfb17f53699e0b56
treee763afd1c484ec3dd580e9c524f83a30742e86ee
parent046c6819b24ebd7d087ed33518b71b0ff23d9918
test named remote-servers `key` usage

Even though `remote-servers` now allows using named server-list with `key`
(or `tls`), the `key` or `tls` is not used, in the context of a named
server-list, when configuring the server.

For instance,

   remote-servers foo { 10.53.0.5; };
   also-notify { foo key fookey; };

won't use `fookey`.

Add a system test highlighting the problem.
bin/tests/system/xfer-servers-list/ns1/named.conf.j2 [new file with mode: 0644]
bin/tests/system/xfer-servers-list/ns1/test.db.j2 [new file with mode: 0644]
bin/tests/system/xfer-servers-list/ns2/named.conf.j2 [new file with mode: 0644]
bin/tests/system/xfer-servers-list/ns3/named.conf.j2 [new file with mode: 0644]
bin/tests/system/xfer-servers-list/ns4/named.conf.j2 [new file with mode: 0644]
bin/tests/system/xfer-servers-list/tests_xfer_servers_list.py [new file with mode: 0644]