-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update TLSA DNS records with certbot-dns-cloudflare plugin #8769
Comments
Thanks for the suggestion! |
We've made a lot of changes to Certbot since this issue was opened. If you still have this issue with an up-to-date version of Certbot, can you please add a comment letting us know? This helps us to better see what issues are still affecting our users. If there is no activity in the next 30 days, this issue will be automatically closed. |
This ticket is still needed. |
We've made a lot of changes to Certbot since this issue was opened. If you still have this issue with an up-to-date version of Certbot, can you please add a comment letting us know? This helps us to better see what issues are still affecting our users. If there is no activity in the next 30 days, this issue will be automatically closed. |
Still needed. |
This is still needed. Right now you have either the choice to run certbot with "reuse_key = True" or use some hacks around, to deploy the TLSA keys in the same way, certbot negotiates via dns-rfc2136 the cert update. |
It would be nice if certbot could update those records after the challenge, as it's already using cloudflare API to add records anyway.
Wikipedia: https://en.wikipedia.org/wiki/DNS-based_Authentication_of_Named_Entities#TLSA_RR
Related: #230.
The text was updated successfully, but these errors were encountered: