Avoid here

diff --git a/docs/appendices/compiling.rst b/docs/appendices/compiling.rst
index a22f694711089101157bb2fc222cf05f7c525a15..6d165b4a1f52293deb4ea1dea2016f6a7873a80f 100644 (file)
--- a/docs/appendices/compiling.rst
+++ b/docs/appendices/compiling.rst
@@ -26,7 +26,7 @@ There are 3 ways of getting the source.
 
 If you want the bleeding edge, you can clone the `repository at GitHub <https://github.com/PowerDNS/pdns>`__ and run ``autoreconf -vi`` in the clone.
 
-You can also download snapshot tarballs `here <https://downloads.powerdns.com/autobuilt_browser/#/auth>`__.
+You can also download `snapshot tarballs <https://downloads.powerdns.com/autobuilt_browser/#/auth>`__.
 
 You can also download releases on the `website <https://downloads.powerdns.com/releases/>`__.
 These releases are PGP-signed with one of these key-ids:

diff --git a/docs/backends/ldap.rst b/docs/backends/ldap.rst
index 0999c3e9ff7a122287019586c815585f149b684a..46fb40fc2deb7b08ab61726ebf43c6dbb7dc18f3 100644 (file)
--- a/docs/backends/ldap.rst
+++ b/docs/backends/ldap.rst
@@ -499,9 +499,8 @@ If "binddn" is given, the script will prompt for a password, otherwise
 an anonymous bind is executed. The updates in LDIF format are written to
 stdout and can be redirected to a file.
 
-The script requires Perl and the Perl Net::LDAP module and can be
-downloaded
-`here <http://www.linuxnetworks.de/pdnsldap/bind2pdns-ldap>`__.
+The `script <http://www.linuxnetworks.de/pdnsldap/bind2pdns-ldap>`__
+requires Perl and the Perl Net::LDAP module.
 
 Updating the entries in the LDAP tree requires to make the dnsdomain2
 schema known to the LDAP server. Unfortunately, both schemas (dnsdomain2

diff --git a/docs/common/api/endpoint-statistics.rst b/docs/common/api/endpoint-statistics.rst
index 3b3e1e5c827c4b88e354403e0ec2b3c2ed56cf2e..34b21a0e2a59d739b451c03255eedffc996dd075 100644 (file)
--- a/docs/common/api/endpoint-statistics.rst
+++ b/docs/common/api/endpoint-statistics.rst
@@ -6,8 +6,8 @@ Statistics endpoint
   Query PowerDNS internal statistics.
   Returns a list of :json:object:`StatisticItem` elements.
 
-  The names and meaning of these items are described :ref:`here <metricnames>`.
-
+  The :ref:`metricnames <metricnames>` page describes the names and meanings of these items.
+ 
   :param server_id: The name of the server
 
   :query statistic: If set to the name of a specific statistic, only this value is returned. If no statistic with that name exists, the response has a 422 status and an error message

diff --git a/docs/common/secpoll.rst b/docs/common/secpoll.rst
index 48eeb12a598bb9615293dba90cb0178d6f1d500e..5ee7ac1e184e855f227de2ee010a98223efe56af 100644 (file)
--- a/docs/common/secpoll.rst
+++ b/docs/common/secpoll.rst
@@ -8,7 +8,7 @@ By default, security polling happens on the domain 'secpoll.powerdns.com', but t
 If this setting is made empty, no polling will take place.
 Organizations wanting to host their own security zones can do so by changing this setting to a domain name under their control.
 
-To make this easier, the zone used to host secpoll.powerdns.com is available `here <https://github.com/PowerDNS/pdns/blob/master/docs/secpoll.zone>`_.
+To make this easier, the zone used to host secpoll.powerdns.com is `available <https://github.com/PowerDNS/pdns/blob/master/docs/secpoll.zone>`_.
 
 To enable distributors of PowerDNS to signal that they have backported versions, the PACKAGEVERSION compilation-time macro can be used to set a distributor suffix.
 

diff --git a/pdns/dnsdistdist/docs/reference/config.rst b/pdns/dnsdistdist/docs/reference/config.rst
index 5bdea2b712dbbe2ace9f6315a7fc966fbd09f8bc..2d38270a43db31f4dcec08a7637137bf993f23a7 100644 (file)
--- a/pdns/dnsdistdist/docs/reference/config.rst
+++ b/pdns/dnsdistdist/docs/reference/config.rst
@@ -1110,7 +1110,7 @@ Dynamic Blocks
   :param addresses: set of Addresses as returned by an exceed function
   :param string message: The message to show next to the blocks
   :param int seconds: The number of seconds this block to expire
-  :param int action: The action to take when the dynamic block matches, see :ref:`here <DNSAction>`. (default to DNSAction.None, meaning the one set with :func:`setDynBlocksAction` is used)
+  :param int action: The action to take when the dynamic block matches, see :ref:`DNSAction <DNSAction>`. (default to DNSAction.None, meaning the one set with :func:`setDynBlocksAction` is used)
 
   Please see the documentation for :func:`setDynBlocksAction` to confirm which actions are supported by the action paramater.
 
@@ -1207,7 +1207,7 @@ faster than the existing rules.
     :param int seconds: Number of seconds the rate has been exceeded
     :param string reason: The message to show next to the blocks
     :param int blockingTime: The number of seconds this block to expire
-    :param int action: The action to take when the dynamic block matches, see :ref:`here <DNSAction>`. (default to the one set with :func:`setDynBlocksAction`)
+    :param int action: The action to take when the dynamic block matches, see :ref:`DNSAction <DNSAction>`. (default to the one set with :func:`setDynBlocksAction`)
     :param int warningRate: If set to a non-zero value, the rate above which a warning message will be issued and a no-op block inserted
 
   .. method:: DynBlockRulesGroup:setRCodeRate(rcode, rate, seconds, reason, blockingTime [, action [, warningRate]])
@@ -1222,7 +1222,7 @@ faster than the existing rules.
     :param int seconds: Number of seconds the rate has been exceeded
     :param string reason: The message to show next to the blocks
     :param int blockingTime: The number of seconds this block to expire
-    :param int action: The action to take when the dynamic block matches, see :ref:`here <DNSAction>`. (default to the one set with :func:`setDynBlocksAction`)
+    :param int action: The action to take when the dynamic block matches, see :ref:`DNSAction <DNSAction>`. (default to the one set with :func:`setDynBlocksAction`)
     :param int warningRate: If set to a non-zero value, the rate above which a warning message will be issued and a no-op block inserted
 
   .. method:: DynBlockRulesGroup:setRCodeRatio(rcode, ratio, seconds, reason, blockingTime, minimumNumberOfResponses [, action [, warningRate]])
@@ -1237,7 +1237,7 @@ faster than the existing rules.
     :param string reason: The message to show next to the blocks
     :param int blockingTime: The number of seconds this block to expire
     :param int minimumNumberOfResponses: How many total responses is required for this rule to apply
-    :param int action: The action to take when the dynamic block matches, see :ref:`here <DNSAction>`. (default to the one set with :func:`setDynBlocksAction`)
+    :param int action: The action to take when the dynamic block matches, see :ref:`DNSAction <DNSAction>`. (default to the one set with :func:`setDynBlocksAction`)
     :param int warningRatio: If set to a non-zero value, the ratio above which a warning message will be issued and a no-op block inserted
 
   .. method:: DynBlockRulesGroup:setQTypeRate(qtype, rate, seconds, reason, blockingTime [, action [, warningRate]])
@@ -1252,7 +1252,7 @@ faster than the existing rules.
     :param int seconds: Number of seconds the rate has been exceeded
     :param string reason: The message to show next to the blocks
     :param int blockingTime: The number of seconds this block to expire
-    :param int action: The action to take when the dynamic block matches, see :ref:`here <DNSAction>`. (default to the one set with :func:`setDynBlocksAction`)
+    :param int action: The action to take when the dynamic block matches, see :ref:`DNSAction <DNSAction>`. (default to the one set with :func:`setDynBlocksAction`)
     :param int warningRate: If set to a non-zero value, the rate above which a warning message will be issued and a no-op block inserted
 
   .. method:: DynBlockRulesGroup:setResponseByteRate(rate, seconds, reason, blockingTime [, action [, warningRate]])
@@ -1266,7 +1266,7 @@ faster than the existing rules.
     :param int seconds: Number of seconds the rate has been exceeded
     :param string reason: The message to show next to the blocks
     :param int blockingTime: The number of seconds this block to expire
-    :param int action: The action to take when the dynamic block matches, see :ref:`here <DNSAction>`. (default to the one set with :func:`setDynBlocksAction`)
+    :param int action: The action to take when the dynamic block matches, see :ref:`DNSAction <DNSAction>`. (default to the one set with :func:`setDynBlocksAction`)
     :param int warningRate: If set to a non-zero value, the rate above which a warning message will be issued and a no-op block inserted
 
   .. method:: DynBlockRulesGroup:setSuffixMatchRule(seconds, reason, blockingTime, action , visitor)
@@ -1283,7 +1283,7 @@ faster than the existing rules.
     :param int seconds: Number of seconds the rate has been exceeded
     :param string reason: The message to show next to the blocks
     :param int blockingTime: The number of seconds this block to expire
-    :param int action: The action to take when the dynamic block matches, see :ref:`here <DNSAction>`. (default to the one set with :func:`setDynBlocksAction`)
+    :param int action: The action to take when the dynamic block matches, see :ref:`DNSAction <DNSAction>`. (default to the one set with :func:`setDynBlocksAction`)
     :param function visitor: The Lua function to call.
 
   .. method:: DynBlockRulesGroup:setSuffixMatchRuleFFI(seconds, reason, blockingTime, action , visitor)
@@ -1297,7 +1297,7 @@ faster than the existing rules.
     :param int seconds: Number of seconds the rate has been exceeded
     :param string reason: The message to show next to the blocks
     :param int blockingTime: The number of seconds this block to expire
-    :param int action: The action to take when the dynamic block matches, see :ref:`here <DNSAction>`. (default to the one set with :func:`setDynBlocksAction`)
+    :param int action: The action to take when the dynamic block matches, see :ref:`DNSAction <DNSAction>`. (default to the one set with :func:`setDynBlocksAction`)
     :param function visitor: The Lua FFI function to call.
 
   .. method:: DynBlockRulesGroup:apply()

diff --git a/pdns/recursordist/docs/appendices/compiling.rst b/pdns/recursordist/docs/appendices/compiling.rst
index 6158be4d8fb49a03d7abf5297879fcde79fad4fb..15ee104aa41bce8712b939194000c3e23f44aef1 100644 (file)
--- a/pdns/recursordist/docs/appendices/compiling.rst
+++ b/pdns/recursordist/docs/appendices/compiling.rst
@@ -16,7 +16,7 @@ There are 3 ways of getting the source.
 
 If you want the bleeding edge, you can clone the `repository at GitHub <https://github.com/PowerDNS/pdns>`__ and run ``autoreconf -vi`` in the ``pdns/recursordist`` directory of the clone.
 
-You can also download snapshot tarballs `here <https://downloads.powerdns.com/autobuilt_browser/#/recursor>`__.
+You can also download `snapshot tarballs <https://downloads.powerdns.com/autobuilt_browser/#/recursor>`__.
 
 You can also download releases on the `website <https://downloads.powerdns.com/releases/>`__.
 These releases are PGP-signed with one of these key-ids:

diff --git a/pdns/recursordist/docs/changelog/pre-4.0.rst b/pdns/recursordist/docs/changelog/pre-4.0.rst
index adcc7733dfd8fc254b6f6635fb40077aa13f27b3..1b73df39ae8bb474e7f46d700932f4955c298d61 100644 (file)
--- a/pdns/recursordist/docs/changelog/pre-4.0.rst
+++ b/pdns/recursordist/docs/changelog/pre-4.0.rst
@@ -2145,8 +2145,6 @@ offer less than the best in spoofing protection. We urge all operators
 of resolvers without proper spoofing countermeasures to consider
 PowerDNS, as it is a Better Internet Nameserver Daemon.
 
-A good article on DNS spoofing can be found
-`here <http://www.securesphere.net/download/papers/dnsspoof.htm>`__.
 Some more information, based on a previous version of PowerDNS, can be
 found on the `PowerDNS development
 blog <http://blog.netherlabs.nl/articles/2006/04/14/holy-cow-1-3-million-additional-ip-addresses-served-by-powerdns>`__.

diff --git a/pdns/recursordist/docs/getting-started.rst b/pdns/recursordist/docs/getting-started.rst
index 5e00612c7c50f5e4d9cf4ac99501e17e75bf7ed7..aa300e8f3f6ab099b1337f09503f51876679eb24 100644 (file)
--- a/pdns/recursordist/docs/getting-started.rst
+++ b/pdns/recursordist/docs/getting-started.rst
@@ -53,7 +53,7 @@ After a restart of the Recursor, it will answer queries on 192.0.2.25 and 2001:D
 
 The recursor is now ready to be used.
 For more options that can be set in ``recursor.conf`` see the :doc:`list of settings <settings>`.
-Guidance on interaction with the Recursor is documented :doc:`here <running>`
+Guidance on interaction with the Recursor is documented in :doc:`<running>`.
 If dynamic answer generation is needed or policies need to be applied to queries, the :doc:`scripting manual <lua-scripting/index>` will come in handy.
 
 Using Ansible

diff --git a/pdns/recursordist/docs/security-advisories/powerdns-advisory-2014-01.rst b/pdns/recursordist/docs/security-advisories/powerdns-advisory-2014-01.rst
index ae995442614e1fa0f355413272be0c5905ec4c04..ba5974a54aff79048abfc6d503ebbb59d3b0b79d 100644 (file)
--- a/pdns/recursordist/docs/security-advisories/powerdns-advisory-2014-01.rst
+++ b/pdns/recursordist/docs/security-advisories/powerdns-advisory-2014-01.rst
@@ -28,8 +28,8 @@ compromise or stack overflow.
 
 Upgrading to 3.6.1 solves the issue.
 
-In addition, if you want to apply a minimal fix to your own tree, it can
-be found `here <https://xs.powerdns.com/tmp/minipatch-3.6.1>`__
+In addition, you can apply a `minimal fix <https://xs.powerdns.com/tmp/minipatch-3.6.1>`__
+to your own tree.
 
 As for workarounds, only clients in allow-from are able to trigger the
 crash, so this should be limited to your userbase. Secondly,

diff --git a/pdns/recursordist/docs/security-advisories/powerdns-advisory-2014-02.rst b/pdns/recursordist/docs/security-advisories/powerdns-advisory-2014-02.rst
index e7605ca30e80585d52a026d020e69b10b2d63a34..70117f069fcef1da4be210dbc35cd55f86253d23 100644 (file)
--- a/pdns/recursordist/docs/security-advisories/powerdns-advisory-2014-02.rst
+++ b/pdns/recursordist/docs/security-advisories/powerdns-advisory-2014-02.rst
@@ -31,9 +31,8 @@ permission, we continued the 3.6.2 release process with the fix for the
 issue already in there.
 
 We recommend that all users upgrade to 3.6.2 if at all possible.
-Alternatively, if you want to apply a minimal fix to your own tree, it
-can be found `here <https://downloads.powerdns.com/patches/2014-02/>`__,
-including patches for older versions.
+Alternatively, you can apply a `minimal fix <https://downloads.powerdns.com/patches/2014-02/>`__
+(including patches for older versions) to your own tree.
 
 As for workarounds, only clients in allow-from are able to trigger the
 degraded service, so this should be limited to your userbase.