Import DNS records from another provider

Importing a DNS zone can save time when moving several records. The import still needs a record-by-record review because providers differ in supported types and in features such as proxying, address flattening and signing.

01 Prepare the source and destination

Export a BIND-format zone file from the current provider when available. Keep an untouched copy. List any features that are not ordinary DNS records, including website redirects, email forwarding, CDN proxy settings or health-based routing. Those features need their own configuration after a move.

Create the destination zone in your DNS Manager and confirm its package permits import and the required record types. If your source domain is already live, prepare this destination before changing nameservers. Existing DNSSEC needs a coordinated registrar DS transition.

02 Import and review

  1. Open the destination domain and select Bulk & setup.
  2. Choose Import DNS or the zone-file import option displayed in your view.
  3. Upload the exported file in a format the dialog accepts. Do not rename an arbitrary spreadsheet to a zone-file extension.
  4. Run the parse or preview step. Correct any invalid names, values or unsupported records the manager reports.
  5. Review the proposed additions, changes and removals. Confirm the root domain, www, MX targets, all mail authentication records and service verification entries.
  6. Confirm the reviewed import and wait for the resulting change to finish.

Can I import provider-managed DNSSEC and system records?

The destination provider manages its own SOA, authoritative nameservers and signing material. Copying an old provider's SOA or DNSSEC records does not recreate its service. Likewise, an exported Cloudflare address may not reproduce the proxy, and an AWS alias can require a different supported record arrangement. Use the destination service's current instructions for these cases.

03 Finish the move

Check the destination's answers before changing delegation, then set the assigned nameservers at the registrar. Keep the old provider available while earlier cached answers expire. Test website access, HTTPS, inbound and outbound email, and important subdomains. If a preview unexpectedly proposes widespread deletion, cancel it and review the import mode instead of continuing. An import failure should be investigated in History & requests before another full import is submitted.

  • 0 Users Found This Useful
  • domains-dns, domain-nexus
Was this answer helpful?

Related Articles

Back up and restore DNS records

A DNS backup records the zone's entries so you can review or restore a previous configuration....

Use bulk DNS changes across one or several zones

Bulk management is useful when several records need the same new address or TTL. It also...

Add a domain registered elsewhere to your DNS Manager

You can manage DNS for a domain registered with another company when your Nabtech service...

Read a DMARC aggregate report in DNS Manager

The Premium DNS Plus report reader helps you inspect a DMARC aggregate report received from an...

Enable DNSSEC and complete the DS-record setup

DNSSEC lets validating resolvers check signed DNS data against a chain of trust. It needs both...