3 ms·
> I also serve many domains with this project so I don't have the nice DNS-01 ACME verification features because not all DNS providers have an API. Are you awa
by throw0101a 7y ago
> I also serve many domains with this project so I don't have the nice DNS-01 ACME verification features because not all DNS providers have an API.
Are you aware of using ACME DNS aliasing with CNAMEs?
* https://www.eff.org/deeplinks/2018/02/technical-deep-dive-securing-automation-acme-dns-challenge-validation https://www.eff.org/deeplinks/2018/02/technical-deep-dive-se...
* https://github.com/Neilpang/acme.sh/wiki/DNS-alias-mode https://github.com/Neilpang/acme.sh/wiki/DNS-alias-mode
* https://dan.langille.org/2019/02/01/acme-domain-alias-mode/ https://dan.langille.org/2019/02/01/acme-domain-alias-mode/
My work's DNS provider does not have a handy API, so if we want a cert for the internal-only foo.example.com, we point _acme-challenge.foo to _acme-challenge.foo.dnstest.example.com. And the NS server for the dnstest.example.com lives in our DMZ and is only there to answer ACME queries from Let's Encrypt. We set up some scripting to allow updates to the NS server via nsupdate.
And there are ACME clients written specifically around the idea of having the client run on a different system than the web server:
* https://github.com/srvrco/getssl https://github.com/srvrco/getssl