1 Name = "Hurricane Electric DNS"
2 Description = ''''''
3 URL = "https://dns.he.net/"
4 Code = "hurricane"
5 Since = "v4.3.0"
6 7 Example = '''
8 HURRICANE_TOKENS=example.org:token \
9 lego --dns hurricane -d '*.example.com' -d example.com run
10 11 HURRICANE_TOKENS=my.example.org:token1,demo.example.org:token2 \
12 lego --dns hurricane -d my.example.org -d demo.example.org
13 '''
14 15 Additional = """
16 Before using lego to request a certificate for a given domain or wildcard (such as `my.example.org` or `*.my.example.org`),
17 create a TXT record named `_acme-challenge.my.example.org`, and enable dynamic updates on it.
18 Generate a token for each URL with Hurricane Electric's UI, and copy it down.
19 Stick to alphanumeric tokens for greatest reliability.
20 21 To authenticate with the Hurricane Electric API,
22 add each record name/token pair you want to update to the `HURRICANE_TOKENS` environment variable, as shown in the examples.
23 Record names (without the `_acme-challenge.` component) and their tokens are separated with colons,
24 while the credential pairs are concatenated into a comma-separated list, like so:
25 26 ```
27 HURRICANE_TOKENS=my.example.org:token1,demo.example.org:token2
28 ```
29 30 If you are issuing both a wildcard certificate and a standard certificate for a given subdomain,
31 you should not have repeat entries for that name, as both will use the same credential.
32 33 ```
34 HURRICANE_TOKENS=example.org:token
35 ```
36 """
37 38 [Configuration]
39 [Configuration.Credentials]
40 HURRICANE_TOKENS = "TXT record names and tokens"
41 [Configuration.Additional]
42 HURRICANE_POLLING_INTERVAL = "Time between DNS propagation check in seconds (Default: 2)"
43 HURRICANE_PROPAGATION_TIMEOUT = "Maximum waiting time for DNS propagation (Default: 300)"
44 HURRICANE_SEQUENCE_INTERVAL = "Time between sequential requests in seconds (Default: 60)"
45 HURRICANE_HTTP_TIMEOUT = "API request timeout in seconds (Default: 30)"
46 47 [Links]
48 API = "https://dns.he.net/"
49