Skip to content
inetGeek

SOA record

SOA

The SOA record marks the start of authority for a zone and carries the parameters that govern how it is transferred and cached.

Check this on a domain with DNS Lookup →

01.

What an SOA record contains

Every zone has exactly one SOA record at its apex. It names the primary nameserver and an administrative contact, and carries a serial number plus several timers.

The administrative contact is an email address written with a dot in place of the @ sign, which is why it looks like a hostname rather than an address.

02.

The serial number

Secondary nameservers use the serial number to decide whether their copy of the zone is current. A secondary that sees a higher serial on the primary transfers the zone again.

A serial that fails to increase after an edit is a classic cause of secondaries serving stale data indefinitely. The common convention is a date-based format such as 2026090501, though any increasing number works.

Why the serial mattersprimary → secondary

primary

serial

www A

secondary

serial

www A

Illustrative zone. A secondary compares serials and only transfers when the primary's is higher; an edit that leaves the serial alone is invisible to it.
03.

The minimum field is negative caching

The final SOA field is named "minimum" but no longer means a minimum TTL. RFC 2308 redefined it as the TTL for negative answers — how long a resolver may remember that a name does not exist.

A high value here means that creating a record someone has already queried for can take a long time to become visible, even though the record itself has a short TTL.

Related records