Skip to main content

RcodeZero 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 RcodeZero DNS API via lexicon.

Installation

pip install certbot-dns-rcode0

Named Arguments

To start using DNS authentication for RcodeZero DNS, pass the following arguments on certbot’s command line:

--authenticator dns-rcode0

select the authenticator plugin (Required)

--dns-rcode0-credentials

RcodeZero DNS credentials INI file. (Required)

--dns-rcode0-propagation-seconds

waiting time for DNS to propagate before asking
the ACME server to verify the DNS record.
(Default: 10, Recommended: >= 600)

--dns-rcode0-acme-domain

domain used to store the acme challanges. A CNAME from
_acme_challenge.<domain> must point to <domain>.<acme-domain>
The RcodeZero-Providers updates the challange in acme-domain
which must be hosted on RcodeZero. (optional)

You may need to set an even higher propagation time (>= 900 seconds) to give the RcodeZero DNS network time to propagate the entries! This may be annoying when calling certbot manually but should not be a problem in automated setups.

Credentials

Use of this plugin requires a configuration file containing RcodeZero DNS API ACME token, obtained from your RcodeZero account page. See also the RcodeZero DNS API documentation.

An example credentials.ini file:

dns_rcode0_api_key  = acme_0123456789abcdef0123456789abcdef01234567

The path to this file can be provided interactively or using the --dns-rcode0-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 the API token as you would protect the password to your RcodeZero 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-01 challenge to acquire new certificates or revoke existing certificates for any domain under the RcodeZero account, even if those domains aren’t being managed by this server.

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 600 to restrict access to the file).

Examples

To acquire a single certificate for both example.com and *.example.com, waiting 900 seconds for DNS propagation:

certbot certonly \
  --authenticator dns-rcode0 \
  --dns-rcode0-credentials ~/.secrets/certbot/rcode0.ini \
  --dns-rcode0-propagation-seconds 900 \
  --server https://acme-v02.api.letsencrypt.org/directory \
  -d 'example.com' \
  -d '*.example.com'

Release files for certbot-dns-rcode0 0.0.0.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for certbot-dns-rcode0 0.0.0.2
File Size Uploaded
certbot_dns_rcode0-0.0.0.2.tar.gz 8.4 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for certbot-dns-rcode0 0.0.0.2
File Interpreter ABI Platform
certbot_dns_rcode0-0.0.0.2-py2.py3-none-any.whl Python 2, Python 3 none any Details

Total release size: 17.3 kB

Release files / certbot_dns_rcode0-0.0.0.2.tar.gz

Download URL certbot_dns_rcode0-0.0.0.2.tar.gz
Size 8.4 kB
Tags Source
SHA-256 checksum
How to use checksums
9075ed39d5375bf78c7c7a03307b3cc52923adce263fadc8f0ccbd8ee8006023
BLAKE2b-256 checksum
How to use checksums
1a9dffd67d8546012c1c10bddf766d85fc2aa024150a46410c26b1a536be2cbc
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.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 21, 2025.

Transparency log

Release files / certbot_dns_rcode0-0.0.0.2-py2.py3-none-any.whl

Download URL certbot_dns_rcode0-0.0.0.2-py2.py3-none-any.whl
Size 8.9 kB
Tags Python 2 Python 3
SHA-256 checksum
How to use checksums
b03db99b6804299e6acc2baffed38360e272f12830ec6290bdd91995c10c9c5e
BLAKE2b-256 checksum
How to use checksums
98858b06111cdf5ca81bf04e4c14eb14df195839879ad8abe869f3da0556889b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.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 21, 2025.

Transparency log

Release history Release notifications | RSS feed

This release

0.0.0.2 This release

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page