From: Vladimír Čunát <vladimir.cunat@nic.cz>
Date: Mon, 17 Jul 2017 09:20:44 +0000 (+0200)
Subject: dns64 docs: document that policy.FORWARD works OK
X-Git-Tag: v1.3.2~9^2
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=72c0e3d47a35309e892f355ccb8b8bd99ce8278a;p=thirdparty%2Fknot-resolver.git

dns64 docs: document that policy.FORWARD works OK

At least it seems so...
---

diff --git a/NEWS b/NEWS
index 03bd455aa..ff5cabe72 100644
--- 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 4eccc99c0..79096dc16 100644
--- 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.