Every zone has exactly one SOA (start of authority) record. It names the primary nameserver and a contact, carries the serial number secondaries use to spot changes, and sets how long “this name does not exist” may be cached.
| Type number | 6 |
| How many | Exactly one, at the zone apex |
| Set by | Usually the DNS host, not you |
| Defined in | RFC 1035 §3.3.13 |
Look up the SOA records of any name
One question to DNS, answered as it is. You can change the record type too.
What it does
Refresh, retry and expire tell secondary nameservers how often to check the primary for a new serial, how soon to retry after a failure, and when to stop answering if the primary stays unreachable.
The last field, minimum, now means the negative-caching time: how long a resolver may remember that a name or record does not exist (RFC 2308) — capped by the SOA record’s own TTL. A long value means a newly added record can stay invisible to people who looked for it just before.
How it is written
| Field | Meaning |
|---|---|
| MNAME | The primary nameserver |
| RNAME | The contact mailbox, with the @ written as a dot |
| Serial | Raised on every change; often YYYYMMDDnn |
| Refresh / Retry / Expire | Timers for secondary nameservers, in seconds |
| Minimum | Negative-caching time, in seconds |
Examples
example.com. 3600 IN SOA ns1.example.net. hostmaster.example.com. 2026092501 7200 3600 1209600 3600
Serial 2026092501, secondaries check every two hours, and a missing name is cached for an hour.
Common mistakes
- A negative-caching time of a day or more, so new records seem slow to appear.
- On self-run nameservers, forgetting to raise the serial, so secondaries never pick up the change.
What we recommend
Keep the minimum at an hour or less. On a managed DNS host, leave the SOA to the host.
Sources
Checked on 25 September 2026 against these official sources:
- RFC 1035: Domain names — rfc-editor.org