Integrations
How each ACME client issues a certificate for a DNSMint hostname over DNS-01, which is what a wildcard or a machine on a private address needs. A hostname on a public address that wants no wildcard needs none of this: point the client at the hostname and it validates over HTTP-01, as in the quickstart.
Proxies and servers
ACME clients
The dns_dnsmint plugin takes the key, and saves it after the first run so renewals need no environment.
lego's built-in httpreq provider, with the key as the basic-auth password. Nothing to pre-seed.
No plugin. certbot hands the challenge to two hook scripts of yours, which is all our endpoints want.
The PowerShell client, and the way to do this on Windows Server.
A webhook solver that runs in your cluster and reads one API key from a Secret.
Platforms
None of the three has a DNS provider of its own, and all three arrive at lego's list. The only way to answer DNS-01 behind NAT.
An external-dns provider, for the half of a cluster's DNS that is not certificates.
Other ways in
No recipe needs it any more, but the DNS-01 API speaks acme-dns for a client that expects it.
A hostname is worth most at the moment the machine is created, and machines are created in Terraform.
An endpoint rather than a package, for an agent that asks for the hostname itself, mid-task.
Every recipe here is verified against the client's current release, and the modules are ours to fix. If one of them fails, or a client you use is missing, write to hello@dnsmint.com. Bugs in the packages can also go straight to their issue trackers on GitHub.