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

Responding to challanges when many SANs #239

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

Originally created by @belliash on GitHub (Aug 4, 2017).

I got a question / problem regarding responding to challenges.

Actually, according to dehydrated output, it requests a challange for all SANs in CSR and then launches a hook, which inserts TXT record. After wards it sends a response to challange and cleanup TXT records. Then repeat.

My problem is that I need to wait few minutes to propagate the changes in DNS. If I add a sleep to hook after inserting TXT record it takes a lot of time to wait for every TXT record.

What would solve my problem is to add all TXT records, wait some time, respond to all challanges and finally cleanup all TXT records.

Is that possible with dehydrated?

Originally created by @belliash on GitHub (Aug 4, 2017). I got a question / problem regarding responding to challenges. Actually, according to dehydrated output, it requests a challange for all SANs in CSR and then launches a hook, which inserts TXT record. After wards it sends a response to challange and cleanup TXT records. Then repeat. My problem is that I need to wait few minutes to propagate the changes in DNS. If I add a sleep to hook after inserting TXT record it takes a lot of time to wait for every TXT record. What would solve my problem is to add all TXT records, wait some time, respond to all challanges and finally cleanup all TXT records. Is that possible with dehydrated?
adam closed this issue 2025-12-29 01:19:36 +01:00
adam commented 2025-12-29 01:19:36 +01:00
Author
Owner
Copy Link

@txr13 commented on GitHub (Aug 4, 2017):

You should look into the HOOK_CHAIN parameter. It's designed for exactly this sort of issue.

@txr13 commented on GitHub (Aug 4, 2017): You should look into the HOOK_CHAIN parameter. It's designed for exactly this sort of issue.
adam commented 2025-12-29 01:19:37 +01:00
Author
Owner
Copy Link

@belliash commented on GitHub (Aug 6, 2017):

That's it! Thanks.

@belliash commented on GitHub (Aug 6, 2017): That's it! Thanks.
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#239
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?