starred/dehydrated
1
0
Fork 0
mirror of https://github.com/dehydrated-io/dehydrated.git synced 2026-09-02 08:57:22 +02:00
Code Issues 79 Packages Projects Releases 10 Wiki Activity

mixed challenges for one certificate #101

New Issue
Closed
opened 2025-12-29 00:24:51 +01:00 by adam · 1 comment
adam commented 2025-12-29 00:24:51 +01:00
Owner
Copy Link
Copy Source

Originally created by @ma0am on GitHub (May 12, 2016).

is it possible to extend the domain.txt config for using different challenges for each host?
aka i need to use dns-01 challenges for roundrobins and http-01 for some external domains
(host challenges for roundrobins are hard to deploy,
but dns access to external domains is not possible)

here is an example for an example.com certificate which i would like to build:

http-01 challenges for:

  • example.com
  • www.example.com
  • host.example.com
  • host.otherdomain.com

dns-01 challenges for:

  • roundrobin.example.com
  • more.roundrobin.example.com
Originally created by @ma0am on GitHub (May 12, 2016). is it possible to extend the domain.txt config for using different challenges for each host? aka i need to use dns-01 challenges for roundrobins and http-01 for some external domains (host challenges for roundrobins are hard to deploy, but dns access to external domains is not possible) here is an example for an **example.com certificate** which i would like to build: http-01 challenges for: - example.com - www.example.com - host.example.com - host.otherdomain.com dns-01 challenges for: - roundrobin.example.com - more.roundrobin.example.com
adam closed this issue 2025-12-29 00:24:51 +01:00
adam commented 2025-12-29 00:24:52 +01:00
Author
Owner
Copy Link
Copy Source

@lukas2511 commented on GitHub (May 16, 2016):

Not yet, sorry. The idea to have per-domain settings has been around for a while (see #105), but it hasn't been implemented yet.

Workaround for now would be to do something like ./letsencrypt.sh -c -t dns-01 -d roundrobin.example.com -d more.roundrobin.example.com.
This would have the same effect as if you'd have a line roundrobin.example.com more.roundrobin.example.com in domains.txt and dns-01 set in config.sh.

@lukas2511 commented on GitHub (May 16, 2016): Not yet, sorry. The idea to have per-domain settings has been around for a while (see #105), but it hasn't been implemented yet. Workaround for now would be to do something like `./letsencrypt.sh -c -t dns-01 -d roundrobin.example.com -d more.roundrobin.example.com`. This would have the same effect as if you'd have a line `roundrobin.example.com more.roundrobin.example.com` in domains.txt and dns-01 set in config.sh.
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 labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Melkus)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/dehydrated#101