certbot-dns-ionos
IONOS DNS Authenticator plugin for Certbot
This plugin automates the process of completing a dns-01 challenge by
creating, and subsequently removing, TXT records using the IONOS Remote API.
Configuration of IONOS
In the System -> Remote Users you have to have a user, with the following rights
- Client Functions
- DNS zone functions
- DNS txt functions
Installation
Snap
Snap version will be compatible with certbot 3.0. Thanks to DorianCoding to make this plugin avalabe in the Snap Store.
Pip
pip install certbot-dns-ionos
Named Arguments
To start using DNS authentication for ionos, pass the following arguments on certbot's command line:
| Command args | Command definition |
|---|---|
--authenticator dns-ionos |
select the authenticator plugin (Required) |
--dns-ionos-credentials |
ionos Remote User credentials INI file. (Required) |
--dns-ionos-propagation-seconds |
waiting time for DNS to propagate before asking the ACME server to verify the DNS record. (Default: 10, Recommended: 60) |
Credentials
An example credentials.ini file:
dns_ionos_prefix = myapikeyprefix
dns_ionos_secret = verysecureapikeysecret
dns_ionos_endpoint = https://api.hosting.ionos.com
The key can be managed under the following link: https://developer.hosting.ionos.de/?source=IonosControlPanel
The path to this file can be provided interactively or using the
--dns-ionos-credentials command-line argument. Certbot
records the path to this file for use during renewal, but does not store the file's contents.
[!CAUTION] You should protect these API credentials as you would the password to your ionos account. Users who can read this file can use these credentials to issue arbitrary API calls on your behalf. Users who can cause Certbot to run using these credentials can complete a
dns-01challenge to acquire new certificates or revoke existing certificates for associated domains, even if those domains aren't being managed by this server.
[!WARNING] Certbot will emit a warning if it detects that the credentials file can be accessed by other users on your system. The warning reads "Unsafe permissions on credentials configuration file", followed by the path to the credentials file. This warning will be emitted each time Certbot uses the credentials file, including for renewal, and cannot be silenced except by addressing the issue (e.g., by using a command like
chmod 600to restrict access to the file andchmod 700to restrict access to the folder).
Examples
To acquire a single certificate for both example.com and
*.example.com, waiting 900 seconds for DNS propagation:
certbot certonly \
--authenticator dns-ionos \
--dns-ionos-credentials /etc/letsencrypt/.secrets/domain.tld.ini \
--dns-ionos-propagation-seconds 900 \
--server https://acme-v02.api.letsencrypt.org/directory \
--agree-tos \
--rsa-key-size 4096 \
-d 'example.com' \
-d '*.example.com'
Docker
In order to create a docker container with a certbot-dns-ionos installation,
create an empty directory with the following Dockerfile:
FROM certbot/certbot
RUN pip install certbot-dns-ionos
Proceed to build the image
docker build -t certbot/dns-ionos .
Once that's finished, the application can be run as follows::
docker run --rm \
-v /var/lib/letsencrypt:/var/lib/letsencrypt \
-v /etc/letsencrypt:/etc/letsencrypt \
--cap-drop=all \
certbot/dns-ionos certonly \
--authenticator dns-ionos \
--dns-ionos-propagation-seconds 900 \
--dns-ionos-credentials \
/etc/letsencrypt/.secrets/domain.tld.ini \
--no-self-upgrade \
--keep-until-expiring --non-interactive --expand \
--server https://acme-v02.api.letsencrypt.org/directory \
-d example.com -d '*.example.com'
It is suggested to secure the folder as follows
chown root:root /etc/letsencrypt/.secrets
chmod 700 /etc/letsencrypt/.secrets
The file 'domain.tld.ini' must be replaced with the version of the example 'credentials.ini' adapted to your provider.
Changelog
- 2024.11.09
- Update for Certbot 3.0.0
- 2024.10.20
- fix: set long_description_content_type to text/markdown. This error breaks the upload to pypi
- 2024.10.19
- Update for Certbot 2.11.0
- Update README.md, changed from README.rst
- Addition of a snap
- Correction in case of API error
- 2024.01.08
- Update README.rst
- Add Link to IONOS control panel and reference between credentials.ini and domain.tld.ini
- 2023.11.13
- Fix managed zone lookup to ensure correct domain is selected where there are two domains with the same ending e.g. example.com and thisisanexample.com (PR #22)
- 2022.11.24
- Remove zope to fix compatibility with Certbot 2.x (Fixes #19)
- As a reminder, Certbot will default to issuing ECDSA certificates from release 2.0.0.
- If you update from a prior certbot release, run the plugin once manually. You will be prompted to update RSA key type to ECDSA.
- 2022.05.15
- Added capability to handle multiple domain validations #16
- 2021.09.20.post1
- Fix version number
- 2021.09.20
- Fix #9 Domain not known when using subdomain
Related Plugins
It's important to note that this plugin targets IONOS Developer DNS API. If you are using IONOS Cloud DNS service, there is a different plugin provided by IONOS: https://github.com/ionos-cloud/certbot-dns-ionos-cloud
Release files for certbot-dns-ionos 2024.11.9
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_ionos-2024.11.9.tar.gz | 14.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| certbot_dns_ionos-2024.11.9-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 28.7 kB
Release files / certbot_dns_ionos-2024.11.9.tar.gz
| Download URL | certbot_dns_ionos-2024.11.9.tar.gz |
|---|---|
| Size | 14.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
619aa7965272aef93d080094e0b7b79da0598d89567511cb683d44db6fa8c803
|
|
BLAKE2b-256 checksum How to use checksums |
4a1f53d64b33a63eafc8640c14c41f1df68b5983aac917b83f83c250588034e3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
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 Nov 9, 2024.
Transparency logRelease files / certbot_dns_ionos-2024.11.9-py2.py3-none-any.whl
| Download URL | certbot_dns_ionos-2024.11.9-py2.py3-none-any.whl |
|---|---|
| Size | 14.1 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
333be82806ae28a02c979baa8eb0bbc4862ad26549f60685468fadbf1fe3609e
|
|
BLAKE2b-256 checksum How to use checksums |
8fa7a5245b64202d8af8a113412718e7233f77404f8b912b8f2710d3e628eaf6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
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 Nov 9, 2024.
Transparency log