Ondřej Surý b9c1b90b50 Drop RFC 2535 special-casing of the KEY record type ... After SIG and NXT lost their special handling, KEY remained the only RFC 2535-era type still receiving coexistence allowances: KEY alongside CNAME at the same owner, KEY answered from the parent side of a zone cut, KEY kept across CNAME eviction in the cache. RFC 3755 retains type 25 only for SIG(0) and TKEY transaction signatures, and neither relies on those allowances in practice. The in-tree comment that flagged the RFC 3007 parent-side carve-out as "unclear" predicted this cleanup. Zones that publish CNAME and KEY at the same owner — already invalid under RFC 2181 — now fail to load. System test fixtures are updated accordingly, and a new test asserts that SIG, NXT, and KEY records pick up covering RRSIGs when their zone is signed.		2026-05-28 13:21:00 +02:00
..
zones	Drop RFC 2535 special-casing of the KEY record type	2026-05-28 13:21:00 +02:00
setup.sh	Use jinja2 templates in checkzone test	2025-12-09 14:23:14 +01:00
tests.sh	Remove leftover test development echo	2025-07-15 23:53:57 +10:00
tests_sh_checkzone.py	Replace clean.sh files with extra_artifacts mark	2024-11-08 10:54:24 +01:00