CDN and edgeDNS hostingCapabilities verified
Gcore DNS
Migrate DNS zones to or from Gcore DNS: what's supported, what access you need, and what changes for each destination.
See how a domain's records would land at Gcore. Free and read-only.
Access we need
- Credentials
- Permanent API token
- Permissions
- A permanent API token whose role can manage DNS. Gcore tokens can't be limited to read-only DNS.
What Gcore 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
- 60s
Record types
- A
- AAAA
- CNAME
- MX
- TXT
- NS
- SRV
- CAA
- HTTPS
Good to know
- Record sets that use GeoDNS or balancing filters, failover health checks, answer metadata or disabled answers are flagged and never changed by us.
- SRV records can't have an empty target, and PTR records only work in reverse-DNS zones.
- ALIAS records are written as CNAMEs, which Gcore flattens at the zone apex.