Matthijs Mekking ee42f66fbe Force set DS state after 'rndc dnssec -checkds' ... Set the DS state after issuing 'rndc dnssec -checkds'. If the DS was published, it should go in RUMOURED state, regardless whether it is already safe to do so according to the state machine. Leaving it in HIDDEN (or if it was magically already in OMNIPRESENT or UNRETENTIVE) would allow for easy shoot in the foot situations. Similar, if the DS was withdrawn, the state should be set to UNRETENTIVE. Leaving it in OMNIPRESENT (or RUMOURED/HIDDEN) would also allow for easy shoot in the foot situations.		2023-01-27 15:07:26 +00:00
..
check	Update sources to Clang 15 formatting	2022-11-29 08:54:34 +01:00
confgen	Update sources to Clang 15 formatting	2022-11-29 08:54:34 +01:00
delv	Resolver query forwarding to DoT-enabled upstream servers	2023-01-20 14:45:30 +00:00
dig	Refactor isc_nm_xfr_allowed()	2023-01-19 10:24:08 +00:00
dnssec	Allow interrupting dnssec-signzone during signing	2023-01-22 20:44:18 +01:00
named	BIND 9.19.9	2023-01-25 21:16:00 +01:00
nsupdate	remove nonfunctional DSCP implementation	2023-01-09 12:15:21 -08:00
plugins	Update sources to Clang 15 formatting	2022-11-29 08:54:34 +01:00
rndc	Update sources to Clang 15 formatting	2022-11-29 08:54:34 +01:00
tests	Force set DS state after 'rndc dnssec -checkds'	2023-01-27 15:07:26 +00:00
tools	fully remove DSCP	2023-01-17 16:18:21 -08:00
Makefile.am	Remove native PKCS#11 support	2021-09-09 15:35:39 +02:00