Skip to content
dnsmigrator

Namecheap BasicDNS NetBird

Migrate DNS from Namecheap to NetBird.

3 record types move as they are. 2 things work differently at NetBird, and the preview shows exactly which of your records they affect.

Free preview. Read-only. Nothing changes until you apply.

What works differently

Generated from the same provider capability data the migration engine uses.

Moves as-is

  • A
  • AAAA
  • CNAME

Alias records are converted

Namecheap alias records become CNAMEs below the apex. At the apex they need static addresses, and the preview shows which ones.

A typical Namecheap zone at NetBird

Example records for example.com. Open any flagged row to read why it changed.

Namecheap NetBird

  • UnsupportedALIAS@

    Not migrated

    @ is an alias to app.example-host.net at the zone apex. NetBird doesn't support apex aliases or CNAMEs.

  • UnsupportedMX@

    Not migrated

    NetBird doesn't support MX records through its API.

  • UnsupportedTXT@

    Not migrated

    NetBird doesn't support TXT records through its API.

  • UnsupportedCAA@

    Not migrated

    NetBird doesn't support CAA records through its API.

  • UnsupportedTXT_dmarc

    Not migrated

    NetBird doesn't support TXT records through its API.

  • ExactCNAMEblog

    example.github.io.

  • UnsupportedURL301go

    Not migrated

    URL301 is a Namecheap redirect feature, not a DNS record. Recreate it as a redirect rule at NetBird.

  • ExactCNAMEwww

    example.com.

How the move works

  1. 1

    Connect Namecheap

    Connect Namecheap with read-only access (API user + API key, with our egress IP allow-listed).

  2. 2

    Connect NetBird

    Connect NetBird (Personal access token (Authorization: Token) + optional self-hosted management URL). Write access is only used when you apply.

  3. 3

    Review the preview

    Check every record marked Review or Unsupported. Each one explains what changes and why.

  4. 4

    Apply to NetBird

    We snapshot the NetBird zone, write in batches, and leave Namecheap untouched.

  5. 5

    Verify

    We query NetBird's own nameservers for every record and compare the answers before you switch.

  6. 6

    Switch nameservers

    Lower TTLs a day or two ahead, remove any DS record if DNSSEC is on, then point the domain at the new nameservers at your registrar.

Good to know about Namecheap

  • Namecheap's API replaces the whole host list on every write, so we always read, merge and then write.
  • SRV records can't be managed through the API.
  • URL redirect records are Namecheap-specific and aren't real DNS records.

Access we need: API access enabled under Profile → Tools, with our static IP added to the allow-list.

Good to know about NetBird

  • NetBird custom zones are private DNS served only to peers in the zone's distribution groups; creating a zone needs at least one distribution group ID.
  • Only A, AAAA and CNAME records are supported.
  • Self-hosted management servers are often on private networks: we only connect if the API is exposed publicly over HTTPS, because private and internal addresses are refused by design.

Access we need: A service user whose role has DNS read permission for the preview and DNS create/update/delete to apply (Admin or Owner).

Questions

Will there be downtime moving from Namecheap to NetBird?

Not if both providers serve the same answers during the switch. The records are copied to NetBird and verified before you change nameservers, so resolvers get the same answer from either side while caches expire.

Do I have to delete anything at Namecheap?

No. We never write to Namecheap. Keep the old zone for a week after cutover so you can switch back instantly if anything looks wrong.

What about DNSSEC?

If DNSSEC is on, remove the DS record at your registrar and wait for it to expire before switching nameservers. Then enable DNSSEC at NetBird and publish its new DS record. The cutover plan walks you through each step.

Related migrations

Ready to see your own zone?

Start a free preview