[Opendnssec-user] rollover started automatically when ManualRollover set

Emil Natan shlyoko at gmail.com
Mon Jul 31 10:57:16 UTC 2017

I just want to share the solution that worked for me in the end. It was
indeed the last resort considered, changing the values directly into the
database. Here is the mysq command I used:

update dnsseckeys set dead=retire, state=6 where keytype=256 and state=5
and zone_id=(select id from zones where name="example.com");

Then I removed the signconf file for the zone and forced the enforcer to
recreate it:
ods-ksmutil notify

Thank you Hoda for the help.


On Sun, Jul 23, 2017 at 4:24 PM, Emil Natan <shlyoko at gmail.com> 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 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.
> 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.
> Emil
> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendnssec.org/pipermail/opendnssec-user/attachments/20170731/f2105ef6/attachment.htm>

More information about the Opendnssec-user mailing list