- DigiCert product docs
- DigiCert DNS
- Manage DNS records
- Import DNS records
Import DNS records
Import DNS records to populate a new primary zone or add records to an existing primary zone. You can upload a zone file or enter BIND text. During zone creation, you can also copy records from an existing zone or retrieve them through a zone transfer.
Import options
The available import methods depend on whether you are creating a zone or adding records to an existing zone.
Where you import | Method | Description |
|---|---|---|
Existing zone’s Records tab | Upload zone file | Add records from a zone file |
Enter BIND text | Add records by pasting their BIND format definitions | |
Create zone panel | Zone file | Populate the new zone by uploading a zone file or entering BIND text |
Existing zone | Copy DNS records from a selected zone, without copying its zone settings | |
Zone transfer (AXFR) | Retrieve records from a nameserver | |
Do not import | Create the zone without importing records |
Importing from an existing zone’s Records tab adds records without replacing existing records. To change an existing record, use its edit action.
For secondary zones, manage records at the primary DNS provider and allow zone transfers to synchronize the changes. See Secondary DNS zones.
Before importing records
Review the destination zone and the records you intend to import. Check that names, record types, values, and TTLs are appropriate for the zone.
Record types determine the information each entry contains. See A records, AAAA records, CAA records, CNAME records, MX records, and TXT records for type-specific requirements.
The BIND text import form lists these record types as unsupported: DLV, DNSKEY, DS, NSEC, NSEC3, NSEC3PARAM, RRSIG.
Configure DNSSEC through the zone’s DNSSEC settings. See DNSSEC.
Review system-managed records separately. Importing records does not replace the configuration used to manage nameserver sets or SOA settings. See Nameserver sets and SOA configurations.
Check for conflicts with records already in the destination zone. If an imported record creates an invalid DNS conflict, the entire import fails and no records are added.
Import records as BIND text
To paste record definitions into an existing primary zone:
Go to DNS > Zones and select Primary zones.
Open the destination zone and select the Records tab.
Select Import records.
Select Enter BIND text.
Paste the record definitions into BIND text.
Select Import.
Review the result and any warning details.
The form includes the following record format: name TTL class type data
Component | Description |
|---|---|
Name | The DNS name to which the record belongs |
TTL | How long the record can be cached, in seconds |
Class | The DNS class, usually |
Type | The record type, such as |
Data | The value or values required by that record type |
For example, these definitions add an address record and an alias in the example.com zone:
www.example.com. 300 IN A 192.0.2.10shop.example.com. 300 IN CNAME www.example.com.
In BIND text, a trailing dot identifies a fully qualified DNS name. Names without a trailing dot are relative to the current origin. Using complete names with trailing dots makes the intended names explicit.
Replace the example names and values with those required for your zone.
Upload a zone file
To import a zone file into an existing primary zone:
Go to DNS > Zones and select Primary zones.
Open the destination zone and select the Records tab.
Select Import records.
Select Upload zone file.
Drag the file into the upload area, or select Browse files and choose the file.
Select Import.
Review the result and any warning details.
Review the file’s contents before uploading it, particularly when it was exported from another DNS provider. Check for unsupported record types, references to the previous provider, and records that conflict with the destination zone.
Uploading a zone file adds records without replacing the zone’s existing records.
Import records when creating a primary zone
Use Record import method in the Create zone panel to choose how the new primary zone receives its initial records.
To begin:
Open the Create zone panel from DNS > Zones.
Select Primary zone.
Enter the Zone name.
Review the zone’s Advanced configuration options.
Select a Record import method:
To retrieve records from a nameserver, select Zone transfer (AXFR) and complete its Nameserver and TSIG key fields.
Notice
Ensure the source nameserver permits the transfer. If it requires TSIG authentication, select the corresponding key. See TSIG keys.
An AXFR import during primary zone creation supplies the initial records. It does not establish ongoing synchronization with the source provider. For ongoing synchronization, use a secondary zone. See Secondary DNS zones.
To copy records from another zone, select Existing zone, then select the source in Zone. Only DNS records are imported; zone settings are not included. Review the new zone’s settings separately.
To import from a file or pasted text, select Zone file. Then choose Upload zone file or Enter BIND text and supply the records.
To create the zone without importing records, select Do not import.
Optionally, enter a Comment to provide context for the audit log.
Select Create.
See Primary DNS zones for zone configuration and DNS audit logs for audit comments.
Import results and conflicts
Review the completion message after each import.
Result | Meaning | Next step |
|---|---|---|
Completed successfully | All valid records were added | Review the imported records |
Completed with warnings | Valid records were added, but some records could not be imported | Review the warning details and correct the affected records |
Failed because of an invalid DNS conflict | No records were added | Resolve the conflict and retry the import |
A conflict can arise when an imported record is incompatible with an existing record at the same name. For example, a CNAME cannot coexist with ordinary A, AAAA, MX, or TXT records at that name. See CNAME records.
After an import completes with warnings, review which records were added before preparing another import. Correct the records identified in the warning details rather than assuming the entire import failed.
Review imported records
After a successful import, the confirmation message displays the number of records imported.
On the Records tab, use Grouped view to review records by type, or Table view to review them in a table. Use Search to locate specific names.
Check the imported record names, destination values, and TTLs. For MX records, also check priorities; for hostname-based destinations, confirm that the names point to the intended services.
When importing records as part of a DNS migration, also review the zone’s assigned nameservers and registrar delegation. Importing records does not update the domain’s nameservers at its registrar. See Primary nameservers and delegation.
TTL and DNS caching
A record’s TTL specifies how long its DNS answer can be cached, in seconds. Review TTL values in the import data before adding the records.
Importing records does not clear answers already cached by resolvers. Previously cached data can remain in use until its TTL expires.
When planning a migration, consider lowering relevant TTLs at the current authoritative provider in advance and allowing the previous TTLs to expire before switching service. Lowering a TTL does not shorten the lifetime of answers already cached with the previous value.