RcodeZero DNS Authenticator plugin for Certbot
pip install certbot-dns-rcode0
To start using DNS authentication for RcodeZero DNS, pass the following arguments on certbot’s command line:
|--authenticator certbot-dns-rcode0:dns-rcode0||select the authenticator plugin (Required)|
|--certbot-dns-rcode0:dns-rcode0-credentials||RcodeZero DNS credentials INI file. (Required)|
waiting time for DNS to propagate before asking
the ACME server to verify the DNS record.
(Default: 10, Recommended: >= 600)
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.
(Note that the verbose and seemingly redundant certbot-dns-rcode0: prefix is currently imposed by certbot for external plugins.)
An example credentials.ini file:
certbot_dns_rcode0:dns_rcode0_api_key = acme_0123456789abcdef0123456789abcdef01234567
The path to this file can be provided interactively or using the --certbot-dns-rcode0: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).
To acquire a single certificate for both example.com and *.example.com, waiting 900 seconds for DNS propagation:
certbot certonly \ --authenticator certbot-dns-rcode0:dns-rcode0 \ --certbot-dns-rcode0:dns-rcode0-credentials ~/.secrets/certbot/rcode0.ini \ --certbot-dns-rcode0:dns-rcode0-propagation-seconds 900 \ --server https://acme-v02.api.letsencrypt.org/directory \ -d 'example.com' \ -d '*.example.com'
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
|Filename, size||File type||Python version||Upload date||Hashes|
|Filename, size certbot_dns_rcode0-0.0.0.1-py2.py3-none-any.whl (7.2 kB)||File type Wheel||Python version py2.py3||Upload date||Hashes View|
|Filename, size certbot-dns-rcode0-0.0.0.1.tar.gz (8.2 kB)||File type Source||Python version None||Upload date||Hashes View|
Hashes for certbot_dns_rcode0-0.0.0.1-py2.py3-none-any.whl
Hashes for certbot-dns-rcode0-0.0.0.1.tar.gz