# PROD Support for RFC8657 CAA constraints for accountURI and validationmethods **URL:** \ **Category:** Feature Requests\ **Created:** [July 21, 2022, 2:08pm UTC](https://community.letsencrypt.org/t/prod-support-for-rfc8657-caa-constraints-for-accounturi-and-validationmethods/181584 "2022-07-21T14:08:47Z")\ **Posts on this page:** 1\ **Showing post:** 19
**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\ **Post date:** [July 23, 2022, 3:13pm UTC](https://community.letsencrypt.org/t/prod-support-for-rfc8657-caa-constraints-for-accounturi-and-validationmethods/181584/19 "2022-07-23T15:13:58Z")
> [@MikeMcQ](#): > > Good question on cached validations. LE should make that clear in [their FAQ about them](https://letsencrypt.org/docs/faq/#i-successfully-renewed-a-certificate-but-validation-didn-t-happen-this-time-how-is-that-possible). I now wonder what happens if even the CAA issue value were changed during the cached period. Would LE check CAA or fully rely on cache? CAA RR are cached MUCH shorter than valide authz (8 hours instead of 30 days). In fact, the lack of maintaining this shorter cache time in certain situations has lead to a quite serious incident: [2020.02.29 CAA Rechecking Bug](https://community.letsencrypt.org/t/2020-02-29-caa-rechecking-bug/114591) --- _[View the full topic](https://community.letsencrypt.org/t/prod-support-for-rfc8657-caa-constraints-for-accounturi-and-validationmethods/181584)._