[Opendnssec-user] rollover started automatically when ManualRollover set

Hoda Rohani hoda at nlnetlabs.nl
Mon Jul 24 09:52:29 UTC 2017

Hello Email,

On 23-07-17 15:24, Emil Natan wrote:
> I tried to decrease various values set in the kasp.xml file, most notably
> validity default and denial, publish and retire safety, propagation delay
> for the zone and the parent zone and TTLs. While that affected the key
> state is some cases, it did not affect the ZSK in retire state which I want
> to remove from the zone.

I think reducing the Life time value of ZSK would help you. You should run 'ods-ksmutil policy import' after decreasing
the Life time to see the result.
After the old ZSK is completely removed you can modify the ZSK Lifetime again to have the main value.

> I also tried to force deletion of that key with ods-ksmutil key delete but
> the action was rejected by the enforcerd since it considers the key to be
> in use.

Actually it seems that this key is still being used for signatures and cannot be deleted.

> I believe it's possible to manually change the value of next transition for
> that key in the database, but that I really consider last resort.

Please let us know if you still have the problem.

> Emil

Hoda Rohani

> On Sat, Jul 22, 2017 at 5:02 PM, Emil Natan <shlyoko at gmail.com> wrote:
>> Hello,
>> opendnssec version 1.4.13, kasp.xml attached.
>> We have all keys (KSK and ZSK) for the next 5 years pregenerated on the
>> HSM.
>> <ManualRollover/> is set for the KSK.
>> Yet yesterday, on the day the KSK rollover was scheduled for, it just
>> happened.
>> Jul 20 03:47:15 signer001 ods-enforcerd: Zone example.com found.
>> Jul 20 03:47:15 signer001 ods-enforcerd: Policy for example.com set to 1.
>> Jul 20 03:47:15 signer001 ods-enforcerd: Policy 1 found in DB.
>> Jul 20 03:47:15 signer001 ods-enforcerd: Config will be output to
>> /ods-data/var/opendnssec/signconf/example.com.xml.
>> Jul 20 03:47:15 signer001 ods-enforcerd: KSK key allocation for zone
>> example.com: 1 key(s) allocated
>> The new KSK was introduced into the zone and DNSKEY signed with both new
>> and old KSK. What makes it even more annoying is that the ZSK was rolled at
>> the same time (as expected), so now we ended having pretty big DNSKEY +
>> RRSIG response.
>> One of the checks on the signed zonefiles stopped it from being published
>> and now we have to decide either to publish the zonefile that way or force
>> the ZSK rollover to finish faster than it should if we wait for it to
>> happen automatically and then publish the zonefile. Because of the
>> signature validity set to 31 days, it's scheduled to happen on  2017-08-20.
>> The DNSKEY RRset has a TTL of one hour and we publish the zone every day
>> and it spreads instantly, so it's already safe to do so. I see the
>> ods-ksmutil provides option to retire KSK (ksk-retire), but I do not see
>> such option for ZSK. Any ideas if and how it can be done?
>> Thanks
>> Emil
> _______________________________________________
> Opendnssec-user mailing list
> Opendnssec-user at lists.opendnssec.org
> https://lists.opendnssec.org/mailman/listinfo/opendnssec-user

More information about the Opendnssec-user mailing list