Originally created by @tommyjlong on GitHub (May 16, 2022).
If I were to use the dns-01 method for a challenge, and my provider only supports manual entry of TXT records (which I understand can be supported by dehydrated), then for renewals, would I have to repeat this manual entry on each renewal?
Thanks.
Originally created by @tommyjlong on GitHub (May 16, 2022).
If I were to use the dns-01 method for a challenge, and my provider only supports manual entry of TXT records (which I understand can be supported by dehydrated), then for renewals, would I have to repeat this manual entry on each renewal?
Thanks.
Unfortunately the answer to that is yes. Additionally this is not something dehydrated has any control over either.
Simply put, Let's Encrypt only keeps domain validations valid for 30 days, after that they have to be revalidated.
@jobe1986 commented on GitHub (May 17, 2022):
Unfortunately the answer to that is yes. Additionally this is not something dehydrated has any control over either.
Simply put, Let's Encrypt only keeps domain validations valid for 30 days, after that they have to be revalidated.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @tommyjlong on GitHub (May 16, 2022).
If I were to use the dns-01 method for a challenge, and my provider only supports manual entry of TXT records (which I understand can be supported by dehydrated), then for renewals, would I have to repeat this manual entry on each renewal?
Thanks.
@jobe1986 commented on GitHub (May 17, 2022):
Unfortunately the answer to that is yes. Additionally this is not something dehydrated has any control over either.
Simply put, Let's Encrypt only keeps domain validations valid for 30 days, after that they have to be revalidated.
@tommyjlong commented on GitHub (May 17, 2022):
That's what I thought.
Thanks for getting back on this.