Skip to content
betaDNS betaDNS hostingSetup guide checked 2026-09-27

Packetframe

Packetframe access token setup: copy the HttpOnly `token` cookie created by a Packetframe login; Packetframe does not expose scoped integration keys.

On this page

Packetframe access token permissions

Credential type
Account session token
Preview access
The Packetframe account token; it carries the account's full API access.
Apply access
The same full-account token used for preview.
API endpoint
DNSMigrator uses the provider's fixed API endpoint.

Additional access

Packetframe's official API source accepts the token from either its HttpOnly cookie or an Authorization: Token header and exposes no per-token scopes. DNSMigrator's access check calls /user/info but does not make a DNS write.

DNSControl id

creds.json TYPE
{
  "TYPE": "PACKETFRAME"
}

Create credentials

Copy the HttpOnly token cookie created by a Packetframe login; Packetframe does not expose scoped integration keys.

Access you'll grant

Preview

The Packetframe account token; it carries the account's full API access.

Apply

The same full-account token used for preview.

Packetframe's official API source accepts the token from either its HttpOnly cookie or an Authorization: Token header and exposes no per-token scopes. DNSMigrator's access check calls /user/info but does not make a DNS write.

Before you start

  • A Packetframe account with access to the DNS zones.
  • A desktop browser whose developer tools can inspect cookies.

Setup steps

0 of 5 done

  1. Sign in to Packetframe

    Sign in to the Packetframe account that can manage the zones. A successful login sets an HttpOnly cookie named token.

  2. Open the cookie inspector

    Open your browser's developer tools. In Chromium, go to Application → Storage → Cookies → https://packetframe.com; in Firefox, go to Storage → Cookies → https://packetframe.com.

  3. Copy the token value

    Select the cookie named token and copy its complete Value. The cookie is marked HttpOnly, so page scripts cannot read it, but the browser's cookie inspector can.

    Cookie nametoken
  4. Paste the account token

    Paste the copied value into Account token. Treat it like the Packetframe account password: the API uses it for account information, zone listing, zone creation, and record changes.

  5. Rotate the token after use

    When you no longer need the connection, remove it and change the Packetframe account password. Packetframe's official API implementation generates a new account token when the password changes, invalidating the copied value.

Troubleshooting

The token cookie is missing

Sign out and sign back in, then inspect cookies for packetframe.com rather than a different subdomain. Keep the login tab open while copying it.

Packetframe returns an authentication error

Copy the complete cookie Value again. A password change rotates the server token, and a browser login after that uses the replacement value.

A zone is missing

The /dns/zones endpoint only lists zones authorized for that Packetframe user. Have the zone owner add this user, or use the token from the owning account.

Official documentation

Guide checked against the official documentation on .

Credential fields

FieldRequirementWhere to find it
Account tokentokenRequiredThe full Value of the HttpOnly cookie named token for packetframe.com. It is a 64-character server token in the current official implementation.

Capabilities

Create zones
Yes
List zones
Yes
DNSSEC
Not available through this connection
Minimum TTL
300 seconds
Apex CNAME
No
Read only
No

Record types

  • A
  • AAAA
  • CNAME
  • MX
  • TXT
  • NS
  • SRV
  • PTR

Caveats

  • 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.

Troubleshooting

The token cookie is missing
Sign out and sign back in, then inspect cookies for packetframe.com rather than a different subdomain. Keep the login tab open while copying it.
Packetframe returns an authentication error
Copy the complete cookie Value again. A password change rotates the server token, and a browser login after that uses the replacement value.
A zone is missing
The /dns/zones endpoint only lists zones authorized for that Packetframe user. Have the zone owner add this user, or use the token from the owning account.