You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
EppLib secDNS (DNSSEC) extension not handling all elements in RFC #31
It is now only possible to add and remove the most basic secDNS (EPP DNSSEC) elements usting EppLib.
The following examples are from http://www.rfc-editor.org/rfc/rfc5910.txt
Example use of the secDNS-1.1 DS Data Interface for a create: (EppLib handles this)
Thanks for the detailed report, and sorry it took so long. This is fixed in EppLib 1.7.0 (#61), which covers everything you listed from RFC 5910:
DNSKEY data with the new SecDNSKeyData, either on its own (SecDNSCreate.KeyData, SecDNSUpdate.KeyDataToAdd / KeyDataToRemove) or inside a DS record (SecDNSData.KeyData).
maxSigLife on create, and changing it through SecDNSUpdate.MaxSigLife.
Update options:SecDNSUpdate.RemoveAll and Urgent.
Reading DNSSEC data from domain info responses with SecDNSInfData.FromResponse(response).
It also fixes key tags above 32767 and lets you set DigestType (for example SHA256). Note that KeyTag is now an int, so rebuild after upgrading. The upgrading notes have the details.
Activity
ademar commentedon Sep 25, 2026
Thanks for the detailed report, and sorry it took so long. This is fixed in EppLib 1.7.0 (#61), which covers everything you listed from RFC 5910:
SecDNSKeyData, either on its own (SecDNSCreate.KeyData,SecDNSUpdate.KeyDataToAdd/KeyDataToRemove) or inside a DS record (SecDNSData.KeyData).maxSigLifeon create, and changing it throughSecDNSUpdate.MaxSigLife.SecDNSUpdate.RemoveAllandUrgent.SecDNSInfData.FromResponse(response).It also fixes key tags above 32767 and lets you set
DigestType(for example SHA256). Note thatKeyTagis now anint, so rebuild after upgrading. The upgrading notes have the details.Complete the secDNS (DNSSEC) extension per RFC 5910