Package: certbot-dns-freedns
FreeDNS - DNS Authenticator plugin for CertbotThis plugin automates the process of completing adns-01challenge
by creating, and subsequently removing, TXT records using the FreeDNS
Remote API.Installationpipinstallcertbot-dns-freednsNamed ArgumentsTo start using DNS authentication for freedns, pass the following
arguments on certbot’s command line:–authenticator dns-freednsselect the authenticator plugin
(Required)–dns-freedns-credentialsfreedns Remote User credentials
INI file. (Required)–dns-freedns-propagation-secondswaiting time for DNS to propagate
before asking the ACME server to
verify the DNS record. (Default:
120, Recommended: >= 600)(Note that the verbose and seemingly redundantcertbot-dns-freedns:prefix is currently imposed by certbot for
external plugins.)CredentialsAn examplecredentials.inifile:dns_freedns_username=myremoteuserdns_freedns_password=verysecureremoteuserpasswordThe path to this file can be provided interactively or using
the--dns-freedns-credentialscommand-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 freedns 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 adns-01challenge to acquire new certificates or revoke existing
certificates for associated domains, 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 likechmod 600to restrict access to the file).ExamplesTo acquire a single certificate for bothexample.comand*.example.com, waiting 900 seconds for DNS propagation:certbotcertonly\--authenticatordns-freedns\--dns-freedns-credentials/etc/letsencrypt/.secrets/domain.tld.ini\--dns-freedns-propagation-seconds900\--serverhttps://acme-v02.api.letsencrypt.org/directory\--agree-tos\--rsa-key-size4096\-d'example.com'\-d'*.example.com'DockerIn order to create a docker container with a certbot-dns-freedns
installation, create an empty directory with the followingDockerfile:FROMcertbot/certbotRUNpipinstallcertbot-dns-freednsProceed to build the image:dockerbuild-tcertbot/dns-freedns.Once that’s finished, the application can be run as follows:dockerrun--rm\-v/var/lib/letsencrypt:/var/lib/letsencrypt\-v/etc/letsencrypt:/etc/letsencrypt\--cap-drop=all\certbot/dns-freednscertonly\--authenticatordns-freedns\--dns-freedns-propagation-seconds900\--dns-freedns-credentials\/etc/letsencrypt/.secrets/domain.tld.ini\--no-self-upgrade\--keep-until-expiring--non-interactive--expand\--serverhttps://acme-v02.api.letsencrypt.org/directory\-dexample.com-d'*.example.com'It is suggested to secure the folder as follows:chownroot:root/etc/letsencrypt/.secretschmod600/etc/letsencrypt/.secrets