Skip to content
Discussion options

You must be logged in to vote

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 to proxy.example.com, then asks whoever is authoritative for proxy.example.com for the TXT. Your dedicated nsupdate server only gets that query if the public example.com zone delegates proxy.example.com to it with an NS record:

proxy.example.com.   IN NS   ns.your-dedicated-server.example.com.

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:

  1. In the public example.com

Replies: 2 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by neilpang
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants