"CAA Record Prevents Issuance": How to Fix Certificate Renewal Errors
The short answer (what's causing it)
The CA checked your CAA records (on the hostname or a parent) and found it isn't listed — often after switching CA or because a CNAME target has its own CAA.
Step-by-step fix
- Query CAA for the exact hostname and each parent.
- Add an
issueentry for your current CA. - Check CNAME targets' CAA.
- Retry issuance.
Record examples (replace example.co.uk with your domain)
dig +short CAA www.example.co.uk
dig +short CAA example.co.uk
example.co.uk. CAA 0 issue "letsencrypt.org"
Examples are illustrative templates, not values for your domain. Test changes at
p=none/ staging first.
Check yours free in seconds
Run the free 20-check SuperTool on your domain: no signup, no install, public DNS only. Relevant checks: CAA, DNSSEC.
Scan my domain free (20-check SuperTool) → £19 NIS2, DORA & ISO 27001 Supplier Posture Bulk Auditor Pack → £5 Website Launch Special Quick-Fix Pack →One-off download via PayPal guest checkout, no subscription. Packs contain DNS/config templates and scripts you run yourself.
Frequently Asked Questions
What's the CA's identifier?
Use the domain the CA documents (e.g. letsencrypt.org, digicert.com).
Can DNS errors cause this?
Yes — a SERVFAIL on CAA lookup can block issuance.
Related FaultyPacket guides & tools
Authorised use: only scan domains you own or are authorised to inspect. Results are point-in-time public DNS observations.