On Fri, 05 Mar 2021 14:44:11 +0100 (CET) Havard Eidnes via Opendnssec-user <opendnssec-user@lists.opendnssec.org> wrote:
> > On Fri, Mar 05, 2021 at 12:58:16AM +0100, Havard Eidnes via > > Opendnssec-user wrote: > > 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/ -- Stefan Ubbink DNS & Systems Engineer Present: Mon, Tue, Wed, Fri SIDN | Meander 501 | 6825 MD | ARNHEM | The Netherlands T +31 (0)26 352 55 00 https://www.sidn.nl
pgpZUV_DQITL3.pgp
Description: OpenPGP digital signature
_______________________________________________ Opendnssec-user mailing list Opendnssec-user@lists.opendnssec.org https://lists.opendnssec.org/mailman/listinfo/opendnssec-user
