What the thing is
The SOA record is a DNS resource record containing administrative metadata for a zone. It is required for zone transfers and RFC 1035 compliance.
Where it came from
It was defined in RFC 1035, the 1987 specification that codified core DNS resource record types and message formats.
What it gets right
It enforces a minimal, mandatory coordination protocol for DNS zone replication. It standardises responsibility (via MNAME and RNAME), versioning (SERIAL), and timing (REFRESH, RETRY, EXPIRE, MINIMUM).
What it gets wrong
It assumes a single authoritative primary master—a model increasingly at odds with modern distributed, multi-master, or cloud-native DNS deployments.
Why it matters now
It remains the non-negotiable anchor of DNS zone integrity—every valid zone still requires one, and every misconfigured SOA still breaks delegation, caching, and propagation.
Is it worth your time
Yes—if you manage DNS infrastructure, troubleshoot zone transfers, or audit zone compliance. No—if you’re looking for cultural resonance, narrative, or human-scale expression.



