CAA at Hetzner: what the DNS editor can do
The Hetzner Console lists CAA among its record types. A record there consists of Name (@ for the apex domain), Criticality (the flag, always 0 in the documentation’s examples), Tag, Value and TTL.
The Hetzner documentation shows examples for the tags issue, issuewild and iodef, and also for issuemail (S/MIME certificates), issuevmc (mark certificates for BIMI) as well as contactemail and contactphone. On iodef Hetzner notes that the notification only works if the certificate authority supports it.
For DNS administration in konsoleH the documentation only names A, AAAA, MX and CNAME. If the zone of a web hosting package lives there, CAA is therefore not documented. If you use a free certificate in konsoleH, read in the SSL checker which authority issued it before adding a CAA record.
How to create the CAA record at Hetzner
The way at Hetzner:
- In the Hetzner Console (console.hetzner.com) open the project, choose “DNS” in the menu and open the zone of the domain.
- For the new record choose “CAA” as the type and enter @ as the name for the apex domain.
- Enter Criticality 0, Tag issue and the certificate authority’s domain as the Value, for example letsencrypt.org.
- Add it with “Add”; for wildcard certificates create a second record with the issuewild tag if needed.
Click path at Hetzner
Path in the Hetzner Console (console.hetzner.com).
Structure of the CAA record
A CAA record defines which certificate authorities may issue certificates for the domain. It consists of flag, tag and value: issue allows an authority to issue for the domain, wildcard certificates included, as long as there is no issuewild record. issuewild applies to wildcard certificates only and takes precedence over issue there. iodef names an address for reports. Without a CAA record any authority may issue; as soon as one exists, only those named. So first collect every authority the domain actually uses, including those of the CDN, shop system or mail provider.
The example allows Let’s Encrypt for regular and wildcard certificates. To forbid wildcard certificates altogether, add the line 0 issuewild ";"; to reserve them for another authority, name that one in the issuewild record.
example.com. CAA 0 issue "letsencrypt.org"
example.com. CAA 0 iodef "mailto:security@example.com"Verify and keep an eye on it
The CAA checker below reads the records the way a certificate authority sees them, including inheritance from the apex domain. You see right away whether the record has arrived at Hetzner and whether the authority of the current certificate remains allowed. DomainWarn keeps checking CAA and certificate afterwards and alerts you when a renewal would fail because of CAA.