Skip to content
AdminKit

SOA record

What is SOA record?

An SOA record is the first record in every DNS zone, naming the zone's primary nameserver, administrator contact, and timing values that control how secondary nameservers replicate it. AdminKit's DNS Lookup tool shows a domain's SOA record alongside its other DNS records in one check.

By AdminKit team, Netbase JSC · Updated

An SOA (Start of Authority) record is the first record in every DNS zone, naming the zone’s primary authoritative nameserver and administrator contact, plus a set of timing values — serial number, refresh, retry, expire, and minimum/negative-cache TTL — that control how secondary nameservers replicate the zone and how long a negative answer (a domain or record that doesn’t exist) can be cached, the same fields Cloudflare’s explainer on SOA records breaks down one by one. The serial number is incremented on every zone change so secondaries know to pull an update; a serial that doesn’t increase after an edit is a common, easy-to-miss cause of changes that silently fail to replicate to secondary nameservers. RIPE-203, Recommendations for DNS SOA Values, suggests writing the serial in a date-based YYYYMMDDnn form and gives example refresh, retry, expire and minimum values for small and stable zones. Unlike most record types, there is exactly one SOA record per zone, and it’s typically surfaced alongside a domain’s other records rather than looked up on its own, since it describes the zone itself rather than resolving to an address. That minimum value is exactly the TTL a resolver uses to cache an NXDOMAIN response for a name that doesn’t exist at all — see the negative caching entry for how that cached non-answer is actually used. A primary nameserver doesn’t have to wait for the refresh interval to elapse either: DNS NOTIFY lets it tell secondaries the serial number just changed, so they can check and resynchronize right away. SOA records are defined in RFC 1035 and listed as RR type 6 in IANA’s DNS Parameters registry, and the minimum field’s negative-caching behavior is specified separately in RFC 2308.

AdminKit groups sOA record under its DNS cluster — browse the AdminKit glossary index for other related terms.

Frequently asked questions

Why would a DNS change not show up on secondary nameservers?

A secondary only pulls an update when the SOA record's serial number increases; if the serial wasn't incremented after an edit, secondaries have no signal that anything changed, which is a common, easy-to-miss cause of a zone change silently failing to replicate.

How many SOA records does a DNS zone have?

Exactly one -- unlike most record types, there's only a single SOA record per zone, since it describes the zone itself rather than resolving to an address.

What does the SOA record's minimum field actually control?

It sets the TTL a resolver uses to cache a negative answer, such as an NXDOMAIN response for a name that doesn't exist at all, as specified in RFC 2308.

Does a primary nameserver have to wait for the refresh interval to notify secondaries of a change?

No -- DNS NOTIFY lets a primary tell secondaries the serial number just changed so they can check and resynchronize immediately, rather than waiting for the refresh interval to elapse.