certbot-dns-multi
DNS plugin for Certbot which integrates with the 117+ DNS providers from the lego ACME client.
At the last check, the supported providers are:
35.com/三五互联, Active24, Akamai EdgeDNS, Alibaba Cloud DNS, AlibabaCloud ESA, all-inkl, Alwaysdata, Amazon Lightsail, Amazon Route 53, Anexia CloudDNS, ArtFiles, ArvanCloud, Aurora DNS, Autodns, Axelname, Azion, Azure (deprecated), Azure DNS, Baidu Cloud, Beget.com, Binary Lane, Bindman, Bluecat, Bluecat v2, BookMyName, Brandit (deprecated), Bunny, Checkdomain, Civo, Cloud.ru, CloudDNS, Cloudflare, ClouDNS, CloudXNS (Deprecated), ConoHa v2, ConoHa v3, Constellix, Core-Networks, CPanel/WHM, DDnss (DynDNS Service), Derak Cloud, deSEC.io, Designate DNSaaS for Openstack, Digital Ocean, DirectAdmin, DNS Made Easy, DNSExit, dnsHome.de, DNSimple, DNSPod (deprecated), Domain Offensive (do.de), Domeneshop, DreamHost, Duck DNS, Dyn, DynDnsFree.de, Dynu, EasyDNS, EdgeCenter, Efficient IP, Epik, Exoscale, External program, F5 XC, freemyip.com, FusionLayer NameSurfer, G-Core, Gandi, Gandi Live DNS (v5), Gigahost.no, Glesys, Go Daddy, Google Cloud, Google Domains, Gravity, Hetzner, Hosting.de, Hosting.nl, Hostinger, Hosttech, HTTP request, http.net, Huawei Cloud, Hurricane Electric DNS, HyperOne, IBM Cloud (SoftLayer), IIJ DNS Platform Service, Infoblox, Infomaniak, Internet Initiative Japan, Internet.bs, INWX, Ionos, Ionos Cloud, IPv64, ISPConfig 3, ISPConfig 3 - Dynamic DNS (DDNS) Module, iwantmyname (Deprecated), JD Cloud, Joker, Joohoi's ACME-DNS, KeyHelp, Leaseweb, Liara, Lima-City, Linode (v4), Liquid Web, Loopia, LuaDNS, Mail-in-a-Box, ManageEngine CloudDNS, Manual, Metaname, Metaregistrar, mijn.host, Mittwald, myaddr.{tools,dev,io}, MyDNS.jp, MythicBeasts, Name.com, Namecheap, Namesilo, NearlyFreeSpeech.NET, Neodigit, Netcup, Netlify, Nicmanager, NIFCloud, Njalla, Nodion, NS1, Octenium, Open Telekom Cloud, Oracle Cloud, OVH, plesk.com, Porkbun, PowerDNS, Rackspace, Rain Yun/雨云, RcodeZero, reg.ru, Regfish, RFC2136, RimuHosting, RU CENTER, Sakura Cloud, Scaleway, Selectel, Selectel v2, SelfHost.(de|eu), Servercow, Shellrent, Simply.com, Sonic, Spaceship, Stackpath, Syse, Technitium, Tencent Cloud DNS, Tencent EdgeOne, Timeweb Cloud, TodayNIC/时代互联, TransIP, UKFast SafeDNS, Ultradns, United-Domains, Variomedia, VegaDNS, Vercel, Versio.[nl|eu|uk], VinylDNS, Virtualname, VK Cloud, Volcano Engine/火山引擎, Vscale, Vultr, webnames.ca, webnames.ru, Websupport, WEDOS, West.cn/西部数码, Yandex 360, Yandex Cloud, Yandex PDD, Zone.ee, ZoneEdit, Zonomi
Installation
via snap
Using the certbot snap is the easiest way to use this plugin. See here for instructions on installing Certbot via snap.
sudo snap install certbot-dns-multi
sudo snap set certbot trust-plugin-with-root=ok
sudo snap connect certbot:plugin certbot-dns-multi
We previously published armhf snaps, but new snap releases are now published only for amd64 and arm64.
via pip
Compiled wheels are available for most x86_64/amd64 Linux distributions for Python 3.11+. On other platforms, pip will try to compile the plugin, which requires Go 1.24 or newer to be installed on your server.
| How did you install Certbot? | How to install the plugin |
|---|---|
From snap |
Don't use pip! Use the snap instructions above. |
Using the official Certbot pip instructions |
sudo /opt/certbot/bin/pip install certbot-dns-multi |
From apt, yum, dnf or any other distro package manager. (Requires Certbot 1.12.0 or newer.) |
pip install certbot-dns-multi |
via docker
Docker images for linux/amd64 and linux/arm64 are available from ghcr.io/alexzorin/certbot-dns-multi.
e.g.
docker run --rm -it -v /etc/letsencrypt:/etc/letsencrypt \
ghcr.io/alexzorin/certbot-dns-multi certonly \
-a dns-multi --dns-multi-credentials /etc/letsencrypt/dns-multi.ini \
-d "*.example.com" -d "example.com" --dry-run
Usage
certbot-dns-multi is controlled via a credentials file.
-
Head to https://go-acme.github.io/lego/dns/ and find your DNS provider in the list. In this example, we'll use
cloudflare. -
Create
/etc/letsencrypt/dns-multi.iniand enter the name of your provider, all lowercase, as below:dns_multi_provider = cloudflare
-
Following the instructions on https://go-acme.github.io/lego/dns/cloudflare/, we add the required configuration items:
dns_multi_provider = cloudflare CLOUDFLARE_DNS_API_TOKEN="1234567890abcdefghijklmnopqrstuvwxyz"
-
Save the file and secure it:
chmod 0600 /etc/letsencrypt/dns-multi.ini
-
Try issue a certificate now:
certbot certonly -a dns-multi \ --dns-multi-credentials=/etc/letsencrypt/dns-multi.ini \ -d "*.example.com" \ --dry-run
-
🥳, or if not, ask on the community forums for help.
1 maintainer
Release files for certbot-dns-multi 5.4.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| certbot_dns_multi-5.4.1.tar.gz | 114.3 kB | Details |
Built distributions (wheels)
Total release size: 283.4 MB
Release files / certbot_dns_multi-5.4.1.tar.gz
| Download URL | certbot_dns_multi-5.4.1.tar.gz |
|---|---|
| Size | 114.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b8c0d09f9ed4c11d7ebb762808c3eb250360745683c9952491dc8785a9007b97
|
|
BLAKE2b-256 checksum How to use checksums |
f5a5b40326b27e14c38959f8c602ca668e8a804a2ea5c85fbc592cdd40db296d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 31, 2026.
Transparency logRelease files / certbot_dns_multi-5.4.1-cp314-cp314-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
| Download URL | certbot_dns_multi-5.4.1-cp314-cp314-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 33.9 MB |
| Tags | CPython 3.14 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
16008780456a25c9cf593699f273029ded8bfcaf8db6674680b63786b0eb49a3
|
|
BLAKE2b-256 checksum How to use checksums |
ed349d790a37071182a4662dca2f09d052d74a49ed4ed78edbbcd8c3844e1eef
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 31, 2026.
Transparency logRelease files / certbot_dns_multi-5.4.1-cp314-cp314-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl
| Download URL | certbot_dns_multi-5.4.1-cp314-cp314-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl |
|---|---|
| Size | 36.9 MB |
| Tags | CPython 3.14 Linux glibc 2.28+ x86-64 Linux glibc 2.5+ x86-64 |
|
SHA-256 checksum How to use checksums |
38042fba1cd1a02498b6d64ce0cec065095343128c128462429e883e7aa64b3d
|
|
BLAKE2b-256 checksum How to use checksums |
828b7ce8895db524c79ca1c3fba2a0a18c7fa3512780e81322d7873702392b39
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 31, 2026.
Transparency logRelease files / certbot_dns_multi-5.4.1-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
| Download URL | certbot_dns_multi-5.4.1-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 33.9 MB |
| Tags | CPython 3.13 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
57e7d007ed50cd72037de9cc83d918c1bceeaa98cfed24ef4a173d8eb980685f
|
|
BLAKE2b-256 checksum How to use checksums |
b9f26ea869ed9b873a0ec8d6584fac423c880ab57f314e334d1a365833d8d497
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 31, 2026.
Transparency logRelease files / certbot_dns_multi-5.4.1-cp313-cp313-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl
| Download URL | certbot_dns_multi-5.4.1-cp313-cp313-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl |
|---|---|
| Size | 36.9 MB |
| Tags | CPython 3.13 Linux glibc 2.28+ x86-64 Linux glibc 2.5+ x86-64 |
|
SHA-256 checksum How to use checksums |
f025f3c1dd5ec1c47ee84563a279c5abbf5db425d827477239db21664c37c209
|
|
BLAKE2b-256 checksum How to use checksums |
68a3a9535f06ef14c4ae4d457cbf835d0af69dc2b53e751dcc4629df3553af2e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 31, 2026.
Transparency logRelease files / certbot_dns_multi-5.4.1-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
| Download URL | certbot_dns_multi-5.4.1-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 33.9 MB |
| Tags | CPython 3.12 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
1d8de3c42835a7a4a450eb19f81d613521b15cd3649f8673d7a25ce50b305607
|
|
BLAKE2b-256 checksum How to use checksums |
c84590314944894bafd1ce408a981eef47a04cbab622b57d7ff93a5ba3504ed4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 31, 2026.
Transparency logRelease files / certbot_dns_multi-5.4.1-cp312-cp312-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl
| Download URL | certbot_dns_multi-5.4.1-cp312-cp312-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl |
|---|---|
| Size | 36.9 MB |
| Tags | CPython 3.12 Linux glibc 2.28+ x86-64 Linux glibc 2.5+ x86-64 |
|
SHA-256 checksum How to use checksums |
8ced527a3407074853d3ad87fb23b2a92c774b08a24e3550842934fb68df6a75
|
|
BLAKE2b-256 checksum How to use checksums |
b274f48a3e47223ec6078e102b36c56393a58f6748620a509c8a22f13ffa471a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 31, 2026.
Transparency logRelease files / certbot_dns_multi-5.4.1-cp311-cp311-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
| Download URL | certbot_dns_multi-5.4.1-cp311-cp311-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 34.0 MB |
| Tags | CPython 3.11 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
f4cee0fa93a6f5d9e5b201f6c0355cbfc60bd59dfed330226f30eebebb116262
|
|
BLAKE2b-256 checksum How to use checksums |
b3f556b117fc9abf70749f8242ef81c8e91582c1afd9a1c667a8ce8f493fe99d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 31, 2026.
Transparency logRelease files / certbot_dns_multi-5.4.1-cp311-cp311-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl
| Download URL | certbot_dns_multi-5.4.1-cp311-cp311-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl |
|---|---|
| Size | 36.9 MB |
| Tags | CPython 3.11 Linux glibc 2.28+ x86-64 Linux glibc 2.5+ x86-64 |
|
SHA-256 checksum How to use checksums |
91f43f3cadc4d279f9dcebf3953b87f05602dbfe4f3025062a41568d6db4d457
|
|
BLAKE2b-256 checksum How to use checksums |
331e73e92112520e0de419befa333c80e745983c313c36e46f16e16f9e3b96f6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 31, 2026.
Transparency log
