summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorTomas Krizek <tomas.krizek@nic.cz>2020-12-11 16:05:30 +0100
committerTomas Krizek <tomas.krizek@nic.cz>2020-12-11 16:05:30 +0100
commitbd1ede4c5bb3cfc2d48127acf46b1b18b72044b7 (patch)
tree766431c7e6696f6a041470d48b72c17426ae9ecb /doc
parentdoc: use :any: to refer to non-function policies (diff)
downloadknot-resolver-bd1ede4c5bb3cfc2d48127acf46b1b18b72044b7.tar.xz
knot-resolver-bd1ede4c5bb3cfc2d48127acf46b1b18b72044b7.zip
doc: make links to policies more consistent
Diffstat (limited to 'doc')
-rw-r--r--doc/config-network-forwarding.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/config-network-forwarding.rst b/doc/config-network-forwarding.rst
index f16b48fe..ea00d604 100644
--- a/doc/config-network-forwarding.rst
+++ b/doc/config-network-forwarding.rst
@@ -14,7 +14,7 @@ Main use-cases are:
Forwarding implementation in Knot Resolver has following properties:
- Answers from *upstream* servers are cached.
- - Answers from *upstream* servers are locally DNSSEC-validated, unless ``policy.STUB`` is used.
+ - Answers from *upstream* servers are locally DNSSEC-validated, unless :func:`policy.STUB` is used.
- Resolver automatically selects which IP address from given set of IP addresses will be used (based on performance characteristics).
- Forwarding can use either unencrypted DNS protocol, or :ref:`tls-forwarding`.