Cross referencing

NLnetLabs · Dec 21, 2021 · ec07c3a · ec07c3a
1 parent f73822a
commit ec07c3a
Show file tree

Hide file tree

Showing 6 changed files with 10 additions and 22 deletions.
diff --git a/source/topics/filtering/rpz.rst b/source/topics/filtering/rpz.rst
@@ -1,7 +1,5 @@
 .. index:: RPZ, Response Policy Zones
 
-.. _doc_filtering_rpz:
-
 .. versionadded:: 1.10.0
     Intial release with QNAME and Response IP Address triggers
 .. versionchanged:: 1.14.0

diff --git a/source/topics/filtering/tags-views.rst b/source/topics/filtering/tags-views.rst
@@ -1,4 +1,3 @@
-.. _doc_filtering_tags_views:
 .. index:: Tags, Views
 
 Tags and Views
@@ -7,15 +6,15 @@ Tags and Views
 The tags and views functionality make it possible to send specific DNS answers
 based on the IP address of the client.
 
+.. Seealso:: :ref:`manpages/unbound.conf:View Options` in 
+             the :doc:`/manpages/unbound.conf` manpage.
+
 Tags
 ----
 
 The tags functionality makes it possible to divide client source addresses
-in categories (tags), and use `local-zone
-<https://nlnetlabs.nl/documentation/unbound/unbound.conf/#local-zone>`_ and
-`local-data
-<https://nlnetlabs.nl/documentation/unbound/unbound.conf/#local-data>`_
-information for these specific tags.
+in categories (tags), and use local-zone and local-data information for these 
+specific tags.
 
 Before these tags can be used, you need to define them in the Unbound
 configuration using *define-tags*. In this example, a tag for domains containing
@@ -100,10 +99,7 @@ space, without having other local-zone elements of subdomains overriding this.
 Configuring a client specific local-zone tree can be done using views.
 
 A view is a named list of configuration options. The supported view
-configuration options are `local-zone
-<https://nlnetlabs.nl/documentation/unbound/unbound.conf/#local-zone>`_ and
-`local-data
-<https://nlnetlabs.nl/documentation/unbound/unbound.conf/#local-data>`_.
+configuration options are local-zone and local-data.
 
 A view is configured using a view clause. There may be multiple view clauses,
 each with a unique name. For example:

diff --git a/source/topics/performance.rst b/source/topics/performance.rst
@@ -1,5 +1,3 @@
-.. _doc_performance:
-
 Performance Tuning
 ==================
 

diff --git a/source/topics/privacy/aggressive-nsec.rst b/source/topics/privacy/aggressive-nsec.rst
@@ -1,7 +1,5 @@
 .. index:: Aggressive NSEC, DNSSEC-Validated cache
 
-.. _doc_privacy_aggressive_nsec:
-
 Aggressive NSEC
 ===============
 

diff --git a/source/topics/privacy/dns-over-https.rst b/source/topics/privacy/dns-over-https.rst
@@ -1,5 +1,3 @@
-.. _doc_privacy_doh:
-
 .. versionadded:: 1.12.0
 
 DNS-over-HTTPS

diff --git a/source/topics/serve-stale.rst b/source/topics/serve-stale.rst
@@ -126,7 +126,7 @@ If more client-side performance is required, the default original serve-expired
 behavior can keep the cache-hit ratio higher. Using it together with the
 prefetch option is highly recommended in order to try and keep an updated cache.
 
-In all cases make sure to consult the :manpage:`unbound.conf(5)` manpage of your
-installed Unbound for defaults and suggested values. And always remember that
-serving expired records should be approached with caution; you may be directing
-your clients to places long gone.
+In all cases make sure to consult the :doc:`/manpages/unbound.conf` manpage of
+your installed Unbound for defaults and suggested values. And always remember
+that serving expired records should be approached with caution; you may be
+directing your clients to places long gone.