DNS hostingDNS hostingCapabilities verified
RWTH Aachen DNS-Admin
Migrate DNS zones to or from RWTH Aachen DNS-Admin: what's supported, what access you need, and what changes for each destination.
See how a domain's records would land at RWTH. Free and read-only.
Access we need
- Credentials
- DNS-Admin API token (PRIVATE-TOKEN header)
- Permissions
- A DNS-Admin API token with your DNS-Admin rights, optionally restricted to a sub-domain. Tokens are not read-only, so the same token is used for preview and apply.
What RWTH 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
- PTR
- SSHFP
Good to know
- The DNS-Admin API is only reachable from the RWTH network (campus or VPN), so the hosted service cannot connect; use the DNSMigrator CLI from inside the network.
- Changes are staged and published by a zone deploy; RWTH deploys zones in 15-minute cycles, so updates can take that long to appear.
- Zones are assigned by the RWTH IT Center and cannot be created through the API; the SOA record is locked.