As this utility runs, it needs to set a TXT flag in the DNS infrastructure to allow LetsEncrypt to validate the certificate. Up until recently we had a 30 second wait time for this TXT flag to propagate and for the last several years, this had worked out well.
However, in a recent batch of certificates generated, I noticed errors from Dehydrated that the TXT key is invalid and was still showing the old (please delete me) value. It appears that some change(s) in GoDaddy's infrastructure causes some delays that were not seen before.
I will be posting a change to allow users to configure an override of this sleep time via an environment variable.
As this utility runs, it needs to set a TXT flag in the DNS infrastructure to allow LetsEncrypt to validate the certificate. Up until recently we had a 30 second wait time for this TXT flag to propagate and for the last several years, this had worked out well.
However, in a recent batch of certificates generated, I noticed errors from
Dehydratedthat the TXT key is invalid and was still showing the old (please delete me) value. It appears that some change(s) in GoDaddy's infrastructure causes some delays that were not seen before.I will be posting a change to allow users to configure an override of this sleep time via an environment variable.