From: Witold Kręcicki <wpk@isc.org>
Date: Wed, 3 Jun 2020 15:59:37 +0000 (+0200)
Subject: Documentation update wrt IPv6 listening.
X-Git-Tag: v9.17.2~17^2~1
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=6a2100034bcb43139ee85785b6f1d1831ccd279d;p=thirdparty%2Fbind9.git

Documentation update wrt IPv6 listening.

With netmgr we're creating separate socket for each IPv6 interface,
just as with IPv4 - update documentation accordingly.
---

diff --git a/CHANGES b/CHANGES
index 0b41d469bd6..173e8dbd156 100644
--- a/CHANGES
+++ b/CHANGES
@@ -1,3 +1,7 @@
+5430.	[doc]		Update docs - with netmgr we're creating separate
+			socket for each IPv6 interface, just as with IPv4.
+			[GL #1782]
+
 5429.	[cleanup]	Move BIND binaries which are neither daemons nor
 			administrative programs to $bindir. [GL #1724]
 
diff --git a/doc/arm/reference.rst b/doc/arm/reference.rst
index bfd18095b13..07a923bb2e3 100644
--- a/doc/arm/reference.rst
+++ b/doc/arm/reference.rst
@@ -2433,26 +2433,6 @@ ports on which the server listens for incoming queries sent using
 IPv6. If not specified, the server listens on port 53 on all IPv6
 interfaces.
 
-When
-
-::
-
-   { any; }
-
-is specified as the ``address_match_list`` for the ``listen-on-v6``
-option, the server does not bind a separate socket to each IPv6
-interface address as it does for IPv4, if the operating system has enough
-API support for IPv6 (specifically if it conforms to :rfc:`3493` and
-:rfc:`3542`). Instead, it listens on the IPv6 wildcard address. If the system
-only has incomplete API support for IPv6, however, the behavior is the
-same as that for IPv4.
-
-A list of particular IPv6 addresses can also be specified, in which case
-the server listens on a separate socket for each specified address,
-regardless of whether the desired API is supported by the system. IPv4
-addresses specified in ``listen-on-v6`` are ignored, with a logged
-warning.
-
 Multiple ``listen-on-v6`` options can be used. For example,
 
 ::