From: Pieter Lexis <pieter.lexis@powerdns.com>
Date: Thu, 25 Jan 2018 16:22:13 +0000 (+0100)
Subject: docs: squash some warnings
X-Git-Tag: dnsdist-1.3.0~116^2~2
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=d496168926d7bf095407232ce092078f756b3371;p=pdns

docs: squash some warnings
---

diff --git a/pdns/recursordist/docs/changelog/4.1.rst b/pdns/recursordist/docs/changelog/4.1.rst
index 1e06f02fc..4eb33687a 100644
--- a/pdns/recursordist/docs/changelog/4.1.rst
+++ b/pdns/recursordist/docs/changelog/4.1.rst
@@ -9,7 +9,7 @@ Changelogs for 4.1.x
 
   This release fixes PowerDNS Security Advisory :doc:`2018-01 <../security-advisories/powerdns-advisory-2018-01>`.
 
-  The full release notes can be read `on the blog <https://blog.powerdns.com/2018/01/22/powerdns-recursor-4-1-1/>`_.
+  The full release notes can be read `on the blog <https://blog.powerdns.com/2018/01/22/powerdns-recursor-4-1-1/>`__.
 
   This is a release on the stable branch, containing a fix for the
   abovementioned security issue and several bug fixes from the
@@ -76,7 +76,7 @@ Changelogs for 4.1.x
 
   This is the first release in the 4.1 train.
 
-  The full release notes can be read `on the blog <https://blog.powerdns.com/2017/12/04/powerdns-recursor-4-1/>`_.
+  The full release notes can be read `on the blog <https://blog.powerdns.com/2017/12/04/powerdns-recursor-4-1/>`__.
 
   This is a major release containing significant speedups (both in throughput and latency), enhanced capabilities and a highly conformant and robust DNSSEC validation implementation that is ready for heavy production use. In addition, our EDNS Client Subnet implementation now scales effortlessly to networks needing very fine grained scopes (as used by some ‘country sized’ service providers).
 
diff --git a/pdns/recursordist/docs/running.rst b/pdns/recursordist/docs/running.rst
index 3c9e322ac..c386130f9 100644
--- a/pdns/recursordist/docs/running.rst
+++ b/pdns/recursordist/docs/running.rst
@@ -57,7 +57,7 @@ To log only info messages, use ``local0.=info``
 Cache Management
 ----------------
 Sometimes a domain fails to resolve due to an error on the domain owner's end, or records for your own domain have updated and you want your users to immediatly see them without waiting for the TTL to expire.
-The :doc:`rec_control <manpages/rec_control>` tool can be used to selectively wipe the cache.
+The :doc:`rec_control <manpages/rec_control.1>` tool can be used to selectively wipe the cache.
 
 To wipe all records for the exact name 'www.example.com'::
 
@@ -72,7 +72,7 @@ Whole subtrees can we wiped as well, to wipe all cache entries for 'example.com'
   When wiping cache entries, matching entries in *all* caches (packet cache, recursor cache, negative cache) are removed.
 
 When debugging resolving issues, it can be advantagious to have a dump of all the cache entries.
-:doc:`rec_control <manpages/rec_control>` can write the caches of all threads to a file::
+:doc:`rec_control <manpages/rec_control.1>` can write the caches of all threads to a file::
 
   rec_control dump-cache /tmp/cache
 
@@ -89,7 +89,7 @@ To enable tracing for all queries, enable the :ref:`setting-trace` setting.
 
 Tracing can also be enabled at runtime, without restarting the Recursor, for specific domains.
 These specific domains can be specified as a regular expression.
-This can be done using :doc:`rec_control trace-regex <manpages/rec_control>`::
+This can be done using :doc:`rec_control trace-regex <manpages/rec_control.1>`::
 
     rec_control trace-regex '.*\.example.com\.$'