starred/dehydrated
1
0
Fork 0
mirror of https://github.com/dehydrated-io/dehydrated.git synced 2026-01-13 15:13:33 +01:00
Code Issues 79 Packages Projects Releases 10 Wiki Activity

Does the DNS update hook need to be run for subsequent verifications after the first verification in DNS mode? #168

New Issue
Closed
opened 2025-12-29 00:26:23 +01:00 by adam · 2 comments
adam commented 2025-12-29 00:26:23 +01:00
Owner
Copy Link

Originally created by @leaf-node on GitHub (Nov 29, 2016).

I didn't find this information in your documentation, but from what I can gather, the presence of the plethora of hooks suggests that automation is necessary because each month or two, full DNS verification with hooks is necessary when verifying in DNS mode.

Is this correct? Thanks!

Originally created by @leaf-node on GitHub (Nov 29, 2016). I didn't find this information in your documentation, but from what I can gather, the presence of the plethora of hooks suggests that automation is necessary because each month or two, full DNS verification with hooks is necessary when verifying in DNS mode. Is this correct? Thanks!
adam closed this issue 2025-12-29 00:26:23 +01:00
adam commented 2025-12-29 00:26:24 +01:00
Author
Owner
Copy Link

@whereisaaron commented on GitHub (Dec 25, 2016):

Whether you use HTTP or DNS verification, Let's Encrypt certificates are valid for only 90 days. So you have to automate re-verifying and issuing new certificates every couple months, plus deploying the new certs to any service that uses them, and restarting the service if necessary.

@whereisaaron commented on GitHub (Dec 25, 2016): Whether you use HTTP or DNS verification, Let's Encrypt certificates are valid for only 90 days. So you have to automate re-verifying and issuing new certificates every couple months, plus deploying the new certs to any service that uses them, and restarting the service if necessary.
adam commented 2025-12-29 00:26:25 +01:00
Author
Owner
Copy Link

@leaf-node commented on GitHub (Dec 25, 2016):

Thanks, that clarifies. I wasn't sure whether a static DNS config could be used for later verification.

@leaf-node commented on GitHub (Dec 25, 2016): Thanks, that clarifies. I wasn't sure whether a static DNS config could be used for later verification.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Complicated
bug
enhancement
help wanted
pull-request
Mirrored from GitHub Pull Request
 suggestions wanted
testing
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/dehydrated#168
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?