CAA at Mittwald: what the DNS editor can do
In the mStudio API (version 2) CAA has been one of the record sets of a DNS zone since January 2025. A record consists of flags (a number from 0 to 255), tag (issue, issuewild or iodef) and value (the certificate authority’s domain name), plus a TTL between 60 and 86400 seconds or the automatic setting.
What is documented is the route through the API. The FAQ on the DNS editor names the types A, AAAA, CNAME, MX, TXT, SRV and NS; whether the DNS section of your project offers CAA is visible there in the list of record types.
SSL certificates are ordered free of charge in mStudio through Let’s Encrypt; they run for 90 days and renew automatically. A CAA record for a domain at Mittwald therefore has to allow letsencrypt.org. If the zone lives at another DNS provider such as Cloudflare, the same applies to the CAA record there.
How to create the CAA record at Mittwald
The way at Mittwald:
- In mStudio open the DNS settings of the domain. Mittwald does not document a click path for it; what your project shows is what counts.
- If the DNS section offers the CAA type, create a record for the apex domain: flags 0, tag issue, value letsencrypt.org. Otherwise set the same record through the mStudio API as the caa record set of the DNS zone.
- Add a separate record for every further certificate authority that should issue for the domain.
- Use the CAA checker to verify that the record is publicly visible and Let’s Encrypt remains allowed.
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 Mittwald 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.