Issue
Description of problem:
I have a few zones using inline-signing which I have set up originally with 2d TTL. Due to this the existing DNSKEY RRs also have 2d TTL. Now I have been trying to reduce the TTL to 1d but it seems there is no supported way or tool to do so.
I have set dnskey-ttl to 1d and replace keys, still all DNSKEY RRs have 2d TTL. Setting it on the key with dnssec-settime doesn't help either and man pages specifically mention:
This option sets the default TTL to use for this key when it is converted into a DNSKEY RR.
This is the TTL used when the key is imported into a zone, unless there was already a DNSKEY
RRset in place, in which case the existing TTL takes precedence.
This may also cause caching resolver issues during automatic key rollover, because bind calculates rollover periods based on the dnskey-ttl configuration value and not on the TTL of the DNSKEY RRs.
Version-Release number of selected component (if applicable):
bind-9.16.23-11
How reproducible:
Set up a zone for inline signing with a higher TTL e.g. 2d, then set up a dnssec policy with short/different dnskey-ttl, e.g. 1h.
Actual results:
The TTL of DNSKEY RRs in the signed zone are still 2d.
Expected results:
The TTL of DNSKEY RRs in the signed zone should be 1h.
Additional info:
bind issue at isc: https://gitlab.isc.org/isc-projects/bind9/-/issues/3987
