CAA at ALL-INKL: what the DNS editor can do
ALL-INKL creates the CAA record in KAS in the DNS settings, with the type CAA and a single DATA field for the content. The whole line of flag, tag and value goes there, for example 0 issue "letsencrypt.org". At ALL-INKL the quotation marks around the certificate authority’s domain are part of it.
Most websites at ALL-INKL use the free Let’s Encrypt certificate that is enabled in KAS in the SSL protection of the domain. A CAA record therefore has to allow letsencrypt.org, otherwise the next renewal fails. The ALL-INKL tutorial names sectigo.com as a second example; several CAA records side by side are possible.
ALL-INKL points out that the record is active after about three to four hours. If the domain’s record should also apply to a subdomain such as www, ALL-INKL advises setting a CNAME from the subdomain to the domain. Under the CAA standard the certificate authority continues the search at the parent domain anyway when a name has no CAA record of its own; the CAA checker shows whether the record is read for www.
How to create the CAA record at ALL-INKL
The way at ALL-INKL:
- In KAS (technical administration) open “Tools” and then “DNS settings” and edit the domain.
- Choose to create a new DNS record and set the type to “CAA”; the name field stays empty for the apex domain.
- Enter the whole line into the DATA field: 0 issue "letsencrypt.org".
- Save, and create a separate record for every further certificate authority.
Click path at ALL-INKL
Official guide from ALL-INKL: DNS Tools: How to add a CAA-record(opens in a new tab)
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 ALL-INKL 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.