DNS hostingDNS hostingCapabilities verified
Packetframe
Migrate DNS zones to or from Packetframe: what's supported, what access you need, and what changes for each destination.
See how a domain's records would land at Packetframe. Free and read-only.
Access we need
- Credentials
- Account session token (Authorization: Token)
- Permissions
- The account's session token from the packetframe.com login cookie. It cannot be scoped or made read-only and is rotated only when the password changes.
What Packetframe 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
- 300s
Record types
- A
- AAAA
- CNAME
- MX
- TXT
- NS
- SRV
- PTR
Good to know
- Packetframe has no official API keys; the adapter uses the account session token, which grants full account access.
- Only A, AAAA, CNAME, MX, TXT, SRV, NS and PTR records exist, with a minimum TTL of 300 seconds; apex NS records are fixed to Packetframe.
- SCRIPT records and CDN-proxied records are Packetframe features that other providers cannot reproduce.