>> I've done the conversion from 1.4.14 to an earlier 2.1.x version >> on another host (which worked at the time), but have come to the >> realization that the test installation needs to be re-done in an >> attempt to re-create the issues we ran across last night. For >> some reason I do not fathom, the test installation has gone to >> <NSEC> (according to the signconf xml files) despite kasp.xml >> saying <NSEC3>, but the migration was done with a script from >> that earlier OpenDNSSEC 2.x version. > > As mentioned in the blog post about the 2.1.7 release [1], there was an > issue in the migration script (OPENDNSSEC-949) which caused NSEC3 zones > becoming NSEC after migration. > > [1] https://www.opendnssec.org/2020/10/opendnssec-2-1-7/
Ah, that explains this particular niggle, then -- before 2.1.8 it ran 2.1.6. Regards, - Håvard _______________________________________________ Opendnssec-user mailing list Opendnssec-user@lists.opendnssec.org https://lists.opendnssec.org/mailman/listinfo/opendnssec-user
