- DigiCert product docs
- DigiCert DNS
- Manage DNS zones
- Secondary DNS zones
Secondary DNS zones
Secondary zones let DigiCert® DNS contain synchronized copies of zones managed at another DNS provider. You continue managing records at the primary provider while DigiCert® DNS retrieves the zone data through zone transfers.
What a secondary zone is
A secondary zone is a copy of a zone obtained from a primary nameserver. The secondary service retrieves updates so it can serve the zone’s records alongside other authoritative nameservers.
For this arrangement to work, both providers must be correctly configured, included in the intended delegation, and able to serve synchronized zone data.
Explore the Secondary zones page
To view secondary zones in your account, go to DNS > Zones and select the Secondary zones tab.
The page displays the following information:
Column | Description |
|---|---|
Zone name | The zone’s domain name. Select it to open the zone |
Records | The record count displayed for the secondary zone |
Inbound IP sets | The inbound IP set assigned to the zone |
Zone status | The zone’s current state, such as Active or Failed |
Last transfer | The date and time associated with the latest transfer |
Transfer status | The state or result of the transfer |
Use Filter to narrow the list. A zone’s actions menu includes Disable zone and Delete zone when available.
Notice
Zone status and transfer status describe different things. An Active zone can display a Failed transfer status, so review both when checking synchronization. A failed transfer does not necessarily mean the zone has stopped answering queries.
Manage a secondary zone
Select a zone name to open it. The zone’s pages provide access to its transferred records and configuration:
Tab | Purpose |
|---|---|
Records | View DNS records received from the primary provider |
Settings | Review zone details, transfer status, inbound IP sets, and SOA values |
Nameservers | Review assigned nameservers and delegation |
Health | Review nameserver consistency, zone transfers, and notification activity |
The Records tab displays each record’s Type, Record name, Values, and TTL. Use the column filters to narrow the list, and use Page Size and the navigation arrows to move through the records.
Secondary-zone records are maintained at the primary DNS provider. Make record changes there, then allow them to transfer to DigiCert® DNS.
The Settings tab displays Created, Last modified, and Resource record count. Under Transfer status, review Last attempt, Next update, Transfer status, and Details to check synchronization with the primary provider.
The Inbound IP sets section identifies the configured transfer sources, notification sources, and TSIG key. Select the edit icon beside Inbound IP sets to change the zone’s assignment. See Inbound IP sets and TSIG keys for configuration guidance.
The SOA (Start of Authority) section displays the primary nameserver, contact email, TTL, serial number, and synchronization timers received from the primary provider. Make changes to these values at the primary provider. See SOA configurations for an explanation of the fields and timers.
To request an update from the primary provider, select Force zone transfer. After the transfer completes, review Transfer status on the Settings tab and check the resulting records.
On the Nameservers tab, compare Assigned nameservers with Delegated nameservers. An Active zone status does not confirm that delegation is complete. See Secondary nameservers and delegation.
Use the Health tab to review delegation, serial-number matching, transfer-source reachability, AXFR service status, and received notifications. Successful transfers and correct delegation are separate checks; verify both before relying on the secondary zone. See DNS zone health.
Create and configure a secondary zone
Before creating the zone, configure the required transfer permissions and notification destinations at your primary DNS provider. Prepare an inbound IP set containing the primary nameserver addresses and any required TSIG configuration.
To create a secondary zone:
Go to DNS > Zones and select Create zone.
Under Zone type, select Secondary zone.
Enter the zone’s FQDN in Zone name.
Select the Inbound IP set for the primary provider.
Optionally, enter a Comment for the audit log.
Select Create.
Review the zone’s transfer status and complete the secondary-service configuration.
The Inbound IP set dropdown also provides Create inbound IP set if you need a new configuration. See Inbound IP sets for instructions.
To disable or delete a zone, open its actions menu on the Secondary zones page, select Disable zone or Delete zone, and confirm the action.
The Configure secondary DNS service dialog provides the information needed to complete setup:
Information | How to use it |
|---|---|
Zone transfer IP addresses | Configure the primary provider to permit transfer requests from these addresses |
Notification IP addresses | Configure the primary provider to send notifications to these destinations |
Nameservers and their addresses | Add the DigiCert® nameservers as NS records at the primary provider and include them in the intended delegation |
Use the addresses displayed in the dialog rather than copying example values from documentation. Copy controls are provided for the transfer and notification address lists.
Verify that the initial transfer succeeds before relying on DigiCert® DNS to answer queries for the zone.
Where records and SOA settings are managed
The primary provider maintains the source zone data. DigiCert® DNS retrieves that data and serves it as a secondary provider.
Provider | Responsibilities |
|---|---|
Primary provider | Maintain DNS records and SOA settings, permit zone transfers, and notify the secondary service of changes |
DigiCert® DNS | Retrieve zone data from the configured primary nameservers, serve the secondary copy, and display transfer information |
Make record and SOA changes at the primary provider. These values are read-only in the secondary service because they originate from the primary zone. Maintaining separate versions would risk inconsistent answers, and later transfers could overwrite local changes.
The SOA section displays transferred authority and timing values, including TTL, Serial, Refresh, Retry, Expire, and Minimum cache. See SOA configurations for their meanings.
The assigned inbound IP set identifies the primary nameservers used for transfers and notifications. See Inbound IP sets and TSIG keys for configuration details.
Delegate the zone to both providers
When both providers will answer public DNS queries, retain the primary provider’s nameservers and add the assigned DigiCert® nameservers.
At the primary provider, update the zone’s NS records to include the intended nameservers from both providers. At the domain registrar, update delegation to include those nameservers as well.
To complete this configuration:
Review the DigiCert® nameservers in Configure secondary DNS service or on the zone’s Nameservers tab.
Add them to the zone’s NS records at the primary provider.
Retain the primary provider’s nameservers if both providers will continue answering queries.
Update the domain’s nameserver settings at its registrar.
Review detected delegation on the Nameservers tab.
For a separately delegated subdomain, update delegation in its parent zone.
Notice
Delegation and synchronization are separate checks. Correct delegation does not prove that a transfer succeeded, and a successful transfer does not prove that DigiCert® nameservers are delegated.
Keep zone data synchronized
Both providers must serve consistent zone data because resolvers may query either provider. If their records differ, users can receive different answers depending on which nameserver responds.
After records change at the primary provider, the secondary checks for updates and retrieves newer zone data. DNS notifications prompt the secondary to check the primary’s SOA serial number; they do not themselves replace the zone’s records.
Review Last attempt, Next update, and Details to understand the latest transfer activity. The SOA synchronization timers also influence how the secondary checks for updates and handles unsuccessful refreshes.
To request a transfer, open the secondary zone and select Force zone transfer. Review the resulting transfer status to confirm the outcome.
To change the primary source configuration:
Open the secondary zone.
Select the edit icon beside Inbound IP sets.
Select the required Inbound IP set.
Select Apply.
Review subsequent transfer results.
Changing the assigned inbound IP set changes the configured primary sources. Record management remains at the primary provider.
Transfer status and troubleshooting
The interface displays the following transfer states:
Status | Meaning |
|---|---|
Not requested | A transfer has not been requested |
Pending | A transfer is awaiting processing |
In progress | A transfer is underway |
Successful | The transfer completed successfully |
Failed | The transfer attempt did not complete successfully; review Details |
If initial setup fails, the zone can display Secondary zone creation failed. The accompanying message identifies the primary source and directs you to check reachability and transfer permissions.
To investigate a failed transfer:
Read the error banner and Transfer status > Details.
Confirm that the assigned inbound IP set contains the intended primary nameserver addresses.
Verify that the primary nameserver is reachable and permits transfers for the zone.
Check the transfer permissions and notification destinations at the primary provider.
If TSIG is used, verify that the key name, algorithm, and shared secret match at both providers.
Correct the issue and select Force zone transfer.
Review the new transfer result.
If the SOA section reports that it cannot retrieve the SOA record, resolve the transfer or connectivity issue before treating setup as complete.
Secondary zones versus AXFR imports
A secondary zone maintains an ongoing synchronization relationship with its primary source. An AXFR import populates a primary zone that you subsequently manage in DigiCert® DNS.
Aspect | Secondary zone | AXFR import into a primary zone |
|---|---|---|
Purpose | Maintain a synchronized copy of another provider’s zone | Populate a primary zone with transferred records |
Record management | At the primary provider | In DigiCert® DNS after import |
Ongoing synchronization | Part of the secondary-service configuration | Not established by the import |
Source configuration | An assigned inbound IP set | The nameserver and optional TSIG key supplied for the import |
Choose a secondary zone when the existing provider will remain the source of record changes. Choose an AXFR import when you want to bring records into a primary zone managed in DigiCert® DNS.
See Primary DNS zones and the record-import instructions for more information.