certbot-dns-nextlayer
next layer 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 # optional
pip install certbot-dns-nextlayer
Verify:
$ certbot plugins --text
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
* dns-nextlayer
Description: Obtain certificates using a DNS TXT record by using the nextlayer
dns api.
Interfaces: IAuthenticator, IPlugin
Entry point: dns-nextlayer = certbot_dns_nextlayer.dns_nextlayer:Authenticator
...
...
Configuration
The credentials file e.g. ~/nldns-credentials.ini should look like this:
dns_nextlayer_token=put_your_token_here
Usage
Example command
certbot certonly --authenticator dns-nextlayer --dns-nextlayer-credentials=~/nldns-credentials.ini -d nextlayer.at
Zone detection method
We've added the configuration parameter --dns-nextlayer-method to select the way our certbot plugin determines the correct zone to add the record to. Currently there are 3 options you can choose from.
intelligent
This is the default method.
It tries to determine the zone intelligently by extracting the TLD and re-adding the first level.
Examples:
* dns.nextlayer.at: nextlayer.at
* dns.nextlayer.co.at: nextlayer.co.at
* www.dns.nextlayer.co.at: nextlayer.co.at
remove-first
This method just removes the first level of the requested domain.
Examples:
* dns.nextlayer.at: nextlayer.at
* dns.nextlayer.co.at: nextlayer.co.at
* www.dns.nextlayer.co.at: dns.nextlayer.co.at
none
This method does what it's called. No magic.
Examples:
* dns.nextlayer.at: dns.nextlayer.at
* dns.nextlayer.co.at: dns.nextlayer.co.at
* www.dns.nextlayer.co.at: www.dns.nextlayer.co.at
Metadata
Release files for certbot-dns-nextlayer 1.1.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| certbot_dns_nextlayer-1.1.3.tar.gz | 4.5 kB | Without provenance | Details for certbot_dns_nextlayer-1.1.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| certbot_dns_nextlayer-1.1.3-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for certbot_dns_nextlayer-1.1.3-py2.py3-none-any.whl |
Total release size: 9.8 kB
Release files / certbot_dns_nextlayer-1.1.3.tar.gz
| Download URL | certbot_dns_nextlayer-1.1.3.tar.gz |
|---|---|
| Size | 4.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ee5776666429bd1562b3ba0c6851a3a4fe9a71a2f6f48c1765edc794545f2751
|
|
BLAKE2b-256 checksum How to use checksums |
6aa99b0a0a10dc0ed48a1f67a61e9a78673a5c70d94e6a4c6c05568aed239ab7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.0
|
Release files / certbot_dns_nextlayer-1.1.3-py2.py3-none-any.whl
| Download URL | certbot_dns_nextlayer-1.1.3-py2.py3-none-any.whl |
|---|---|
| Size | 5.3 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
f7a7f0ca6b9c8a38ae4a7888f15a8e66d904a0ef8c2d46ab168647b7c987c091
|
|
BLAKE2b-256 checksum How to use checksums |
435b3007b67e122384cd149c60095a6f1484258f95f700cdc5cd149c76fde47e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.0
|
Security for certbot-dns-nextlayer 1.1.3
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.