INWX Google Cloud DNS

Migrate DNS from INWX to Cloud DNS.

14 record types move as they are. 2 things work differently at Cloud DNS, 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
PTR
NAPTR
SSHFP
TLSA
HTTPS
SVCB

Alias records are converted

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

URL, URL301, FRAME aren't available

Cloud DNS can't store URL, URL301, FRAME records through its API. They're marked Unsupported with the reason, never dropped silently.

A typical INWX zone at Cloud DNS

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

INWX Cloud DNS

ExactA@
192.0.2.70
ExactAAAA@
2001:db8::70
ExactMX@
10 mx1.mail.example.net. +1
ExactTXT@
"v=spf1 include:_spf.example.net -all"
ExactCAA@
0 issue "letsencrypt.org"
ExactTXT_dmarc
"v=DMARC1; p=reject; rua=mailto:dmarc@example.com"
ExactSRV_sip._tls
100 1 443 sip.example.net.
ExactCNAMEwww
example.com.

How each record at INWX translates to Google Cloud DNS
Status	Type	Name	At Cloud DNS	TTL
Exact	A	@	192.0.2.70	5m
Exact	AAAA	@	2001:db8::70	5m
Exact	MX	@	10 mx1.mail.example.net. 20 mx2.mail.example.net.	1h
Exact	TXT	@	"v=spf1 include:_spf.example.net -all"	1h
Exact	CAA	@	0 issue "letsencrypt.org"	1h
Exact	TXT	_dmarc	"v=DMARC1; p=reject; rua=mailto:dmarc@example.com"	1h
Exact	SRV	_sip._tls	100 1 443 sip.example.net.	1h
Exact	CNAME	www	example.com.	1h

How the move works

1
Connect INWX
Connect INWX with read-only access (Username + password session login, with optional TOTP 2FA secret).
2
Connect Cloud DNS
Connect Cloud DNS (Service account key (JSON)). 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 Cloud DNS
We snapshot the Cloud DNS zone, write in batches, and leave INWX untouched.
5
Verify
We query Cloud DNS'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 INWX

TTLs must be between 300 seconds and 10 days.
Each record value is a separate API call, and INWX limits login attempts, so large zones apply slowly.
Accounts with 2FA need the TOTP shared secret, which stores both factors together.

Access we need: A sub-account with nameserver view rights for the preview; nameserver edit (and DNSSEC) rights to apply.

Good to know about Cloud DNS

Routing policies (weighted round robin, geolocation, failover) don't carry over to most providers.
Apex CNAMEs are not allowed.

Access we need: roles/dns.reader for the preview, roles/dns.admin to apply.

Questions

Will there be downtime moving from INWX to Cloud DNS?

Not if both providers serve the same answers during the switch. The records are copied to Cloud DNS 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 INWX?

No. We never write to INWX. 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 Cloud DNS and publish its new DS record. The cutover plan walks you through each step.

Ready to see your own zone?

Start a free preview