CAA at Host Europe: what the DNS editor can do
The DNS editor in KIS offers the types A, AAAA, CNAME, TXT, MX, NS and SRV, but no CAA type. Host Europe confirms this in its FAQ on the CAA record: currently no CAA record can be set in KIS. It is only possible on systems where you run a name server yourself, such as a root or virtual server.
For certificates from Host Europe you need no CAA record: without CAA any certificate authority may issue. But if one exists because the zone lives at another DNS provider, it has to allow Host Europe’s authority. Host Europe names the value godaddy.com for this, which also covers its partner Starfield Technologies, and points out that the subdomains of the certificate are checked too, above all www.
With cPanel web hosting Host Europe renews certificates automatically through Let’s Encrypt. An existing CAA record there therefore has to allow letsencrypt.org.
How to handle CAA at Host Europe
The way at Host Europe:
- Use the CAA checker to see whether a CAA record exists for the domain at all. If the zone is at Host Europe the result is empty, and any certificate authority may issue.
- If the zone is at another DNS provider and the website uses a Host Europe certificate: add a CAA record with 0 issue "godaddy.com" there, with cPanel web hosting 0 issue "letsencrypt.org".
- If you want to restrict issuance for the domain, host the zone at a DNS provider with CAA support and point the domain’s name servers to it in KIS.
- After every change check that the authority of the current certificate is allowed; the SSL checker shows the issuer.
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 Host Europe 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.