Originally created by @astorath on GitHub (Jul 18, 2019).
Hi!
How can I use domain/challenge alias with dehydrated? Have found nothing in docs about that...
Originally created by @astorath on GitHub (Jul 18, 2019).
Hi!
How can I use domain/challenge alias with dehydrated? Have found nothing in docs about that...
Could you elaborate as to what you mean by domain/challenge alias?
The reason I ask is the terminology you used can have multiple different meanings.
Either way, if you mean CNAME records, then yes Let's Encrypt's dns-01 validation will follow CNAME records. I for example use _acme-challenge. CNAME'ed to _acme-challenge.. so I keep all my dynamic DNS under a single domain name.
@jobe1986 commented on GitHub (Jul 18, 2019):
Could you elaborate as to what you mean by domain/challenge alias?
The reason I ask is the terminology you used can have multiple different meanings.
Either way, if you mean CNAME records, then yes Let's Encrypt's dns-01 validation will follow CNAME records. I for example use _acme-challenge.<domain> CNAME'ed to _acme-challenge.<domain>.<dynamicdnsdomain> so I keep all my dynamic DNS under a single domain name.
How do you setup dehydrated then? Where should I put alias domain (the one dehydrated will use to setup challenges)?
@astorath commented on GitHub (Jul 18, 2019):
@jobe1986, yep, I mean CNAME records.
How do you setup dehydrated then? Where should I put alias domain (the one dehydrated will use to setup challenges)?
That would have to be accounted for by your custom hook script that handles the dynamic DNS updates, as to how exactly that really depends on which hook script you use, and I only have experience using the basic nsupdate based hook script.
@jobe1986 commented on GitHub (Jul 18, 2019):
That would have to be accounted for by your custom hook script that handles the dynamic DNS updates, as to how exactly that really depends on which hook script you use, and I only have experience using the basic nsupdate based hook script.
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 @astorath on GitHub (Jul 18, 2019).
Hi!
How can I use domain/challenge alias with dehydrated? Have found nothing in docs about that...
@jobe1986 commented on GitHub (Jul 18, 2019):
Could you elaborate as to what you mean by domain/challenge alias?
The reason I ask is the terminology you used can have multiple different meanings.
Either way, if you mean CNAME records, then yes Let's Encrypt's dns-01 validation will follow CNAME records. I for example use _acme-challenge. CNAME'ed to _acme-challenge.. so I keep all my dynamic DNS under a single domain name.
@astorath commented on GitHub (Jul 18, 2019):
@jobe1986, yep, I mean CNAME records.
How do you setup dehydrated then? Where should I put alias domain (the one dehydrated will use to setup challenges)?
@jobe1986 commented on GitHub (Jul 18, 2019):
That would have to be accounted for by your custom hook script that handles the dynamic DNS updates, as to how exactly that really depends on which hook script you use, and I only have experience using the basic nsupdate based hook script.
@astorath commented on GitHub (Jul 18, 2019):
I see, thanks