ClouDNS NetBird

Migrate DNS from ClouDNS to NetBird.

3 record types move as they are. 3 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

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

Routing policies are flattened

NetBird has no routing policies. Weighted, geo and latency sets collapse into one set of answers, and failover keeps only the primary. Each one is flagged for review.

MX, TXT, NS, SRV, CAA, PTR, DNAME, TLSA, SSHFP, DS, NAPTR, CLOUDNS_WR aren't available

NetBird can't store MX, TXT, NS, SRV, CAA, PTR, DNAME, TLSA, SSHFP, DS, NAPTR, CLOUDNS_WR records through its API. They're marked Unsupported with the reason, never dropped silently.

A typical ClouDNS zone at NetBird

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

ClouDNS NetBird

ExactA@
192.0.2.70
ExactAAAA@
2001:db8::70
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.
ExactCNAMEwww
example.com.

How each record at ClouDNS translates to NetBird
Status	Type	Name	At NetBird	TTL
Exact	A	@	192.0.2.70	5m
Exact	AAAA	@	2001:db8::70	5m
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	www	example.com.	1h

How the move works

1
Connect ClouDNS
Connect ClouDNS with read-only access (API user auth ID (or sub-user ID/name) + password).
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 ClouDNS 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 ClouDNS

TTLs must be one of ClouDNS's fixed values (60, 300, 900, 1800, 3600, 21600 … 2592000); other TTLs are rounded up.
Web redirects (CLOUDNS_WR) are ClouDNS-only and are written as plain 301 redirects without frame options.
The API is rate limited to about 20 requests per second per IP, so large zones apply record by record and take a while.

Access we need: A read-only API sub-user with the zones delegated is enough for the preview; applying needs a read-and-write sub-user or a main API user.

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 ClouDNS 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 ClouDNS?

No. We never write to ClouDNS. 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