DNSSEC10
Status: Final
Purpose
- Verify that signed child-zone nameservers consistently provide NSEC or NSEC3 denial-of-existence material (including signatures and owner/type-shape checks) when querying for apex
NSECandNSEC3PARAM. - The apex NODATA proof read here carries one denial record. The consistency of a proof with several records, the denial of a name that does not exist, is owned by DNSSEC23.
Preconditions And Inputs
- Preconditions:
- A
zone.Zoneobject is available.
- A
- Required inputs:
- Child nameserver name/IP items from
DelegationNameserversandZoneNameservers. - DNSKEY, NSEC, and NSEC3PARAM query responses (DNSSEC enabled).
- Child nameserver name/IP items from
- Profile/config knobs that affect behavior:
net.ipv4andnet.ipv6: disabled transports are skipped with transport debug tags.resolver.defaults.parallel: per-nameserver parallel execution fanout.
Algorithm And Decision Flow
- Emit
TEST_CASE_START. - Build child nameserver set from delegation+zone NS items, grouped by IP.
- For each unique nameserver IP (parallelized):
- If transport is disabled, emit
IPV4_DISABLEDorIPV6_DISABLEDfor rrtypesDNSKEY,NSEC, andNSEC3PARAM, mark nameserver ignored, and skip. - Query
DNSKEY(DNSSEC enabled); if response is absent/non-NOERROR/non-AA, mark ignored and skip. - If no apex DNSKEY records are returned, classify nameserver as
without DNSKEYand skip remaining DS10 checks. - Otherwise classify nameserver as
with DNSKEYand keep DNSKEY set for signature checks.
- If transport is disabled, emit
- Run
NSECquery processing:- Response-shape failure =>
NSEC query response errorset. - Non-empty answer with NSEC records => NSEC-in-answer path (multi-record, apex-owner checks).
- Non-empty answer without NSEC => erroneous-answer set.
- Empty answer with NSEC3 in authority => NSEC3-NODATA path (SOA presence/owner checks, NSEC3 owner/type-list checks, signature presence and verification checks).
- Empty answer with NSEC in authority (no NSEC3) => NSEC-NODATA path for RFC 4470 / RFC 9824 white-lies / minimally covering NSEC / compact denial of existence implementations (SOA presence/owner checks, NSEC count/apex-owner checks, signature presence and verification checks; type-list validation is skipped because the synthesized bitmap intentionally excludes the queried type). Treated as NSEC evidence equivalent to NSEC-in-answer for consistency checks.
- Response-shape failure =>
- Run
NSEC3PARAMquery processing:- Response-shape failure =>
NSEC3PARAM query response errorset. - Non-empty answer with NSEC3PARAM => NSEC3PARAM-in-answer path (apex-owner check applied to every NSEC3PARAM RR in the RRset; multiple NSEC3PARAM RRs are permitted to accommodate parameter rollover, RFC 5155 section 7.3).
- Non-empty answer without NSEC3PARAM => erroneous-answer set.
- Empty answer with NSEC in authority => NSEC-NODATA path (SOA presence/owner checks, NSEC owner/type-list checks, signature presence and verification checks).
- Response-shape failure =>
- During NSEC/NSEC3 signature verification:
- Track per-keytag conditions: no matching DNSKEY, expired, not-yet-valid, verify error.
- Track successful verification per nameserver.
- Track unsupported algorithm situations as
DS10_ALGO_NOT_SUPPORTED_BY_ZM.
- Aggregate outcomes across nameservers and emit structural consistency tags:
DS10_ERR_MULT_*,DS10_INCONSISTENT_*,DS10_MIXED_NSEC_NSEC3,DS10_HAS_NSEC,DS10_HAS_NSEC3.
- Emit detailed content/signature tags for NSEC and NSEC3/NSEC3PARAM observations.
- Emit DNSSEC-presence summary tags:
DS10_ZONE_NO_DNSSECwhen only no-DNSKEY responders were observed.DS10_SERVER_NO_DNSSECwhen mixed DNSKEY/no-DNSKEY responders were observed.
- Emit
DS10_EXPECTED_NSEC_NSEC3_MISSINGfor nameservers with DNSKEY that produced neither expected NSEC nor expected NSEC3 evidence sets. - Emit
TEST_CASE_END.
Per-Nameserver DNSKEY Classification (step 3)
NSEC Query Processing (step 4)
NSEC3PARAM Query Processing (step 5)
Aggregation and Final Emission (steps 6-11)
Emitted Tags (Possible Set)
| Tag | Emitted when |
|---|---|
DS10_ALGO_NOT_SUPPORTED_BY_ZM | Signature verification required an unsupported algorithm. |
DS10_ERR_MULT_NSEC | More than one NSEC record was observed where one was expected. |
DS10_ERR_MULT_NSEC3 | More than one NSEC3 record was observed where one was expected. |
DS10_EXPECTED_NSEC_NSEC3_MISSING | Nameserver had DNSKEY support but did not provide expected NSEC/NSEC3 evidence (RFC 4035 section 3.1.3.1, RFC 5155 section 7.2.3). |
DS10_HAS_NSEC | Zone behavior is consistently NSEC-only for observed nameservers. |
DS10_HAS_NSEC3 | Zone behavior is consistently NSEC3-only for observed nameservers. |
DS10_INCONSISTENT_NSEC | NSEC evidence is inconsistent across nameservers. |
DS10_INCONSISTENT_NSEC3 | NSEC3 evidence is inconsistent across nameservers. |
DS10_INCONSISTENT_NSEC_NSEC3 | At least one nameserver uses NSEC-only and at least one uses NSEC3-only, with no nameserver exhibiting both simultaneously. |
DS10_MIXED_NSEC_NSEC3 | At least one nameserver shows both NSEC and NSEC3 behavior. |
DS10_NONSTANDARD_NSEC_RESPONSE | NSEC query returned NSEC in the authority section instead of the answer section (RFC 4470 white-lies or RFC 9824 section 3.2 compact denial). |
DS10_NSEC3PARAM_GIVES_ERR_ANSWER | NSEC3PARAM query had unexpected non-empty answer content. |
DS10_NSEC3PARAM_MISMATCHES_APEX | NSEC3PARAM owner name did not match zone apex (RFC 5155 section 4). |
DS10_NSEC3PARAM_QUERY_RESPONSE_ERR | NSEC3PARAM query had no usable authoritative NOERROR response. |
DS10_NSEC3_ERR_TYPE_LIST | NSEC3 type bitmap failed mandatory/forbidden checks (RFC 5155 sections 7.1 and 7.2.3). |
DS10_NSEC3_MISMATCHES_APEX | NSEC3 owner hash/name did not match expected apex semantics (RFC 5155 section 7.2.3). |
DS10_NSEC3_MISSING_SIGNATURE | NSEC3 RRset had no matching RRSIG coverage (RFC 4035 section 3.1.1). |
DS10_NSEC3_NODATA_MISSING_SOA | NSEC3 NODATA authority response lacked SOA (RFC 2308 section 3). |
DS10_NSEC3_NODATA_WRONG_SOA | NSEC3 NODATA authority response had SOA with wrong owner (RFC 2308 section 3). |
DS10_NSEC3_NO_VERIFIED_SIGNATURE | NSEC3 signatures existed but none verified for affected nameservers. |
DS10_NSEC3_RRSIG_EXPIRED | NSEC3 RRSIG expired for given keytag (RFC 4034 section 3.1.5). |
DS10_NSEC3_RRSIG_NOT_YET_VALID | NSEC3 RRSIG not yet valid for given keytag (RFC 4034 section 3.1.5). |
DS10_NSEC3_RRSIG_NO_DNSKEY | NSEC3 RRSIG keytag had no matching DNSKEY (RFC 4035 section 5.3.1). |
DS10_NSEC3_RRSIG_VERIFY_ERROR | NSEC3 RRSIG verification failed for given keytag (RFC 4035 section 5.3.3). |
DS10_NSEC_ERR_TYPE_LIST | NSEC type bitmap failed mandatory/forbidden checks (RFC 4034 section 4.1.2, RFC 4035 section 2.3). |
DS10_NSEC_GIVES_ERR_ANSWER | NSEC query had unexpected non-empty answer content. |
DS10_NSEC_MISMATCHES_APEX | NSEC owner name did not match zone apex (RFC 4035 section 3.1.3.1). |
DS10_NSEC_MISSING_SIGNATURE | NSEC RRset had no matching RRSIG coverage (RFC 4035 section 3.1.1). |
DS10_NSEC_NODATA_MISSING_SOA | NSEC NODATA authority response lacked SOA (RFC 2308 section 3). |
DS10_NSEC_NODATA_WRONG_SOA | NSEC NODATA authority response had SOA with wrong owner (RFC 2308 section 3). |
DS10_NSEC_NO_VERIFIED_SIGNATURE | NSEC signatures existed but none verified for affected nameservers. |
DS10_NSEC_QUERY_RESPONSE_ERR | NSEC query had no usable authoritative NOERROR response. |
DS10_NSEC_RRSIG_EXPIRED | NSEC RRSIG expired for given keytag (RFC 4034 section 3.1.5). |
DS10_NSEC_RRSIG_NOT_YET_VALID | NSEC RRSIG not yet valid for given keytag (RFC 4034 section 3.1.5). |
DS10_NSEC_RRSIG_NO_DNSKEY | NSEC RRSIG keytag had no matching DNSKEY (RFC 4035 section 5.3.1). |
DS10_NSEC_RRSIG_VERIFY_ERROR | NSEC RRSIG verification failed for given keytag (RFC 4035 section 5.3.3). |
DS10_SERVER_NO_DNSSEC | At least one nameserver returned a usable DNSKEY and at least one nameserver returned no usable DNSKEY. |
DS10_ZONE_NO_DNSSEC | No nameserver returned usable DNSKEY while at least one returned no DNSKEY. |
IPV4_DISABLED | IPv4 transport is disabled for a queried nameserver/query type. |
IPV6_DISABLED | IPv6 transport is disabled for a queried nameserver/query type. |
TEST_CASE_END | Testcase completion marker is emitted. |
TEST_CASE_START | Testcase start marker is emitted. |
Tag Arguments
| Tag | Argument key | Type | Meaning |
|---|---|---|---|
DS10_ALGO_NOT_SUPPORTED_BY_ZM | keytag, algo_num, algo_mnemo, addresses | int, int, string, array<string> | Unsupported algorithm details and the nameserver IPs from the verification path. |
DS10_ERR_MULT_NSEC | servers | array<object> | Structured nameserver identities ({ns,address} object). |
DS10_ERR_MULT_NSEC3 | servers | array<object> | Structured nameserver identities ({ns,address} object). |
DS10_EXPECTED_NSEC_NSEC3_MISSING | servers | array<object> | Structured nameserver identities ({ns,address} object). |
DS10_HAS_NSEC | servers | array<object> | Structured nameserver identities ({ns,address} object). |
DS10_HAS_NSEC3 | servers | array<object> | Structured nameserver identities ({ns,address} object). |
DS10_INCONSISTENT_NSEC | servers | array<object> | Structured nameserver identities ({ns,address} object). |
DS10_INCONSISTENT_NSEC3 | servers | array<object> | Structured nameserver identities ({ns,address} object). |
DS10_INCONSISTENT_NSEC_NSEC3 | servers | array<object> | Structured nameserver identities ({ns,address} object). |
DS10_MIXED_NSEC_NSEC3 | servers | array<object> | Structured nameserver identities ({ns,address} object). |
DS10_NONSTANDARD_NSEC_RESPONSE | servers | array<object> | Structured nameserver identities ({ns,address} object) that placed the NSEC RR in the authority section. |
DS10_NSEC3PARAM_GIVES_ERR_ANSWER | servers | array<object> | Structured nameserver identities ({ns,address} object). |
DS10_NSEC3PARAM_MISMATCHES_APEX | servers | array<object> | Structured nameserver identities ({ns,address} object). |
DS10_NSEC3PARAM_QUERY_RESPONSE_ERR | servers | array<object> | Structured nameserver identities ({ns,address} object). |
DS10_NSEC3_ERR_TYPE_LIST | servers | array<object> | Structured nameserver identities ({ns,address} object). |
DS10_NSEC3_MISMATCHES_APEX | servers | array<object> | Structured nameserver identities ({ns,address} object). |
DS10_NSEC3_MISSING_SIGNATURE | servers | array<object> | Structured nameserver identities ({ns,address} object). |
DS10_NSEC3_NODATA_MISSING_SOA | servers | array<object> | Structured nameserver identities ({ns,address} object). |
DS10_NSEC3_NODATA_WRONG_SOA | domain, servers | string, array<object> | Wrong SOA owner domain and affected nameservers as {ns,address} items. |
DS10_NSEC3_NO_VERIFIED_SIGNATURE | servers | array<object> | Structured nameserver identities ({ns,address} object) lacking any verified NSEC3 signature. |
DS10_NSEC3_RRSIG_EXPIRED | keytag, servers | int, array<object> | Keytag and affected nameservers as {ns,address} items. |
DS10_NSEC3_RRSIG_NOT_YET_VALID | keytag, servers | int, array<object> | Keytag and affected nameservers as {ns,address} items. |
DS10_NSEC3_RRSIG_NO_DNSKEY | keytag, servers | int, array<object> | Keytag and affected nameservers as {ns,address} items. |
DS10_NSEC3_RRSIG_VERIFY_ERROR | keytag, reason, servers | int, string, array<object> | Keytag, reason and affected nameservers as {ns,address} items. reason is labels when the Labels field does not fit the owner and Signer’s Name, signature otherwise (Implementation Notes). |
DS10_NSEC_ERR_TYPE_LIST | servers | array<object> | Structured nameserver identities ({ns,address} object). |
DS10_NSEC_GIVES_ERR_ANSWER | servers | array<object> | Structured nameserver identities ({ns,address} object). |
DS10_NSEC_MISMATCHES_APEX | servers | array<object> | Structured nameserver identities ({ns,address} object). |
DS10_NSEC_MISSING_SIGNATURE | servers | array<object> | Structured nameserver identities ({ns,address} object). |
DS10_NSEC_NODATA_MISSING_SOA | servers | array<object> | Structured nameserver identities ({ns,address} object). |
DS10_NSEC_NODATA_WRONG_SOA | domain, servers | string, array<object> | Wrong SOA owner domain and affected nameservers as {ns,address} items. |
DS10_NSEC_NO_VERIFIED_SIGNATURE | servers | array<object> | Structured nameserver identities ({ns,address} object) lacking any verified NSEC signature. |
DS10_NSEC_QUERY_RESPONSE_ERR | servers | array<object> | Structured nameserver identities ({ns,address} object). |
DS10_NSEC_RRSIG_EXPIRED | keytag, servers | int, array<object> | Keytag and affected nameservers as {ns,address} items. |
DS10_NSEC_RRSIG_NOT_YET_VALID | keytag, servers | int, array<object> | Keytag and affected nameservers as {ns,address} items. |
DS10_NSEC_RRSIG_NO_DNSKEY | keytag, servers | int, array<object> | Keytag and affected nameservers as {ns,address} items. |
DS10_NSEC_RRSIG_VERIFY_ERROR | keytag, reason, servers | int, string, array<object> | Keytag, reason and affected nameservers as {ns,address} items. reason is labels when the Labels field does not fit the owner and Signer’s Name, signature otherwise (Implementation Notes). |
DS10_SERVER_NO_DNSSEC | servers | array<object> | Structured nameserver identities ({ns,address} object) without DNSKEY among mixed responders. |
DS10_ZONE_NO_DNSSEC | servers | array<object> | Structured nameserver identities ({ns,address} object) without DNSKEY when zone appears unsigned. |
IPV4_DISABLED | ns | string | Nameserver identity (ns name only; use address for IP) skipped on IPv4. |
IPV4_DISABLED | address | string | Nameserver IP address for the same endpoint. |
IPV4_DISABLED | query_type | string | Query type skipped (DNSKEY, NSEC, NSEC3PARAM). |
IPV6_DISABLED | ns | string | Nameserver identity (ns name only; use address for IP) skipped on IPv6. |
IPV6_DISABLED | address | string | Nameserver IP address for the same endpoint. |
IPV6_DISABLED | query_type | string | Query type skipped (DNSKEY, NSEC, NSEC3PARAM). |
TEST_CASE_END | testcase | string | Testcase display name (DNSSEC10). |
TEST_CASE_START | testcase | string | Testcase display name (DNSSEC10). |
Severity Levels Per Tag
| Tag | Level | Notes |
|---|---|---|
DS10_ALGO_NOT_SUPPORTED_BY_ZM | NOTICE | Default from share/profile.json (test_levels.DNSSEC). |
DS10_ERR_MULT_NSEC | ERROR | Default from share/profile.json (test_levels.DNSSEC). |
DS10_ERR_MULT_NSEC3 | ERROR | Default from share/profile.json (test_levels.DNSSEC). |
DS10_EXPECTED_NSEC_NSEC3_MISSING | ERROR | Default from share/profile.json (test_levels.DNSSEC). |
DS10_HAS_NSEC | INFO | Default from share/profile.json (test_levels.DNSSEC). |
DS10_HAS_NSEC3 | INFO | Default from share/profile.json (test_levels.DNSSEC). |
DS10_INCONSISTENT_NSEC | ERROR | Default from share/profile.json (test_levels.DNSSEC). |
DS10_INCONSISTENT_NSEC3 | ERROR | Default from share/profile.json (test_levels.DNSSEC). |
DS10_INCONSISTENT_NSEC_NSEC3 | ERROR | Default from share/profile.json (test_levels.DNSSEC). |
DS10_MIXED_NSEC_NSEC3 | ERROR | Default from share/profile.json (test_levels.DNSSEC). |
DS10_NONSTANDARD_NSEC_RESPONSE | NOTICE | Default from share/profile.json (test_levels.DNSSEC). |
DS10_NSEC3PARAM_GIVES_ERR_ANSWER | ERROR | Default from share/profile.json (test_levels.DNSSEC). |
DS10_NSEC3PARAM_MISMATCHES_APEX | ERROR | Default from share/profile.json (test_levels.DNSSEC). |
DS10_NSEC3PARAM_QUERY_RESPONSE_ERR | ERROR | Default from share/profile.json (test_levels.DNSSEC). |
DS10_NSEC3_ERR_TYPE_LIST | ERROR | Default from share/profile.json (test_levels.DNSSEC). |
DS10_NSEC3_MISMATCHES_APEX | ERROR | Default from share/profile.json (test_levels.DNSSEC). |
DS10_NSEC3_MISSING_SIGNATURE | ERROR | Default from share/profile.json (test_levels.DNSSEC). |
DS10_NSEC3_NODATA_MISSING_SOA | ERROR | Default from share/profile.json (test_levels.DNSSEC). |
DS10_NSEC3_NODATA_WRONG_SOA | ERROR | Default from share/profile.json (test_levels.DNSSEC). |
DS10_NSEC3_NO_VERIFIED_SIGNATURE | ERROR | Default from share/profile.json (test_levels.DNSSEC). |
DS10_NSEC3_RRSIG_EXPIRED | ERROR | Default from share/profile.json (test_levels.DNSSEC). |
DS10_NSEC3_RRSIG_NOT_YET_VALID | ERROR | Default from share/profile.json (test_levels.DNSSEC). |
DS10_NSEC3_RRSIG_NO_DNSKEY | WARNING | Default from share/profile.json (test_levels.DNSSEC). |
DS10_NSEC3_RRSIG_VERIFY_ERROR | ERROR | Default from share/profile.json (test_levels.DNSSEC). |
DS10_NSEC_ERR_TYPE_LIST | ERROR | Default from share/profile.json (test_levels.DNSSEC). |
DS10_NSEC_GIVES_ERR_ANSWER | ERROR | Default from share/profile.json (test_levels.DNSSEC). |
DS10_NSEC_MISMATCHES_APEX | ERROR | Default from share/profile.json (test_levels.DNSSEC). |
DS10_NSEC_MISSING_SIGNATURE | ERROR | Default from share/profile.json (test_levels.DNSSEC). |
DS10_NSEC_NODATA_MISSING_SOA | ERROR | Default from share/profile.json (test_levels.DNSSEC). |
DS10_NSEC_NODATA_WRONG_SOA | ERROR | Default from share/profile.json (test_levels.DNSSEC). |
DS10_NSEC_NO_VERIFIED_SIGNATURE | ERROR | Default from share/profile.json (test_levels.DNSSEC). |
DS10_NSEC_QUERY_RESPONSE_ERR | ERROR | Default from share/profile.json (test_levels.DNSSEC). |
DS10_NSEC_RRSIG_EXPIRED | ERROR | Default from share/profile.json (test_levels.DNSSEC). |
DS10_NSEC_RRSIG_NOT_YET_VALID | ERROR | Default from share/profile.json (test_levels.DNSSEC). |
DS10_NSEC_RRSIG_NO_DNSKEY | WARNING | Default from share/profile.json (test_levels.DNSSEC). |
DS10_NSEC_RRSIG_VERIFY_ERROR | ERROR | Default from share/profile.json (test_levels.DNSSEC). |
DS10_SERVER_NO_DNSSEC | ERROR | Default from share/profile.json (test_levels.DNSSEC). |
DS10_ZONE_NO_DNSSEC | NOTICE | Default from share/profile.json (test_levels.DNSSEC). |
IPV4_DISABLED | DEBUG2 | Default from share/profile.json (test_levels.DNSSEC). |
IPV6_DISABLED | DEBUG2 | Default from share/profile.json (test_levels.DNSSEC). |
TEST_CASE_END | DEBUG | Default from share/profile.json (test_levels.DNSSEC). |
TEST_CASE_START | DEBUG | Default from share/profile.json (test_levels.DNSSEC). |
Differences From Upstream
- Differences (Upstream vs Gonemaster):
- Upstream: summary for
DS10_INCONSISTENT_NSEC_NSEC3describes two separate lists (ns_list_nsec,ns_list_nsec3). Gonemaster: emits a single combinedserversargument. - Upstream: most DS10 tags are documented with
servers. Gonemaster:DS10_ALGO_NOT_SUPPORTED_BY_ZMusesaddresseswhile other DS10 tags useservers. - Upstream: does not explicitly specify testcase boundary and per-query transport debug emissions in this testcase summary. Gonemaster: emits
TEST_CASE_START,TEST_CASE_END,IPV4_DISABLED, andIPV6_DISABLED. - NSEC-in-authority NODATA responses (RFC 4470 white-lies / minimally covering NSEC / RFC 9824 compact denial of existence, as used by e.g. AWS Route 53, Cloudflare, NS1): both upstream (since engine v9.0.0, see “Resolved upstream issues” below) and gonemaster treat NSEC-in-authority on the NSEC query as NSEC evidence equivalent to NSEC-in-answer and emit
DS10_NONSTANDARD_NSEC_RESPONSE(NOTICE) rather than a falseDS10_INCONSISTENT_NSEC. One difference remains: upstream performs NSEC type-list validation on the synthesized NSEC record (and may emitDS10_NSEC_INCORRECT_TYPE_LIST), while gonemaster deliberately skips that check because an RFC 4470 / RFC 9824 synthesized bitmap intentionally excludes the queried type and may carry NSEC3PARAM/NSEC3. All other checks (SOA, count, apex owner, signature) match. DS10_ERR_MULT_NSEC3PARAMis not emitted (the tag has been removed). RFC 5155 does not constrain the cardinality of the apexNSEC3PARAMRRset and a zone may legitimately publish more than oneNSEC3PARAMRR during a parameter (salt/iterations) rollover. Gonemaster follows the upstream removal: the apex-owner check (DS10_NSEC3PARAM_MISMATCHES_APEX) is applied to every NSEC3PARAM RR in the answer instead of only the first. Apex-hash verification for the NSEC3 chain itself uses each NSEC3 record’s own salt/iterations, so a multi-chain rollover is already validated correctly without a cardinality check.
- Upstream: summary for
- Resolved upstream issues:
- The NSEC-in-authority gap (false
DS10_INCONSISTENT_NSECfor RFC 4470 / RFC 9824 on-line signers, zonemaster/zonemaster#1424 ) is resolved upstream in engine v9.0.0 / Zonemaster v2026.1 (spec update #1478, implementation #1523/#1539): upstream now adds a NODATA-with-NSEC-in-authority branch and emitsDS10_NONSTANDARD_NSEC_RESPONSE. Gonemaster had already implemented this branch and tag ahead of the release.
- The NSEC-in-authority gap (false
- Potential upstream report:
no– the gap is now handled on both sides; only the type-list-validation difference noted above remains, and that is an intentional gonemaster choice rather than an upstream defect.
Implementation Notes
The following behaviors are implementation choices, not mandated by RFC 4034, RFC 4035, RFC 5155, RFC 4470 or RFC 9824:
- Reference time source: RRSIG validity checks use wall-clock time (
time.Now().UTC()) as the reference “now”. RFC 4034 section 3.1.5 requires checking whether signatures are currently valid; using wall-clock time rather than packet timestamps (asdnssec04does) is an implementation choice appropriate for aggregate multi-nameserver analysis where a single consistent reference point is preferred. - Deduplication by IP: The nameserver set is built by IP address; delegation and zone NS entries sharing the same IP are merged. First-seen nameserver identity string (
name/ip) is used in output arguments. The protocol does not specify how to handle NS records for the same IP from different sources. serversvsaddressesargument name: Most DS10 tags useservers(nameserver identity strings) whileDS10_ALGO_NOT_SUPPORTED_BY_ZMusesaddresses(raw IPs from the signature verification path). This asymmetry is an implementation-defined output format.- RFC 4470 / RFC 9824 white-lies NSEC handling: When the NSEC query returns a NODATA response with NSEC in the authority section (rather than NSEC in the answer section), this is recognized as NSEC evidence from an on-line signing / minimally covering NSEC (RFC 4470) or compact denial of existence (RFC 9824) implementation. RFC 9824 section 7.2 explicitly permits dynamically generated NSEC records for owner names that don’t exist or are ENTs, relaxing the RFC 4035 section 2.3 constraint. The synthesized NSEC record’s type bitmap intentionally excludes the queried type (NSEC) and may include normally-forbidden types (NSEC3PARAM), so type-list validation is skipped for this record. All other checks (SOA, count, apex owner, signature) are performed normally. For consistency purposes this evidence is treated identically to NSEC-in-answer.
- RRSIG verification is bounded: at most 8 RRSIGs over one RRset are considered, and at most 4 DNSKEYs with the key tag and algorithm of an RRSIG are tried for it, each in response order. RFC 4035 section 5.3.1 requires trying every DNSKEY that matches an RRSIG; a key tag is not a unique identifier (RFC 4034 Appendix B), so a zone chooses how many keys match, and the caps depart from that requirement. A cut logs
LIMIT_REACHEDwithboundrrsigs_per_rrsetorkeys_per_tag, once per testcase (DNSSEC Limits ). Each RRSIG is verified over one copy of the RRset. An RRSIG does not verify when its Labels field exceeds the label count of the RRset owner (RFC 4035 section 5.3.1). It also fails when the owner name rebuilt from that field (RFC 4035 section 5.3.2) is not at or below the Signer’s Name, or is the Signer’s Name but differs from the RRset owner.DS10_NSEC_RRSIG_VERIFY_ERRORandDS10_NSEC3_RRSIG_VERIFY_ERRORcarryreasonlabelsfor such an RRSIG andsignaturefor any other failure, one finding per key tag and reason.
Edge Cases And Limitations
- Nameserver processing is deduplicated by IP; all DS10 output tags except
DS10_ALGO_NOT_SUPPORTED_BY_ZMreportserversas nameserver identity strings (name/ip) rather than raw IPs. DS10_NSEC_NO_VERIFIED_SIGNATUREandDS10_NSEC3_NO_VERIFIED_SIGNATUREare suppressed per nameserver when at least one signature verifies for that nameserver.- Signature validity checks use testcase wall-clock time (
time.Now().UTC()), not packet capture timestamps. - An RRSIG past the first 8 over its RRset is not considered, and a DNSKEY past the first 4 with the key tag and algorithm of an RRSIG is not tried. A zone whose only valid signature or only verifying key lies past a cut is reported from what was considered: an RRSIG that no considered key verifies yields
DS10_NSEC_RRSIG_VERIFY_ERRORorDS10_NSEC3_RRSIG_VERIFY_ERROR.