This looks very similar to an issue we ran into a few weeks ago -- the solution was to update our nameserver implementation to be more in-spec.
https://community.letsencrypt.org/t/potential-networking-client-changes-on-dns-challenges/207967
This looks very similar to an issue we ran into a few weeks ago -- the solution was to update our nameserver implementation to be more in-spec.
https://community.letsencrypt.org/t/potential-networking-client-changes-on-dns-challenges/207967