"Yuri Schaeffer" schreef in bericht
news:7b52287e-c6d9-7862-dcdc-3c9db8c8f...@nlnetlabs.nl...
We never had this problem with 1.4. From our /etc/opendnssec/kasp.xml:
PT15H
PT86400S
PT10800S
datecounter
The kasp.xml has not
> We never had this problem with 1.4. From our /etc/opendnssec/kasp.xml:
>
>
>PT15H
>
>PT86400S
>PT10800S
>datecounter
>
>
>
> The kasp.xml has not been touched since December 2015.
> So, there must be something else. Could
"Yuri Schaeffer" schreef in bericht
news:46da313f-2c47-92b1-8c3d-cc1af1ec6...@nlnetlabs.nl...
Hi Fred,
The log message "If this is the result of a key rollover ..." suggests
(at least to me) that it is normal that a manual intervention is needed
during a roll-over, but we are not used to it.
"Yuri Schaeffer" schreef in bericht
news:46da313f-2c47-92b1-8c3d-cc1af1ec6...@nlnetlabs.nl...
Hi Fred,
The log message "If this is the result of a key rollover ..." suggests
(at least to me) that it is normal that a manual intervention is needed
during a roll-over, but we are not used to it.
Hi Fred,
> The log message "If this is the result of a key rollover ..." suggests
> (at least to me) that it is normal that a manual intervention is needed
> during a roll-over, but we are not used to it.
> Is this a bug, or is it the intended behavior?
> Are there new options to be included in t
Recently we upgraded to ods 2.01. from 1.4.10. During key roll-overs we
never needed to update our input zones as long as we used version 1.
This night ods was still in the process of retiring the backup keys, used in
version 1.4.10, when it started a ZSK key roll-over. After that the signer
ref
