Check and manage DNSSEC

DNSSEC signs your zone’s responses cryptographically. Resolvers can use those signatures to check that a response really comes from your zone and was not altered along the way.

Where the status lives

Domains → your domain → DNS → DNSSEC, direct address: dash.regfish.de/my/domains/<tld>/<sld>/dnssec

Automatic management

If the domain runs on regfish nameservers, regfish handles the signing, the submission to the registry, and the ongoing checks itself. The page then shows Automatic management by regfish — Active and, below it:

Field	Meaning
Operating mode	Which nameservers serve the zone
Active keys	How many keys are on file with the registry
Last verified	When regfish last checked the chain
Last applied	When a change last went to the registry
Signed since	How long the zone has been signed

Verify status starts a check by hand. That is worth doing after a nameserver change, or when an external test reports that the chain is broken.

Two expandable sections go deeper: Technical DNSSEC details shows the keys on file with the registry, Recent DNSSEC activity the history of changes.

Caution

DNSSEC does not forgive half-finished migrations. Switching nameservers without cleanly ending DNSSEC first makes the domain unreachable for every validating resolver — and no quick record fix will repair that, because the registry data has to catch up. Disable DNSSEC first, wait, then switch the nameservers.

The same thing through the API

Task	Endpoint
Read the status	GET /dns/{domain}/dnssec
Set the configuration	PUT /dns/{domain}/dnssec
Verify the status	POST /dns/{domain}/dnssec/verify
Cancel a running transition	POST /dns/{domain}/dnssec/cancel
List jobs	GET /dns/{domain}/dnssec/jobs

Important for scripts: DNSSEC changes run asynchronously. That is why the API distinguishes between the target (desired_state) and the state actually observed (live_state) — the two are allowed to differ for a while. To wait for completion, query the job list instead of polling the status in a tight loop.