And in the creation of NSEC3 records, the "next link of the chain" (which is currently in upper case) means the "chained-to" record will also be in Upper Case???
eg...
13bu1nqrimn19lbkq6cvqume6thbsebr.web.za. 300 IN NSEC3 1 1 5
A021CAFA36A752AC 1ALJ0RMHHSFU8I2RQ6HB0T74JE03MGC1 MX RRSIG
||
\||/ <-- a down pointing arrow
\/
1alj0rmhhsfu8i2rq6hb0t74je03mgc1.web.za. 300 IN NSEC3 1 1 5
A021CAFA36A752AC 1NRSLBF0FHCATO1CB7E13OP7DHHVPAUT MX RRSIG
So in the next release, the line above will be written as:
1ALJ0RMHHSFU8I2RQ6HB0T74JE03MGC1.web.za. 300 IN NSEC3 1 1 5
A021CAFA36A752AC 1NRSLBF0FHCATO1CB7E13OP7DHHVPAUT MX RRSIG
Please.
On 30/08/2016 16:41, Yuri Schaeffer wrote:
> On 30-08-16 16:10, Mark Elkins wrote:
>> Much to my annoyance, OpenDNSSEC converts to lower case the Left Hand
>> side of all zones (the name part, before the TTL). Can this modification
>> of data be switched off?
>
> Agreed and the next release will have a fix for this.
>
> https://github.com/opendnssec/opendnssec/pull/479/commits/9094d7623335c78ff18fdc606e30efdc340646b9
>
> There is no run-time option for this.
>
> //Yuri
--
Mark James ELKINS - Posix Systems - (South) Africa
[email protected] Tel: +27.128070590 Cell: +27.826010496
For fast, reliable, low cost Internet in ZA: https://ftth.posix.co.za
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Opendnssec-user mailing list [email protected] https://lists.opendnssec.org/mailman/listinfo/opendnssec-user
