aboutsummaryrefslogtreecommitdiff
path: root/releasenotes/notes/letsencrypt-dns01-challenge-432b5122dc832f4a.yaml
diff options
context:
space:
mode:
Diffstat (limited to 'releasenotes/notes/letsencrypt-dns01-challenge-432b5122dc832f4a.yaml')
-rw-r--r--releasenotes/notes/letsencrypt-dns01-challenge-432b5122dc832f4a.yaml14
1 files changed, 14 insertions, 0 deletions
diff --git a/releasenotes/notes/letsencrypt-dns01-challenge-432b5122dc832f4a.yaml b/releasenotes/notes/letsencrypt-dns01-challenge-432b5122dc832f4a.yaml
new file mode 100644
index 000000000..0b35c17ca
--- /dev/null
+++ b/releasenotes/notes/letsencrypt-dns01-challenge-432b5122dc832f4a.yaml
@@ -0,0 +1,14 @@
+---
+features:
+ - |
+ The ``letsencrypt-lego`` image now supports the ACME ``dns-01`` challenge
+ in addition to the existing ``http-01`` challenge. The
+ ``letsencrypt-certificates`` script accepts a new ``--challenge`` option
+ (defaulting to ``http-01``) and, when ``dns-01`` is selected, a
+ ``--dns-provider`` option naming any DNS provider supported by the bundled
+ ``lego`` binary. An optional ``--dns-additional-opts`` passthrough allows
+ forwarding extra ``lego`` DNS flags (such as ``--dns.resolvers`` or
+ ``--dns.propagation-disable-ans``) for environments where the default
+ authoritative name server propagation check cannot be performed. The
+ default behaviour is unchanged: without ``--challenge`` the ``http-01``
+ challenge is used exactly as before.