docs/content/dns/zz_gen_technitium.md
Configuration for Technitium.
<!--more-->technitiumHere is an example bash command using the Technitium provider:
TECHNITIUM_SERVER_BASE_URL="https://localhost:5380" \
TECHNITIUM_API_TOKEN="xxxxxxxxxxxxxxxxxxxxx" \
lego --dns technitium -d '*.example.com' -d example.com run
| 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" %}}).
| Environment Variable Name | Description |
|---|---|
TECHNITIUM_HTTP_TIMEOUT | API request timeout in seconds (Default: 30) |
TECHNITIUM_POLLING_INTERVAL | Time between DNS propagation check in seconds (Default: 2) |
TECHNITIUM_PROPAGATION_TIMEOUT | Maximum waiting time for DNS propagation in seconds (Default: 60) |
TECHNITIUM_TTL | The TTL of the TXT record used for the DNS challenge in seconds (Default: 120) |
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.