# CAA record preventing issuance since Friday 26th but nothing has obviously changed **URL:** \ **Category:** Help\ **Created:** [May 30, 2023, 3:49pm UTC](https://community.letsencrypt.org/t/caa-record-preventing-issuance-since-friday-26th-but-nothing-has-obviously-changed/199238 "2023-05-30T15:49:29Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\ **Post date:** [May 30, 2023, 4:02pm UTC](https://community.letsencrypt.org/t/caa-record-preventing-issuance-since-friday-26th-but-nothing-has-obviously-changed/199238/2 "2023-05-30T16:02:46Z")
Let's Encrypt made a recent change that I think they are reversing. But, the reason for the failure is you are using the flag value of 128 which means critical. You have this set for `iodef` but Let's Encrypt does not support iodef. For now, setting the flag to 0 for iodef should allow cert issuance. [https://unboundtest.com/m/CAA/siren.io/DIEWR5A7](https://unboundtest.com/m/CAA/siren.io/DIEWR5A7) EDIT: Below is post with more detail > [@Renewal failures - "CAA prevents issuance" with unchanged CAA](https://community.letsencrypt.org/t/renewal-failures-caa-prevents-issuance-with-unchanged-caa/199053/5): > > Y… --- _[View the full topic](https://community.letsencrypt.org/t/caa-record-preventing-issuance-since-friday-26th-but-nothing-has-obviously-changed/199238)._