dns64 docs: document that policy.FORWARD works OK

At least it seems so...

diff --git a/NEWS b/NEWS
index 03bd455aaf423904d6e27deeea15f058bc7f5b77..ff5cabe72a9fd1179e83a95186164012ce512f4c 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -5,7 +5,7 @@ Bugfixes
 --------
 - daemon: check existence of config file even if rundir isn't specified
 - policy.FORWARD and STUB: use RTT tracking to choose servers (#125, #208)
-- dns64: fix CNAME problems (#203)  It still won't work with query policies.
+- dns64: fix CNAME problems (#203)  It still won't work with policy.STUB.
 
 Improvements
 ------------

diff --git a/modules/dns64/README.rst b/modules/dns64/README.rst
index 4eccc99c0cacc9262ff535c2e401651818e5d140..79096dc16c908d45ca56f79307290126c8431870 100644 (file)
--- a/modules/dns64/README.rst
+++ b/modules/dns64/README.rst
@@ -5,7 +5,7 @@ DNS64
 
 The module for :rfc:`6147` DNS64 AAAA-from-A record synthesis, it is used to enable client-server communication between an IPv6-only client and an IPv4-only server. See the well written `introduction`_ in the PowerDNS documentation.
 
-.. warning:: The module currently won't work well with query policies.
+.. warning:: The module currently won't work well with policy.STUB.
 
 .. tip:: The A record sub-requests will be DNSSEC secured, but the synthetic AAAA records can't be. Make sure the last mile between stub and resolver is secure to avoid spoofing.