From: Mark Andrews <marka@isc.org>
Date: Wed, 11 Jul 2018 02:18:27 +0000 (+1000)
Subject: Document ipv4only-enable, ipv4only-contact and ipv4only-server.
X-Git-Tag: v9.17.9~26^2~3
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=64c45abab267eb821c3ea49c1518767d7654fac3;p=thirdparty%2Fbind9.git

Document ipv4only-enable, ipv4only-contact and ipv4only-server.
---

diff --git a/doc/arm/reference.rst b/doc/arm/reference.rst
index 726f37ed5a8..0790cff7f5b 100644
--- a/doc/arm/reference.rst
+++ b/doc/arm/reference.rst
@@ -1365,6 +1365,9 @@ default is used.
    contact for the zones. These can be set at the view/options
    level but not on a per-prefix basis.
 
+   ``dns64`` will also cause IPV4ONLY.ARPA to be created if not
+   explicitly disabled using ``ipv4only-enable``.
+
    Each ``dns64`` supports an optional ``clients`` ACL that determines
    which clients are affected by this directive. If not defined, it
    defaults to ``any;``.
@@ -1659,6 +1662,12 @@ Boolean Options
    This option was part of an experimental implementation of the EDNS
    CLIENT-SUBNET for authoritative servers, but is now obsolete.
 
+``ipv4only-enable``
+   Create the IPV4ONLY.ARPA zone as described in RFC 8880.  By
+   default the zone is only created if a DNS64 prefix is configured.
+   Control the SOA contact and server values with ``ipv4only-contact``
+   and  ``ipv4only-server`` respectively.
+
 ``root-key-sentinel``
    If ``yes``, respond to root key sentinel probes as described in
    draft-ietf-dnsop-kskroll-sentinel-08. The default is ``yes``.