DNS server alias (not different domain alias) #4909
|
We have one domain example.com and public DNS record _acme-challenge.example.com CNAME proxy.example.com, where is our small letsencrypt dedicated DNS server for the domain, updatable via nsupdate. What is correct syntax for acme.sh to use this dedicated DNS server, please? Thanks, Michal |
Replies: 2 comments
|
Another informations: The DNS records on proxy.example.com are updated correctly (acme.sh --dns dns_nsupdate ....). The problem seems to be that the external DNS check (from letsencrypt servers, I suppose) does not asks _acme-challenge.example.com. There is no attempt to connect to this DNS server from internet in firewall/server logs. |
|
acme.sh is doing its part -- the missing piece is public DNS resolution, not the update. When Let's Encrypt validates, it resolves Without that delegation, the query is answered by your main DNS provider (which has no TXT) and your server is never contacted -- exactly the "no connection in the logs" you see. Two fixes together:
export NSUPDATE_SERVER="proxy.example.com"
export NSUPDATE_KEY="/path/to/tsig.key"
export NSUPDATE_ZONE="proxy.example.com"
acme.sh --issue -d example.com --dns dns_nsupdate --domain-alias proxy.example.comCleaner alternative: delegate a dedicated sub-zone |
acme.sh is doing its part -- the missing piece is public DNS resolution, not the update.
When Let's Encrypt validates, it resolves
_acme-challenge.example.com, follows your CNAME toproxy.example.com, then asks whoever is authoritative forproxy.example.comfor the TXT. Your dedicated nsupdate server only gets that query if the publicexample.comzone delegatesproxy.example.comto it with an NS record:Without that delegation, the query is answered by your main DNS provider (which has no TXT) and your server is never contacted -- exactly the "no connection in the logs" you see.
Two fixes together:
example.com