DNSSEC at Hetzner: the status
Hetzner states on the product page of its DNS service that the Hetzner Console currently does not include support for DNSSEC. A zone on the Hetzner name servers is therefore unsigned, and there is no switch to change that.
The Console has the DS record type with the fields Tag/ID, Encryption, Hash type and Hash. According to the documentation Hetzner only supports DS records, no DNSKEY records. A DS record inside a zone points to a signed child zone at another provider; it does not sign your own zone. On its own it does not establish validation either: as long as the zone it sits in is unsigned, the DS record carries no signature, the chain of trust breaks above it, and validating resolvers treat the child zone like an unsigned one.
For konsoleH (web hosting) and domain registration in Robot the Hetzner documentation says nothing about DNSSEC. Whether key data can be published at the registry for a domain registered there with external name servers can therefore only be answered by support.
How to handle DNSSEC at Hetzner
The way through the Hetzner control panel:
- Use the DNSSEC checker to see whether the domain has a DS record. For a zone on the Hetzner name servers there should be none.
- If a DS record is left over from a previous provider, it has to be removed at the registrar: it does not match an unsigned zone, and validating resolvers then stop answering for the domain.
- If DNSSEC is mandatory, for example because a client requires it, host the zone at a DNS provider that signs and publish its DS data at the domain’s registrar.
- The DS record in the Hetzner Console is only meant for the special case of a subdomain living as its own signed zone at another provider.
The order when changing providers
DNSSEC does not forgive a wrong order. The DS record at the registry points to the key of the zone; if the two do not match, validating resolvers answer with SERVFAIL and the domain is unreachable for many users, website and mail included.
- Before changing name servers switch off DNSSEC or remove the DS record.
- Wait until the TTL of the DS record has expired, usually one to two days.
- Only then change the name servers and sign again at the new provider.
Verify and keep an eye on it
The DNSSEC checker below follows the chain from the registry to the zone: DS record, DNSKEY and signatures. You see right away whether DNSSEC is fully set up for a domain at Hetzner or whether an orphaned DS record puts the domain at risk. DomainWarn keeps checking this afterwards and alerts you when the chain breaks or signatures expire.