]> git.ipfire.org Git - thirdparty/bind9.git/commitdiff
CHANGES, release notes
authorEvan Hunt <each@isc.org>
Tue, 2 Feb 2021 23:47:52 +0000 (15:47 -0800)
committerOndřej Surý <ondrej@sury.org>
Wed, 3 Feb 2021 11:06:17 +0000 (12:06 +0100)
CHANGES
doc/notes/notes-current.rst

diff --git a/CHANGES b/CHANGES
index cd946939a120ff4fe347e170217fe36abc89fd3c..1f8591e7ae5b8a6cce06b6dd093c89a5235d2ce4 100644 (file)
--- a/CHANGES
+++ b/CHANGES
@@ -1,7 +1,9 @@
-5576.  [func]          Initial support for DNS-over-HTTP(S). BIND now
-                       includes DNS-over-HTTP(S) layer built on top of nghttp2.
-                       Both encrypted and unencrypted HTTP/2 connections
-                       are supported. [GL !4566]
+5576.  [experimental]  Initial server-side implementation of DNS-over-HTTPS
+                       (DoH). Support for both TLS-encrypted and unencrypted
+                       HTTP/2 connections has been added to the network manager
+                       and integrated into named. (Note: there is currently no
+                       client-side support for DNS-over-HTTPS; this will be
+                       added to dig in a future release.) [GL #1144]
 
 5575.  [bug]           When migrating to dnssec-policy, BIND considered keys
                        with the "Inactive" and/or "Delete" timing metadata as
index ae6b01a7e29f0d6e5088d3b93e0fe70293b902d6..ba95f08b248be5d08314cf19de3951878c572b9a 100644 (file)
@@ -52,12 +52,12 @@ New Features
   an optional ``tls`` option which specifies either a previously configured
   ``tls`` statement or ``ephemeral``. [GL #2392]
 
-- ``named`` now has initial support for DNS-over-HTTP(S). Both
-  encrypted (via TLS) and unencrypted HTTP/2 connections are supported.
-  The latter are mostly there for debugging/troubleshooting
-  purposes and for the means of encryption offloading to third-party
-  software (as might be desirable in some environments to aid in TLS
-  certificates management).  [GL !4566]
+- ``named`` now supports DNS-over-HTTPS (DoH). Both TLS-encrypted and
+  unencrypted HTTP/2 connections are supported (the latter may be used to
+  offload encryption to other software).
+
+  Note that there is no client-side support for HTTPS as yet; this will be
+  added to ``dig`` in a future release. [GL #1144]
 
 Removed Features
 ~~~~~~~~~~~~~~~~