Zones
ZONE is always a zone name (example.com) or its uuid.
dinio zone listdinio zone show example.comdinio zone create example.comdinio zone key create example.comdinio zone delete example.com| Command | |
|---|---|
zone list |
Zones the key can see, sorted by name, with their status (active or suspended). |
zone show ZONE |
One zone: name, uuid, status, whether it has a key, timestamps. |
zone create NAME |
Create a zone. You become its Owner; the apex SOA and NS are added for you. Needs a personal key. A name below a free domain is a lease. |
zone delete ZONE |
Delete a zone with everything in it: records, health checks, geo bans, redirects and certificates. Asks for confirmation. |
zone key create ZONE |
Issue a new zone key. A previous zone key stops working immediately. Asks for confirmation. |
zone key revoke ZONE |
Revoke the zone key. Asks for confirmation. |
Writing a zone to a file and importing records are on Zone files.
Zone keys
Section titled “Zone keys”zone key create prints the new key once — Dinio keeps only a hash of it — so store it
right away:
dinio zone key create example.com --yes -o json | jq -r .api_keyUse the zone key for automation that only touches this zone; see API keys.
If the CLI itself is using that zone’s key, the new key replaces the one in use. When the old
key came from the profile, the CLI saves the new one there and keeps working; when it came
from --api-key or DINIO_API_KEY, replace it there yourself. After zone key revoke with
its own key, store a new one with dinio profile set-key.