Skip to content

Your account

dinio me works on your own user. It finds you by the email stored in the profile, so set it once:

Terminal window
dinio profile set default --email me@example.com
Command
me show [--email E] Your account: email, uuid, role, whether it is suspended, whether a personal key is set.
me key create [--email E] Issue a new personal key. The current one stops working immediately. Asks for confirmation.
me key revoke [--email E] Revoke your personal key. Asks for confirmation.

All three need a personal key. --email overrides the profile’s email for one call.

me key create prints the new key once — Dinio keeps only a hash of it. If the old key came from the profile, the new one is saved there too, and the CLI keeps working. If it came from --api-key or DINIO_API_KEY, replace it there yourself.

Terminal window
dinio me key create --yes -o json | jq -r .api_key

After me key revoke, the CLI has no working key: issue a new one in the Dinio web app and store it with dinio profile set-key.

Each of Dinio’s services has its own package: auth for DNS hosting, filter for DNS filtering. Until you choose one for a service, nothing can be added in it. See Packages and usage.

Terminal window
dinio plan list
dinio plan choose auth pro --period yearly
dinio usage
Command
plan list [--line auth|filter] The packages side by side: price per month and per year, and every limit. Needs no API key.
plan choose LINE CODE [--period monthly|yearly] Choose a package by its code, as plan list shows it. A paid package needs --period; a free one takes none.
usage Per service: your package, and for each limit what you use, what is left, and the level (ok, warn from 80 %, limit, over).
auth: Pro (auth-pro@v1, active, billed yearly)
USED LIMIT FREE LEVEL
zones 17 20 3 warn
free subdomains 1 3 2 ok
health checks 12 50 38 ok
shortest health-check interval - 30s - -
zone statistics, days back - 30 - -
zones warn: Business allows unlimited (`dinio plan choose auth business`)

A paid package starts as a trial. Moving to a smaller package is refused while you use more than it allows: the CLI lists what is over, and nothing changes.

When a command is refused by a limit, the CLI says which limit and whose package it is — for anything in a zone, the zone Owner’s. A create that brings a limit to 80 % or more succeeds and prints a warning on stderr, pointing at dinio usage and dinio plan list.