What is an SOA record?
Every DNS zone has exactly one SOA (start of authority) record. It names the primary nameserver and the person responsible, and it carries the numbers that control how secondary nameservers copy the zone.
The serial number goes up with every change. Secondary servers compare serials to know when to fetch a new copy, which makes it the quickest way to tell whether a change has reached all nameservers.
How to read an SOA record
In a zone file, the record looks like this:
example.com. 3600 IN SOA ns.example.com. admin.example.com. 2026111601 7200 3600 1209600 3600
- Primary nameserver (MNAME).
- Contact e-mail (RNAME), with the @ written as a dot.
- Serial: the zone's version number.
- Refresh: how often secondaries check for a new serial.
- Retry: how long they wait after a failed check.
- Expire: how long they keep answering without contact with the primary.
- Minimum: how long resolvers cache "this name does not exist" answers.
From the command line
Look up SOA records without this site.
On macOS and Linux, use dig:
dig example.com SOA +short
On Windows, use nslookup:
nslookup -type=SOA example.com
To skip caches, ask one of the domain’s nameservers directly: dig @ns1.example.net example.com SOA. The “Its own nameservers” option on the result page does the same.
Questions and answers
My nameservers show different serial numbers. What does that mean?
A secondary has not copied the latest zone yet. If it stays that way longer than the refresh time, zone transfers are failing. The Trace tab shows the serial of every nameserver side by side.
A subdomain shows no SOA record. Why?
SOA records exist only at the top of a zone. For a name inside the zone, such as www, the lookup returns nothing; look up the domain itself.