Skip to content
DNSmigrator

DNSMigrator docs

Introduction

Learn DNS migration from planning through verified cutover. Preview every record, handle DNSSEC, migrate DNS safely, and keep a tested rollback path.

3 min read

On this page

DNS migration moves a zone’s records and authoritative service from one provider to another, while DNSMigrator keeps every provider write behind a record-by-record preview and explicit confirmation. You can inspect a migration for free, then download a translated zone file, apply to a connected destination, or manage the zone after the move.

QuickstartConnect a source and destination, preview the plan, apply it, verify it, and cut over.Migration workflowUnderstand every migration stage and the guarantee each stage makes.Managed zonesEdit records, lint drafts, preview changes, push, monitor drift, and restore backups.Connecting providersCreate least-privilege connections and check their read or write access.BIND zone filesUse a zone file as a source, validate one, or export a translated destination file.Coming from DNSControlMap creds.json, dnsconfig.js, preview, push, and get-zones to the app.CLICheck public DNS and translate, lint, diff, or export zone files without credentials.DNSControl parityLook up every supported command, function, record type, modifier, and known deviation.Free web toolsUse the checker, translator, validator, diff, propagation, and DNSSEC tools without signing in.

What is DNS migration?#

A DNS migration changes where a zone is hosted without transferring the domain registration itself. A DNS migration tool should inventory the source, translate provider-specific behavior, compare the destination, verify its answers, and keep record apply separate from the nameserver cutover.

If you are moving one live zone, follow the first-migration quickstart. It takes you through the same order enforced by the app: connect, preview, apply, verify, then change delegation. Read DNSSEC transitions before changing nameservers for a signed zone.

If you already use DNSControl, start with Coming from DNSControl, then keep the parity reference nearby while importing dnsconfig.js. If you only have a BIND export, the zone translator and zone file validator run in your browser.

Popular providers: Cloudflare · Amazon Route 53 · Azure DNS · Google Cloud DNS · GoDaddy · Namecheap

How the docs are organized#

  • Getting started explains the product model, your first migration, and DNSControl terminology.
  • Migrations follows a zone from source discovery through translation, planning, apply, authoritative verification, rollback, and nameserver cutover.
  • Zone management covers the saved draft, record editor, builders, ignore rules, multi-provider DNS, drift checks, backups, and config-as-code import and export.
  • Providers lists current DNS and registrar support. Each provider page includes capabilities and, when available, a credential setup guide tied to the fields in the connect form.
  • Workspace covers people, roles, notifications, reports, billing, and the activity trail.
  • CLI and tools documents credential-free local commands and public web utilities.
  • Reference contains the DNSControl parity matrix, glossary, and FAQ.

DNS migration questions#

What is DNS migration?
DNS migration moves authoritative DNS records and service from one provider to another. It is separate from transferring the domain registration, which remains with the registrar unless you run a different domain-transfer process.
Is DNSMigrator a free DNS migration tool?
Creating and reviewing a record-by-record migration preview is free, as are the credential-free CLI and web tools. Applying records to a connected provider or using cutover automation can require a one-time entitlement.
When does a DNS migration go live?
Applying records prepares the destination but does not send normal traffic there. Traffic moves after you change the domain’s nameservers and recursive resolvers replace their cached delegation.
Do I need provider credentials to migrate DNS?
Use provider connections for the most complete API-based preview and for an in-app apply. If you cannot connect the source, you can validate and translate a BIND zone file without sharing provider credentials.