The SOA record in depth
What it is
SOA = Start of Authority (not "state of authority"). Every zone has exactly one SOA record, at its apex. It declares the zone's primary authoritative source, an admin contact, and timers used by secondary servers and negative caching.
example.com. 900 IN SOA ns-1234.awsdns-12.org. awsdns-hostmaster.amazon.com. (
1 ; SERIAL
7200 ; REFRESH (2 h)
900 ; RETRY (15 min)
1209600 ; EXPIRE (14 days)
86400 ) ; MINIMUM (negative-caching TTL cap)
(This is essentially Route 53's default SOA.)
dig SOA example.com +multiline
dig SOA example.com +short
Field by field
| Field | Meaning | Notes |
|---|---|---|
| MNAME | The primary name server for the zone | Secondaries know where to pull from; dynamic DNS updates go here |
| RNAME | The administrator's email address, with the @ written as a dot |
hostmaster.example.com. = [email protected] (a dot in the local part is escaped \.) |
| SERIAL | Version number of the zone | Must increase on every change; secondaries compare it to decide whether to transfer |
| REFRESH | How often secondaries check the primary's serial | e.g. 3600 = hourly (NOTIFY makes this mostly a fallback) |
| RETRY | How soon a secondary retries if a refresh check fails | Shorter than refresh, e.g. 600 |
| EXPIRE | How long a secondary keeps serving the zone without reaching the primary | After this it stops answering for the zone (SERVFAIL) rather than serve possibly stale data — e.g. 1209600 = 14 days |
| MINIMUM | Historically the default TTL; today the negative-caching TTL (RFC 2308) | Negative answers are cached for min(SOA TTL, MINIMUM) |
Worked example — refresh 3600, retry 600, expire 1209600: secondaries check the serial every hour; if the primary is unreachable they retry every 10 minutes; if they can't reach it for 14 days, they stop serving the zone.
Serial numbers
- Common convention: YYYYMMDDnn —
2026102501= first change on 25 Oct 2026;2026102502= second change that day. Unix timestamps and simple counters are also fine. - Forgetting to bump the serial after editing a BIND zone file is a classic mistake: secondaries see the same serial and don't pull the change, so different servers return different answers.
- The serial uses 32-bit sequence-space arithmetic, so it can wrap carefully if ever set wrong — but you can't simply decrease it.
- In Route 53, you don't manage the serial — Route 53 handles propagation to its servers itself (and doesn't use classic zone transfers).
Negative caching from the SOA
When a name doesn't exist, the authoritative server returns NXDOMAIN with the SOA record in the authority section; resolvers cache that negative answer for min(SOA TTL, MINIMUM). With Route 53's defaults (SOA TTL 900, MINIMUM 86400) that's 15 minutes. To change it in Route 53, edit the SOA record — its TTL and/or the last field.