Merge branch '1782-ipv6-docs' into 'master'

Documentation update wrt IPv6 listening.

Closes #1782

See merge request isc-projects/bind9!3642
This commit is contained in:
Ondřej Surý 2020-06-04 13:53:17 +00:00
commit 2d6f379935
3 changed files with 9 additions and 20 deletions

View file

@ -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]

View file

@ -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,
::

View file

@ -122,6 +122,11 @@ Feature Changes
``rndc``, ``rndc-confgen``, and ``tsig-confgen`` were left in
``$sbindir``. [GL #1724]
- listen-on-v6 { any; } creates separate sockets for all interfaces,
while previously it created one socket on systems conforming to
:rfc:`3493` and :rfc:`3542`, this change was introduced in 9.16.0
but accudently ommited from documentation.
Bug Fixes
~~~~~~~~~