Package: certbot-dns-nicru
certbot-dns-nicruNICru DNS Authenticator plugin for CertbotThis plugin automates the process of completing adns-01challenge by
creating, and subsequently removing, TXT records using the nic.ru Remote API.Installationpipinstallcertbot-dns-nicruNamed ArgumentsTo start using DNS authentication for nicru, pass the following arguments on
certbot's command line:--authenticator dns-nicrunicru config INI file. (Required)--dns-nicru-propagation-seconds <second>waiting time for DNS to propagate before askingCredentialsAn examplecredentials.inifile:dns_nicru_client_id=application-iddns_nicru_client_secret=application-tokendns_nicru_username=0001110/NIC-Ddns_nicru_password=passworddns_nicru_scope=.+:.+/zones/example.com(/.+)?dns_nicru_service=DNS_SERVICE_NAMEdns_nicru_zone=example.comWhere:application-id, application-token - credentials for oath 2.0, they were got afterregistrationapplication.nicru_username, nicru_passoword - credentials for access to nic.runicru_service - the name of service, it can be taken from page:https://www.nic.ru/manager/services.cgi?step=srv.my_dnsThe path to this file can be provided interactively or using the--dns-nicru-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 ispconfig 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-nicru\--dns-nicru-credentials/etc/letsencrypt/.secrets/domain.tld.ini\--dns-nicru-propagation-seconds300\--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-ispconfig installation,
create an empty directory with the followingDockerfile:FROMcertbot/certbotRUNpipinstallcertbot-dns-nicruProceed to build the image:dockerbuild-tcertbot/dns-nicru.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-nicru certonly \
    --authenticator dns-nicru \
    --dns-nicru-propagation-seconds 300 \
    --dns-nicru-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:chownroot:root/etc/letsencrypt/.secrets
chmod600/etc/letsencrypt/.secrets