GoDaddy DNS NetBird
Migrate DNS from GoDaddy to NetBird.
3 record types move as they are. 1 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
MX, TXT, NS, SRV, CAA aren't available
A typical GoDaddy zone at NetBird
Example records for example.com. Open any flagged row to read why it changed.
GoDaddy NetBird
- ExactA@
192.0.2.50
- 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.
- UnsupportedSRV_sip._tls
Not migrated
NetBird doesn't support SRV records through its API.
- ExactCNAMEftp
example.com.
- ExactCNAMEwww
example.com.
| Status | Type | Name | At NetBird | TTL | Details |
|---|---|---|---|---|---|
| Exact | A | @ |
| 10m | |
| Unsupported | MX | @ | Not migrated | — | |
| Unsupported | TXT | @ | Not migrated | — | |
| Unsupported | CAA | @ | Not migrated | — | |
| Unsupported | TXT | _dmarc | Not migrated | — | |
| Unsupported | SRV | _sip._tls | Not migrated | — | |
| Exact | CNAME | ftp |
| 1h | |
| Exact | CNAME | www |
| 1h |
How the move works
- 1
Connect GoDaddy
Connect GoDaddy with read-only access (Production API key + secret).
- 2
Connect NetBird
Connect NetBird (Personal access token (Authorization: Token) + optional self-hosted management URL). Write access is only used when you apply.
- 3
Review the preview
Check every record marked Review or Unsupported. Each one explains what changes and why.
- 4
Apply to NetBird
We snapshot the NetBird zone, write in batches, and leave GoDaddy untouched.
- 5
Verify
We query NetBird's own nameservers for every record and compare the answers before you switch.
- 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 GoDaddy
- DS records can't be changed through GoDaddy's v1 API, so DNSSEC is handled in their dashboard.
- GoDaddy's DNS API is limited to qualifying accounts. If yours isn't one, export the zone file and we'll use that.
- The minimum TTL is 600 seconds.
- Domain forwarding is a GoDaddy web feature, not a DNS record, and isn't migrated.
Access we need: GoDaddy only grants DNS API access to qualifying accounts. Otherwise, export a zone file.
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 GoDaddy 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 GoDaddy?
No. We never write to GoDaddy. 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.
Ready to see your own zone?
Start a free preview