What is an SOA record?

If you have been reading through the chapters on DNS record types, you have seen records that point your domain to servers, route email, verify ownership, and handle security. Each of those records exists inside something called a DNS zone. And every DNS zone has one record that comes before all the others. That record is the SOA record.

The SOA record does not point to a server. It does not route email. It does not verify anything. Instead, it holds the rules that tell nameservers how to manage the entire zone. Think of it as the table of contents for your domain's DNS. It does not contain the chapters, but it tells the system how those chapters are organized and when to look for new ones.

What does SOA stand for?

SOA stands for Start of Authority. The name tells you exactly what the record does. It marks the starting point of the DNS zone and declares which nameserver is the primary authority for that zone.

Every DNS zone has exactly one SOA record. You cannot have two, and you cannot have zero. It is a required part of the DNS standard. When a nameserver first loads information about your domain, the SOA record is the first thing it reads.

What is inside an SOA record?

An SOA record contains seven fields. Each one gives nameservers a specific piece of information about how to handle your DNS zone.

• Primary nameserver (MNAME) is the hostname of the main nameserver that holds the original copy of your DNS zone. All updates to your DNS records start here. Other nameservers copy from this one
• Admin email (RNAME) is the email address of the person responsible for the DNS zone. It is written in a slightly odd format where the @ symbol is replaced with a dot. So admin.yourdomain.com means admin@yourdomain.com
• Serial number is a version number for your DNS zone. Every time someone makes a change to any record in the zone, the serial number goes up. Secondary nameservers check this number to see if they need to download a fresh copy
• Refresh interval tells secondary nameservers how often (in seconds) to check the primary nameserver for updates. A typical value is 3600, which means every hour
• Retry interval tells secondary nameservers how long to wait before trying again if their last attempt to contact the primary nameserver failed. This is usually shorter than the refresh interval, often around 600 seconds (10 minutes)
• Expire time tells secondary nameservers how long they can keep serving data if they cannot reach the primary nameserver at all. Once this time runs out, the secondary nameserver stops answering queries for your domain. A common value is 604800 seconds (one week)
• Minimum TTL (negative caching TTL) tells other DNS servers how long to remember that a record does not exist. If someone asks for a subdomain that has no DNS record, this value controls how long that "does not exist" answer gets cached before the server checks again

You do not need to memorize these fields. The important thing to understand is that the SOA record gives nameservers a set of timing rules so they know when to sync, when to retry, and when to stop trusting old data.

Why does the SOA record exist?

Your domain's DNS records are not stored on a single server. They are copied across multiple nameservers around the world. When you change an A record or add a new MX record, that change starts on the primary nameserver. The secondary nameservers need to pick up that change and update their copies.

The SOA record is what makes this work. It tells secondary nameservers how often to check for changes, what to do if the primary nameserver is unavailable, and when to stop trusting their cached data entirely. Without these rules, nameservers would have no consistent way to stay in sync.

Do you need to edit your SOA record?

For the vast majority of brand owners, the answer is no. Your DNS provider creates and manages the SOA record automatically when you set up your domain. You do not need to configure it, update it, or think about it.

The only scenarios where someone might edit an SOA record are highly technical, like migrating DNS zones between providers or running your own nameservers. If you are using a managed DNS service (which is the standard setup for nearly every domain), your provider handles everything behind the scenes.

When does the SOA record matter for troubleshooting?

Even though you will probably never edit your SOA record, knowing it exists can help when things go wrong. Here are a few situations where the SOA record becomes relevant.

• DNS changes are not showing up. If you update a record and it takes longer than expected to appear, the SOA record's refresh interval might explain the delay. Secondary nameservers will not check for updates faster than this interval allows
• Your domain stops resolving after a provider outage. If your primary nameserver goes offline for an extended period, the expire time in the SOA record determines how long secondary nameservers keep serving your records. Once the expire time passes, your domain goes dark until the primary nameserver comes back online
• Zone transfers are failing. If you are moving your DNS to a new provider and the zone transfer keeps failing, the SOA record's serial number and timing values can reveal mismatches that are preventing the new nameservers from syncing correctly

For most brands, these are edge cases. But understanding that the SOA record controls how DNS works behind the scenes makes it easier to ask the right questions when something is not behaving as expected.

What happens if the SOA record has wrong values?

Incorrect SOA values do not break your website instantly. They cause slow, hard-to-diagnose problems with how your DNS updates spread across the internet.

• A refresh interval that is too long means DNS changes take longer to show up everywhere
• An expire time that is too short means secondary nameservers give up quickly if the primary goes down, making your domain more fragile during outages
• A serial number that does not increment means secondary nameservers think nothing changed and never download the update

This is why DNS providers handle the SOA record for you. The values need to be balanced carefully, and getting them wrong creates problems that stay invisible until something goes down.

How WEMASY handles SOA records

When you connect a domain to WEMASY, the platform manages DNS configuration as part of the setup process. SOA records are handled at the infrastructure level. You will not see an SOA record in your domain settings because there is nothing you need to change.

WEMASY's hosting includes DNS management, SSL certificates, and nameserver configuration. The SOA values are set to keep your DNS zone in sync across nameservers without any manual work on your end. See what is included in each plan on the WEMASY pricing page.

What comes next

Now that you understand how the SOA record controls the timing and synchronization of your DNS zone, the next chapter covers TTL in DNS. TTL determines how long any individual DNS record is cached before servers check for a fresh copy, and it connects directly to the timing concepts in the SOA record. For an overview of all record types and when to use each one, see the chapter on DNS record types.

Frequently asked questions