← Back to blog

SOA record: what each field means, a worked example, and the serial format

Domainee·
soa recordwhat is an soa recorddns soa recordsoa record examplesoa record fields
SOA record: what each field means, a worked example, and the serial format

An SOA (Start of Authority) record is the required record at the top of every DNS zone. It names the primary nameserver, the zone admin's contact and the serial number and timers that govern zone transfers and caching.

Every zone has exactly one, always at the zone apex. Managed DNS providers usually create it and maintain it for you, so you rarely edit it. You will still meet it in dig output, in zone files, and when a brand-new record looks broken for an hour.

What is an SOA record?

The SOA record is the first record in a zone file. It says who is authoritative for the zone and how secondary nameservers should keep their copy fresh.

One SOA per zone. Always at the apex (example.com, not www.example.com).

Here is what it looks like in a dig result (illustrative values):

$ dig example.com SOA +short
ns1.example.com. hostmaster.example.com. 2026111201 7200 3600 1209600 3600

Seven values, one line. The next section takes them one at a time.

SOA record fields explained

FieldMeaningUnitWhat changing it does
MNAMEPrimary nameserver for the zoneHostnamePoints secondaries and tools at a different primary
RNAMEZone admin contact, with . in place of @Hostname-style emailChanges who is listed as the contact
SERIALVersion number of the zoneUnsigned 32-bit integerA higher value tells secondaries to pull a fresh copy
REFRESHHow often a secondary checks the primary for a new serialSecondsShorter means faster pickup, more queries
RETRYHow long a secondary waits before retrying after a failed refreshSecondsShorter means quicker recovery attempts
EXPIREHow long a secondary keeps answering without reaching the primarySecondsPast this, the secondary stops serving the zone
MINIMUMNegative-caching TTLSecondsControls how long resolvers cache a "does not exist" answer

The RNAME quirk

The admin email is written with a dot instead of @. So hostmaster.example.com. means hostmaster@example.com. If the local part itself contains a dot, it is escaped with a backslash.

MINIMUM is not a default TTL anymore

This is the field most guides get wrong. MINIMUM started life as the default TTL for records in the zone. Since RFC 2308 it is the negative-caching TTL: how long a resolver may remember that a name does not exist. Per RFC 2308, the negative TTL a resolver uses is the lower of the SOA record's own TTL and MINIMUM.

Hold that thought. It comes back in the custom-domains section.

A worked SOA record example, line by line

Here is a full SOA as it would appear in a zone file:

example.com. 3600 IN SOA ns1.example.com. hostmaster.example.com. (
    2026111201 ; serial
    7200       ; refresh
    3600       ; retry
    1209600    ; expire
    3600       ; minimum
)

Walking through it:

  • ns1.example.com. is the primary nameserver (MNAME).
  • hostmaster.example.com. is hostmaster@example.com (RNAME).
  • 2026111201 is the serial: 12 Nov 2026, first revision that day.
  • 7200 refresh is 2 hours. Every 2 hours, a secondary asks the primary for its serial.
  • 3600 retry is 1 hour. If that check fails, the secondary tries again an hour later.
  • 1209600 expire is 14 days. If a secondary can't reach the primary for 14 days, it stops answering for the zone.
  • 3600 minimum is 1 hour. A "no such name" answer can be cached for up to an hour.

Sensible values vary by provider. Most managed DNS sets them for you, so treat these as an example, not a recommendation.

SOA serial number format (YYYYMMDDnn)

The serial is a version counter. A secondary compares its stored serial with the primary's. If the primary's is higher, the secondary pulls a zone transfer. If not, it assumes nothing changed.

The common convention is date-based: YYYYMMDDnn.

2026111201
^^^^        year   2026
    ^^      month  11
      ^^    day    12
        ^^  revision of the day  01

So 2026111201 is the first change on 12 Nov 2026. The second is 2026111202. With two digits for nn, you get 99 revisions a day if you start at 01. The ten-digit value fits comfortably in the 32-bit serial field.

The date format is a convention, not a rule. A plain integer you bump by one works just as well. Many providers do exactly that.

What goes wrong

If the serial doesn't increase after a change, secondaries think nothing happened and keep serving stale data. If it goes backwards, same story: the secondary sees a lower number and ignores the update. Fixing it means moving the serial above what the secondaries already hold.

How to look up an SOA record

Two commands cover it:

dig example.com SOA
nslookup -type=soa example.com

In the dig answer section, read the data left to right: primary nameserver, admin contact, serial, then the four timers. Add +short for just the data.

To inspect a domain's records in the browser, try the free DNS record lookup. It needs no signup.

Can you edit an SOA record?

Usually no, and you rarely should. Managed DNS providers generate the SOA and bump the serial automatically whenever you change a record.

When you would edit it:

  • Self-hosted BIND or similar. You own the zone file, so you own the serial.
  • Lowering MINIMUM before a migration. A shorter negative-caching TTL means fewer stale "not found" answers while you cut over.
  • Fixing a bad RNAME. A typo'd contact address is worth correcting.

Never delete it. A zone without an SOA is broken.

Why the SOA matters when customers connect a custom domain

You will never touch your customers' SOA records. But two of its quirks explain tickets you will get.

Negative caching makes a correct record look wrong

A customer checks app.theirbrand.com before adding the CNAME. Their resolver gets "does not exist" and caches it for up to the SOA's MINIMUM time. They add the CNAME. It's correct. It still looks broken, because the cached "no" is still being served.

That's negative caching, and it's not a bug. It's one reason a right record can look wrong for a while. For the general picture, see what DNS TTL values mean in practice and DNS propagation.

What Domainee does about it: each domain is re-checked every 5 minutes, or on demand via POST /v1/domains/{id}/check. A hostname that isn't resolving yet reports dns_not_resolving in monitorStatus. Other states include dns_incorrect, pending_ssl and active_ssl, so you can tell "not there yet" from "wrong" from "working".

curl -X POST https://api.domainee.dev/v1/domains/{id}/check \
  -H "Authorization: Bearer $DOMAINEE_API_KEY"

That re-check is ours. A customer's own resolver cache is theirs, so "it's live on our side, give it a bit" is sometimes the honest answer.

The apex is crowded

The SOA and NS records live at the zone apex. A CNAME can't coexist with other records at the same name, so it can't live at the root. That's the short version of why a CNAME at the root is impossible.

Domainee supports both apex domains and subdomains. Where an apex provider disallows CNAME, we offer two anycast A records instead.

What your customer actually does

POST /v1/domains takes a hostname and an originUrl and returns a CNAME record for the customer to add. The target is edge.domainee.dev. One CNAME. No SOA edits, no registrar account. GET /v1/domains/{id}/instructions detects the customer's DNS provider from public NS records and returns provider-specific steps.

SOA record FAQ

What is an SOA record?

An SOA (Start of Authority) record is the mandatory first record in a DNS zone. It names the primary nameserver and the zone admin contact, and it carries the serial number and timers that control zone transfers and negative caching.

What is the SOA serial number format?

The common format is YYYYMMDDnn: year, month, day and a two-digit revision. 2026111201 is the first change on 12 Nov 2026. It's a convention. Any integer that increases with every zone change works.

What is the minimum TTL in an SOA record used for?

MINIMUM is the negative-caching TTL under RFC 2308. It sets how long resolvers may cache a "name does not exist" answer. It no longer acts as the zone's default record TTL.

Can I edit or delete my SOA record?

You can edit it on self-hosted DNS, but managed providers usually handle it and bump the serial for you. Never delete it. A zone without an SOA is broken.

How many SOA records can a domain have?

One per zone. It sits at the zone apex. Subdomains don't get their own SOA unless they are delegated as separate zones.

How do I check a domain's SOA record?

Run dig example.com SOA or nslookup -type=soa example.com. Add +short to dig for only the data. The answer lists primary nameserver, admin contact, serial, refresh, retry, expire and minimum.

Next step

You can't do much about your customers' SOA records. You can stop them thinking about DNS.

Inspect any domain with the free DNS record lookup. Then read the docs or sign up. 20 custom domains and 100 GB/month are free, forever.

FAQ

What is an SOA record?

An SOA (Start of Authority) record is the mandatory first record in a DNS zone. It names the primary nameserver and the zone admin contact, and it carries the serial number and timers that control zone transfers and negative caching. Every zone has exactly one, at the apex.

What does SOA stand for in DNS?

SOA stands for Start of Authority. The record marks where a zone's authority begins: which nameserver is the primary source of truth, who administers the zone, and which timing values secondary nameservers and resolvers should follow when copying and caching zone data.

What are the fields in an SOA record?

An SOA record has seven fields: MNAME (primary nameserver), RNAME (admin contact with a dot in place of @), SERIAL (zone version), REFRESH, RETRY and EXPIRE (secondary nameserver timers, in seconds), and MINIMUM (the negative-caching TTL).

What is the SOA serial number format?

The common format is YYYYMMDDnn: year, month, day and a two-digit revision counter. So 2026111201 is the first change on 12 Nov 2026. It's only a convention. Any integer that increases with every zone change works, and many providers simply add one.

What is the minimum TTL in an SOA record used for?

MINIMUM is the negative-caching TTL under RFC 2308. It tells resolvers how long they may cache a "name does not exist" answer. It started as a default record TTL, but that is no longer its role, which is why many older guides describe it wrongly.

Can I edit or delete my SOA record?

You can edit it if you run your own DNS, such as BIND, for example to lower MINIMUM before a migration or fix a bad RNAME. Managed providers usually generate it and bump the serial automatically. Never delete it: a zone without an SOA is broken.

How many SOA records can a domain have?

Exactly one SOA record per zone, always at the zone apex. A subdomain only has its own SOA if it has been delegated as a separate zone. Within a normal zone, a second SOA record is invalid and will cause errors.

How do I check a domain's SOA record?

Run dig example.com SOA, or nslookup -type=soa example.com on systems without dig. Add +short to dig for just the data. Read it left to right: primary nameserver, admin contact, serial, refresh, retry, expire, then minimum.

What is the RNAME in an SOA record and why is there no @?

RNAME is the zone admin's email address. The @ character already has a special meaning in zone files, so the format replaces it with a dot: hostmaster.example.com. means hostmaster@example.com. A dot inside the local part is escaped with a backslash.

Does the SOA record affect how fast DNS changes propagate?

Partly. REFRESH, RETRY and the serial govern how fast secondary nameservers pick up changes. MINIMUM controls how long resolvers cache a not-found answer, which is why a new record can look missing for a while. Record TTLs cover everything else.

Why can't I put a CNAME at the apex when an SOA is there?

A CNAME can't coexist with any other record at the same name. The apex always holds the SOA and NS records, so a CNAME there would conflict with them. Some providers offer ALIAS or CNAME flattening, or you can use A records instead.

SOA Record: Fields, Example and Serial Format | Domainee | Domainee