Skip to content
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

Manual DNS #46

Closed
centuryx476 opened this issue Jun 7, 2018 · 1 comment
Closed

Manual DNS #46

centuryx476 opened this issue Jun 7, 2018 · 1 comment
Labels
question Further information is requested

Comments

@centuryx476
Copy link

Hello,
Not sure if it is an issue or just how it works now.
In the previous versions when I will submit a new Cert it will give the "TXT" record value.
I will then submit it to my domain registrar and complete the process.

But now in version 2.4.0 I request a Cert it does not give me the "TXT" record value and just makes the cert.
Is that suppose to be happening ?

Thanks

@rmbolger
Copy link
Owner

rmbolger commented Jun 7, 2018

It depends on how long it has been since the original cert was generated. The challenges that you previously successfully validated have a window of time that they're good for. So if you request a new cert with names that have non-expired validations, you won't have to answer any new challenges for them. But if you add any new names, you'd have to answer challenges for them.

I believe the challenge validations used to be good for 60 days, but maybe a year ago they dropped to 30 days.

@rmbolger rmbolger added the question Further information is requested label Jun 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants