bind9/bin/tests/system/notify
Mark Andrews a6ca8407ee
Check notify with bad notify source address and tsig
named was asserting when the notify source address was not available
and TSIG was being used.  Check this scenario by adding a nameserver
to the zone which is configured to uses a non-existent source address
and a blackholed destination address and a TSIG using a server clause
for that destination address.

(cherry picked from commit f99d7f4217)
2026-02-20 10:50:19 +01:00
..
CA Use correct certificates for TLS notify tests 2024-10-24 03:11:50 +00:00
ns1 Use jinja2 templates in notify test 2025-12-10 13:43:52 +01:00
ns2 Check notify with bad notify source address and tsig 2026-02-20 10:50:19 +01:00
ns3 Use jinja2 templates in notify test 2025-12-10 13:43:52 +01:00
ns4 Use jinja2 templates in notify test 2025-12-10 13:43:52 +01:00
ns5 Use jinja2 templates in notify test 2025-12-10 13:43:52 +01:00
.gitignore Add system tests for notify over TLS 2024-10-24 03:11:50 +00:00
dhparam3072.pem Use FIPS compatible DH-param files 2024-12-09 12:00:49 +00:00
setup.sh Check notify with bad notify source address and tsig 2026-02-20 10:50:19 +01:00
tests.sh Check notify with bad notify source address and tsig 2026-02-20 10:50:19 +01:00
tests_sh_notify.py Check notify with bad notify source address and tsig 2026-02-20 10:50:19 +01:00