Zone01 (zone01)

Status: Final

Purpose

• Validate SOA MNAME handling for the child zone: name sanity, resolvability, authority behavior, and serial-based master inference.

Preconditions And Inputs

• Preconditions:
  • A zone.Zone object is available.
  • A recursor is available on the zone object.
• Required inputs:
  • Nameserver addresses from methods.Method4and5.
  • Child NS names from methods.Method3.
  • Recursive A/AAAA lookups for SOA MNAME hostnames.
  • Direct SOA queries to SOA MNAME host/IP combinations.
• Profile/config knobs that affect behavior:
  • net.ipv4 and net.ipv6 control whether transport families are queried.

Algorithm And Decision Flow

1. Emit TEST_CASE_START.
2. Query each nameserver from Method4and5 for SOA at the child zone apex.
3. For each response, continue only when all are true:
   • response exists;
   • RCODE=NOERROR;
   • AA=true;
   • at least one SOA RR for the zone name exists.
4. From accepted SOA answers, collect:
   • SOA MNAME values;
   • SOA serial values from child nameservers;
   • source nameserver IPs where MNAME is localhost or ..
5. Emit:
   • Z01_MNAME_IS_LOCALHOST when any accepted response had MNAME localhost;
   • Z01_MNAME_IS_DOT when any accepted response had MNAME ..
6. For each non-localhost and non-dot MNAME:
   • If MNAME is not in Method3 child NS name set, emit Z01_MNAME_NOT_IN_NS_LIST.
   • Resolve MNAME addresses using recursor lookup (A/AAAA).
   • For each resolved address:
     • If localhost address (127.0.0.1 or ::1), emit Z01_MNAME_HAS_LOCALHOST_ADDR.
     • Else query SOA directly against that mname/ip.
       • If no response, emit Z01_MNAME_NO_RESPONSE.
       • If RCODE != NOERROR, emit Z01_MNAME_UNEXPECTED_RCODE.
       • If no SOA in answer, emit Z01_MNAME_MISSING_SOA_RECORD.
       • If SOA present but AA=false, emit Z01_MNAME_NOT_AUTHORITATIVE.
       • If SOA present and AA=true, store returned serial for master comparison.
   • If no MNAME address was resolved, emit Z01_MNAME_NOT_RESOLVE (subject to the implementation caveat documented below).
7. If at least one authoritative MNAME serial was collected, compare each collected MNAME serial against serials gathered from child nameservers using RFC1982 ordering:
   • If any child nameserver serial is greater than the candidate MNAME serial, classify as not master.
   • Otherwise classify as master.
8. Emit:
   • Z01_MNAME_NOT_MASTER for non-master MNAME host/IPs, with serial context;
   • Z01_MNAME_IS_MASTER for master-candidate MNAME host/IPs.
9. Emit TEST_CASE_END.

Emitted Tags (Possible Set)

Tag Arguments

Severity Levels Per Tag

SOA MNAME is never used for authoritative nameserver discovery and is not part of normal DNS lookup, so operational impact of MNAME errors is limited. Accordingly, no MNAME-related tag exceeds NOTICE severity.

Differences From Upstream

• Upstream reference: zone01.md
• Differences (Upstream vs Gonemaster):
  • Upstream: does not describe testcase boundary debug markers in testcase outputs. Gonemaster: emits TEST_CASE_START and TEST_CASE_END.
  • Upstream: describes MNAME non-resolve handling per MNAME name. Gonemaster: uses a cumulative foundIP counter across all MNAME names, which can suppress Z01_MNAME_NOT_RESOLVE for later unresolved MNAME values after any earlier MNAME resolved.
  • Upstream: describes processing a name server IP set. Gonemaster: iterates raw Method4and5 output (no testcase-local IP deduplication before initial SOA probing).
• Potential upstream report:
  • no

Edge Cases And Limitations

• Only child SOA responses that are NOERROR, authoritative, and include SOA for the zone name contribute MNAME candidates.
• If no such candidate is collected, the testcase ends without emitting a dedicated “missing candidate MNAME” result tag.
• Transport-family skips (IPV4_DISABLED/IPV6_DISABLED) can be emitted by shared helper paths, but these tags are currently outside this testcase metadata contract.