DNS hostingDNS hostingCapabilities verified
netcup
Migrate DNS zones to or from netcup: what's supported, what access you need, and what changes for each destination.
See how a domain's records would land at netcup. Free and read-only.
Access we need
- Credentials
- Customer number + API key + API password (CCP API session)
- Permissions
- A CCP API key and API password. netcup keys cannot be limited to read-only or to single domains, so the same key is used for preview and apply.
What netcup supports
The same data the translation engine uses when it plans a migration.
- Create zones through the API
- List zones through the API
- Turn on DNSSEC through the API
- Apex CNAME (flattening)
- Apex ALIAS record
- Aliases to cloud resources
- CDN proxy on records
- Routing policies
- Minimum TTL
- 86400s
Record types
- A
- AAAA
- CNAME
- MX
- TXT
- SRV
- CAA
- TLSA
Good to know
- netcup has no per-record TTL: every record uses the zone TTL (86400 seconds by default), so source TTLs are not kept.
- Domains can only be listed for reseller accounts; everyone else enters the zone name, and NS records are not managed.
- TXT values with quotes or backslashes and CAA values with semicolons are altered or rejected by the API.