We've got a DNS cluster with AWS Route53 providing the service (via special plugin). As such, there's some delay between when cluster returns that the record has been updated and the actual update, and that might take up to 60 seconds according to AWS docs.
We're running autossl for wildcard domains now and they only support DNS DCV, as such, autossl updates the record and then almost immediately asks letsencrypt to check it, and of course, gets the old record because not enough time has passed.
I've opened a ticket, #93454103 , but they've provided useless response suggesting submitting a feature request.
So anyone deciding to run a dns cluster with dns dcv, beware of this pitfall.
We're running autossl for wildcard domains now and they only support DNS DCV, as such, autossl updates the record and then almost immediately asks letsencrypt to check it, and of course, gets the old record because not enough time has passed.
I've opened a ticket, #93454103 , but they've provided useless response suggesting submitting a feature request.
So anyone deciding to run a dns cluster with dns dcv, beware of this pitfall.