mir/bind
2
0
Fork 0
mirror of https://gitlab.isc.org/isc-projects/bind9 synced 2025-08-31 14:35:26 +00:00
Code Issues Releases Wiki Activity

Documentation update wrt IPv6 listening.

Browse Source 
With netmgr we're creating separate socket for each IPv6 interface,
just as with IPv4 - update documentation accordingly.
This commit is contained in:
Witold Kręcicki
2020-06-03 17:59:37 +02:00
committed by Ondřej Surý
parent 7bf3636160
commit 6a2100034b
2 changed files with 4 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
CHANGES
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]

20
doc/arm/reference.rst
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,
::