Cloud platformDNS hostingCapabilities verified
Selectel DNS Hosting
Migrate DNS zones to or from Selectel DNS Hosting: what's supported, what access you need, and what changes for each destination.
See how a domain's records would land at Selectel. Free and read-only.
Access we need
- Credentials
- Service user (username + password) with a project-scoped IAM token
- Permissions
- Create a service user with the member role scoped to only the project that holds your zones. The reader role on that project is enough for read-only exports.
What Selectel 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
- ALIAS
- DNAME
- HTTPS
- SVCB
- SSHFP
Good to know
- Only DNS Hosting (actual) zones are supported. Zones still on DNS Hosting (legacy, API v1) must be moved to the actual version in the control panel first.
- Zones belong to a project; this connection only sees the project it signs in to.
- Apex NS and SOA records are created and managed by Selectel and can't be changed.
- A CNAME can't be placed at the zone apex; use ALIAS instead.
- Each record set can hold at most 100 values.
- Records you disabled in Selectel are left untouched and aren't imported.
- Selectel doesn't publish API rate limits; requests are retried with backoff when throttled.