- DigiCert product docs
- DigiCert DNS
- Shared DNS settings
- SOA configurations
SOA configurations
A Start of Authority (SOA) record identifies a DNS zone’s primary nameserver, administrative contact, and version number. It also contains timing values used for secondary zone synchronization and negative DNS caching.
DigiCert® DNS lets you manage named SOA configurations and apply them to primary zones.
What an SOA record is
An SOA record contains information about a zone’s authority and synchronization settings. Secondary nameservers use its serial number and timers to determine when to check for updates, retry unsuccessful checks, and stop treating an outdated zone copy as authoritative.
In DigiCert® DNS, an SOA configuration is a reusable collection of these settings. You can apply the same configuration to multiple zones.
The configuration’s Name identifies it within DigiCert® DNS. The Serial identifies the version of an individual zone and appears in that zone’s SOA details.
Explore the SOA page
To view SOA configurations in your account, go to Configuration > Product settings and select the SOA tab.
The page displays the following information:
Column | Description |
|---|---|
Name | The name identifying the SOA configuration |
Primary nameserver | The hostname of the primary nameserver identified in the SOA record |
Contact email | The administrative contact email address for the zone |
TTL | How long the SOA record can be cached, in seconds |
Refresh | How often secondary nameservers check for zone updates, in seconds |
Retry | How long secondary nameservers wait before retrying a failed refresh, in seconds |
Expire | How long a secondary can go without successfully refreshing the zone before its copy expires, in seconds |
Min cache | The value used with the SOA TTL to determine how long negative DNS responses can be cached, in seconds |
Zones | The number of zones using the configuration. Select the count to view the applied zones |
To create an SOA configuration:
Select Create SOA record.
Enter a Name that identifies the configuration.
Review or enter the Primary nameserver hostname.
Review or enter the Contact email.
Enter the TTL, Refresh, Retry, Expire, and Minimum cache values in seconds.
Select Create.
After creating the configuration, apply it from a primary zone’s Settings tab.
To edit a configuration, select its edit icon, update the available fields, and select Update.
To view the zones using a configuration, select its count in the Zones column. The Applied zones panel lists those zones. Select a zone name to open it.
To delete a configuration, select its delete icon when available and confirm the deletion. Deletion cannot be undone.
Default SOA configuration
DigiCert® DNS provides an SOA configuration named Default. You can review its settings on the SOA page and select it when assigning an SOA configuration to a primary zone.
To edit the Default configuration, select its edit icon, update the available fields, and select Update. Its name is read-only.
If a group of zones needs different settings, create a separate SOA configuration and apply it to those zones.
To see which configuration a zone uses, open the zone’s Settings tab and locate SOA (Start of Authority).
Shared SOA configurations
You can apply one SOA configuration to multiple zones that need the same authority and timing settings. For example, a group of zones could share the same contact email and secondary refresh intervals.
Use descriptive configuration names so you can identify their purpose when assigning them to zones.
Before editing a shared configuration, select its Zones count to review where it is used. If only some zones need different settings, create a separate configuration and assign it to those zones.
Apply SOA configurations to primary zones
To apply or change the SOA configuration for a primary zone:
Go to DNS > Zones and select the Primary zones tab.
Open the zone and select its Settings tab.
Select the edit icon beside SOA (Start of Authority).
Select the required configuration from the SOA record menu.
Select Apply.
If you need a new configuration, select Create SOA record from the menu.
The zone’s SOA section displays the assigned configuration, primary nameserver, contact email, serial number, and timing values.
SOA serial numbers
The SOA serial number identifies a version of a zone. Secondary nameservers compare it with the serial number of their local copy to determine whether an update is needed.
A newer serial number indicates that the secondary should retrieve updated zone data. The serial number works with the synchronization timers; it is not a caching duration.
To view a zone’s serial number, open its Settings tab and locate the Serial column in the SOA (Start of Authority) section.
The SOA configuration creation and editing forms contain the reusable authority and timing settings. They do not include a serial-number field.
SOA timers and supported values
Enter SOA timing values in seconds. The creation form displays the following ranges:
Field | Range in seconds | Equivalent duration |
|---|---|---|
TTL | 3,600–2,419,200 | 1 hour–28 days |
Refresh | 3,600–21,600 | 1-6 hours |
Retry | 600–1,800 | 10-30 minutes |
Expire | 86,400–2,419,200 | 1-28 days |
Minimum cache | 60–86,400 | 1 minute-1 day |
Secondary synchronization timers
Refresh, Retry, and Expire govern how secondary nameservers maintain their copies of a zone:
Refresh sets the interval between routine checks for updates.
Retry sets the wait before another attempt after a failed refresh.
Expire limits how long a secondary can continue treating its zone copy as authoritative without a successful refresh.
For example, a refresh value of 3600 represents a one-hour interval. If a refresh fails and the retry value is 600, the secondary waits ten minutes before trying again. If it cannot refresh successfully before the expiry interval elapses, its zone copy expires.
Caching timers
TTL and Minimum cache govern how resolvers cache the SOA record and negative DNS responses:
TTL sets how long the SOA record can remain cached. Other DNS records have their own TTL values.
Minimum cache works with the SOA TTL to determine how long negative responses can remain cached, such as when a name does not exist or the requested record type is absent.
For example, an SOA TTL of 43200 represents twelve hours. If Minimum cache is 300, negative responses can be cached for five minutes because the negative caching TTL is the lower of these two values.