An SOA record (Start of Authority) is the first record in every DNS zone and contains the basic information about your domain: which nameserver is responsible, who manages it technically, and how often other nameservers should refresh the data. You usually don’t need to create it yourself, but if you manage DNS in Plesk or with another provider, it’s useful to know what the values mean and when to adjust them.
What exactly is an SOA record
Every DNS zone, meaning every domain, starts with an SOA record. It’s separate from records like A, MX or TXT and isn’t used to route traffic. Instead, it tells other nameservers and resolvers how to handle the zone: who owns the data and how often it should be checked for changes.
This is especially important if you use multiple nameservers (for example a primary and a secondary one), or if your domain moves to a different host. Without a correct SOA record, secondary nameservers won’t know when to fetch a new copy of the zone.
Which fields does an SOA record contain
An SOA record looks cryptic, but consists of a limited number of parts:
- Primary nameserver: the nameserver that serves as the source for the zone.
- Hostmaster email: the contact address of the administrator, written with a dot instead of an @.
- Serial: a sequence number you increase with every change in the zone, so secondary nameservers know something has changed.
- Refresh: how often a secondary nameserver should check for updates.
- Retry: how long to wait before a new attempt if the previous check failed.
- Expire: after how much time a secondary nameserver considers the data expired if there’s no contact with the primary server.
- Minimum TTL: how long negative responses (such as ‘record does not exist’) may be cached.
Viewing and editing the SOA record
In most cases you don’t need to manually create the SOA record, as this happens automatically as soon as you add a domain to your hosting account or DNS zone. If you still want to check or adjust the values, you can do so via your host’s DNS management.
Log in to your DNS management
Go to your domain’s control panel, for example Plesk, and open the DNS settings section.
Find the SOA record
This is usually at the top of the list of DNS records, separate from A and MX records.
Check the values
Check whether the primary nameserver is correct and whether the hostmaster email address is still up to date.
Only adjust if necessary
Only change refresh, retry and expire values if you know the effect, as they determine how quickly changes propagate.
Save and check propagation
After saving it may take a while before the change is visible everywhere, depending on the configured TTL values.
If you manage multiple domains, you’ll find these settings alongside your other domain settings under domain names in your hosting account.
Common problems with SOA
Problems with the SOA record are rare, but can have annoying consequences:
- Serial number not increased: secondary nameservers keep showing old data, causing your website or email to not work correctly everywhere.
- Incorrect primary nameserver: if this doesn’t match the actual nameserver, other servers can’t fetch the zone correctly.
- Too short expire time: during temporary outages, secondary servers may already consider the zone expired before the problem is resolved.
- Outdated hostmaster email address: this causes technical notifications about the zone to miss the right person.
These kinds of problems often surface when moving a domain to a different host. Therefore, after switching to a different host, always check whether the DNS zone, including the SOA record, has been correctly taken over. You can prevent this by waiting a bit with canceling your old hosting until everything is confirmed to work well, including for your business email.
Frequently asked questions
Do I need to create an SOA record myself?
No, this happens automatically as soon as you add a domain to a hosting account or DNS zone. You can at most adjust it.
What happens if the serial number is incorrect?
Secondary nameservers won’t synchronize, so changes in your DNS zone won’t become visible everywhere.
Can an incorrect SOA record take my website offline?
Only in exceptional cases, for example if secondary nameservers consider the zone expired due to a too short expire time.
Where do I find the SOA record in Plesk?
Via the DNS settings section of your domain, at the top of the list of other DNS records.
Conclusion
The SOA record is invisible to most visitors of your website, but essential for a properly functioning DNS zone. As long as the serial number is up to date and the primary nameserver is correct, you’ll rarely need to look at it. If you’re unsure about your DNS settings, check them via your control panel or contact us via our knowledge base.