go/lego
go/lego
1
0
Fork 0
mirror of https://github.com/go-acme/lego.git synced 2024-12-23 01:07:23 +02:00
Code Issues Releases Activity
1225d05a2b
lego/docs/content/dns/zz_gen_technitium.md
Ludovic Fernandez 4efd1e1711
Add DNS provider for Technitium (#2332)
2024-11-10 16:27:08 +00:00

2.4 KiB
Raw Blame History

title date draft slug dnsprovider
Technitium 2019-03-03T16:39:46+01:00 false technitium
since code url
v4.20.0 technitium https://technitium.com/

Configuration for Technitium.

  • Code: technitium
  • Since: v4.20.0

Here is an example bash command using the Technitium provider:

TECHNITIUM_SERVER_BASE_URL="https://localhost:5380" \
TECHNITIUM_API_TOKEN="xxxxxxxxxxxxxxxxxxxxx" \
lego --email you@example.com --dns technitium -d '*.example.com' -d example.com run

Credentials

Environment Variable Name Description
TECHNITIUM_API_TOKEN API token
TECHNITIUM_SERVER_BASE_URL Server base URL

The environment variable names can be suffixed by _FILE to reference a file instead of a value. More information [here]({{% ref "dns#configuration-and-credentials" %}}).

Additional Configuration

Environment Variable Name Description
TECHNITIUM_HTTP_TIMEOUT API request timeout
TECHNITIUM_POLLING_INTERVAL Time between DNS propagation check
TECHNITIUM_PROPAGATION_TIMEOUT Maximum waiting time for DNS propagation
TECHNITIUM_TTL The TTL of the TXT record used for the DNS challenge

The environment variable names can be suffixed by _FILE to reference a file instead of a value. More information [here]({{% ref "dns#configuration-and-credentials" %}}).

Technitium DNS Server supports Dynamic Updates (RFC2136) for primary zones, so you can also use the RFC2136 provider.

RFC2136 provider is much better compared to the HTTP API option from security perspective. Technitium recommends to use it in production over the HTTP API.

More information