-
Matthijs Mekking authored
When you do a restart or reconfig of named, or rndc loadkeys, this triggers the key manager to run. The key manager will check if new keys need to be created. If there is an active key, and key rollover is scheduled far enough away, no new key needs to be created. However, there was a bug that when you just start to sign your zone, it takes a while before the KSK becomes an active key. An active KSK has its DS submitted or published, but before the key manager allows that, the DNSKEY needs to be omnipresent. If you restart named or rndc loadkeys in quick succession when you just started to sign your zone, new keys will be created because the KSK is not yet considered active. Fix is to check for introducing as well as active keys. These keys all have in common that their goal is to become omnipresent.
b378d037
To find the state of this project's repository at the time of any of these versions, check out the tags.