certbot-dns-dynudns 0.0.6

Dynu DNS Authenticator plugin for Certbot

certbot-dns-dynudns

Dynu DNS Authenticator plugin for Certbot.

This plugin is built from the ground up and follows the development style and life-cycle of other certbot-dns-* plugins found in the Official Certbot Repository.

Installation

pip install --upgrade certbot
pip install certbot-dns-dynudns

Verify:

$ certbot plugins --text

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
* dns-dynu
Description: Obtain certificates using a DNS TXT record (if you are using Dynu
for DNS.)
Interfaces: Authenticator, Plugin
Entry point: dns-dynu = certbot_dns_dynudns.dns_dynu:Authenticator

...
...

Configuration

The credentials file e.g. ~/dynu-credentials.ini should look like this:

dns_dynu_auth_token = AbCbASsd!@34

Usage

certbot ... \
        --authenticator dns-dynu  \
        --dns-dynu-credentials ~/dynu-credentials.ini \
        certonly

FAQ

Why such long name for a plugin?

This follows the upstream nomenclature: certbot-dns-<dns-provider>.

Why do I have to use : separator in the name? And why are the configuration file parameters so weird?

This is a limitation of the Certbot interface towards third-party plugins.

For details read the discussions:

• https://github.com/certbot/certbot/issues/6504#issuecomment-473462138
• https://github.com/certbot/certbot/issues/6040
• https://github.com/certbot/certbot/issues/4351
• https://github.com/certbot/certbot/pull/6372

Development

Create a virtualenv, install the plugin (editable mode), spawn the environment and run the test:

virtualenv -p python3 .venv
. .venv/bin/activate
pip install -e .
docker-compose up -d
./test/run_certonly.sh test/dynu-credentials.ini

Credits

dns-lexicon

Helpful links

DNS Plugin list

acme.sh

dynu with acme.sh

dynu api