validns did not recognise the EUI48 (TYPE 108) and EUI64 (TYPE 109) resource
records defined by RFC 7043, so any zone using them failed to validate.
Both types share a strict presentation-format parser (six or eight
hyphen-separated hex octets), store the raw octet array on the wire, and render
under -v in canonical lowercase hyphenated form per RFC 7043 §3. The generic
(# length hex) form keeps working through the existing path. Coverage adds a
positive zone, strict negatives in manyerrors.zone, a human-form round-trip,
and an RSASHA256-signed fixture whose RRSIGs prove the wire encoding
round-trips through DNSSEC verification.
Fixes #126
validns did not recognise the EUI48 (TYPE 108) and EUI64 (TYPE 109) resource
records defined by RFC 7043, so any zone using them failed to validate.
Both types share a strict presentation-format parser (six or eight
hyphen-separated hex octets), store the raw octet array on the wire, and render
under -v in canonical lowercase hyphenated form per RFC 7043 §3. The generic
(\# length hex) form keeps working through the existing path. Coverage adds a
positive zone, strict negatives in manyerrors.zone, a human-form round-trip,
and an RSASHA256-signed fixture whose RRSIGs prove the wire encoding
round-trips through DNSSEC verification.
Fixes #126