diff --git a/doc/arm/Bv9ARM.ch06.html b/doc/arm/Bv9ARM.ch06.html index db86971f00..b6a869967b 100644 --- a/doc/arm/Bv9ARM.ch06.html +++ b/doc/arm/Bv9ARM.ch06.html @@ -94,7 +94,7 @@ HREF="Bv9ARM.ch06.html#Configuration_File_Grammar" >
By default, the server does not bind a separate socket to each -IPv6 interface address as it does for IPv4. Instead, it listens on the -IPv6 wildcard address. -Alternatively, a list of IPv6 addresses can be specified, in which case -the server listens on a separate socket for each specified address.
The listen-on-v6 option is used to +specify the interfaces and the ports on which the server will listen +for incoming queries sent using IPv6.When
{ any; }is specified +as the address_match_list for the +listen-on-v6 statement, +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.
Multiple 6.2.16.6. Query Address
[RFC974] [RFC1034] [RFC1035] [RFC2181] [RFC2308] [RFC1995] [RFC1996] [RFC2136] [RFC2845] [RFC1886] [RFC2065] [RFC2137] [RFC1535] [RFC1536] [RFC1982] [RFC1183] [RFC1706] [RFC2168] [RFC1876] [RFC2052] [RFC2163] [RFC2230] [RFC1101] [RFC1123] [RFC1591] [RFC2317] [RFC1537] [RFC1912] [RFC2010] [RFC2219] [RFC1464] [RFC1713] [RFC1794] [RFC2240] [RFC2345] [RFC2352] [RFC1712] Proposed Standards Still Under Development
Other Important RFCs About DNS
Resource Record Types
DNS
DNS
Other DNS
Obsolete and Unimplemented Experimental RRs
A.3.3. Other Documents About BIND
Bibliography