From: Otto Moerbeek <otto.moerbeek@open-xchange.com>
Date: Fri, 3 Nov 2023 09:00:04 +0000 (+0100)
Subject: rec: fix a few yaml examples that still used old syntax
X-Git-Tag: rec-5.1.0-alpha0~31^2~1
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=25ff8de16f4553ea1ffb215d7e12043ce69e377b;p=thirdparty%2Fpdns.git

rec: fix a few yaml examples that still used old syntax
---

diff --git a/pdns/recursordist/settings/table.py b/pdns/recursordist/settings/table.py
index 16fa43c7d0..84f0678b70 100644
--- a/pdns/recursordist/settings/table.py
+++ b/pdns/recursordist/settings/table.py
@@ -424,7 +424,7 @@ These threads cannot be specified in this setting as their thread-ids are left u
         'doc' : '''
 Set CPU affinity for threads, asking the scheduler to run those threads on a single CPU, or a set of CPUs.
 This parameter accepts a space separated list of thread-id=cpu-id, or thread-id=cpu-id-1,cpu-id-2,...,cpu-id-N.
-For example, to make the worker thread 0 run on CPU id 0 and the worker thread 1 on CPUs 1 and 2::
+For example, to make the worker thread 0 run on CPU id 0 and the worker thread 1 on CPUs 1 and 2:
 
 .. code-block:: yaml
 
@@ -482,6 +482,17 @@ This can come in handy on lossy networks when forwarding, where the same server
 By default, the PowerDNS Recursor would throttle the 'first' server on a timeout and hence not retry the 'second' one.
 In this case, ``dont-throttle-netmasks`` could be set to ``192.0.2.1``.
 
+.. warning::
+  Most servers on the internet do not respond for a good reason (overloaded or unreachable), ``dont-throttle-netmasks`` could make this load on the upstream server even higher, resulting in further service degradation.
+ ''',
+        'doc-new' : '''
+When an authoritative server does not answer a query or sends a reply the recursor does not like, it is throttled.
+Any servers matching the supplied netmasks will never be throttled.
+
+This can come in handy on lossy networks when forwarding, where the same server is configured multiple times (e.g. with ``forward_zones_recurse: [ {zone: example.com, forwarders: [ 192.0.2.1, 192.0.2.1 ] } ]``.
+By default, the PowerDNS Recursor would throttle the 'first' server on a timeout and hence not retry the 'second' one.
+In this case, :ref:`setting-dont-throttle-netmasks` could be set to include ``192.0.2.1``.
+
 .. warning::
   Most servers on the internet do not respond for a good reason (overloaded or unreachable), ``dont-throttle-netmasks`` could make this load on the upstream server even higher, resulting in further service degradation.
  ''',
@@ -1195,6 +1206,24 @@ Examples::
   local-address=0.0.0.0:5353
   local-address=[::]:8053
   local-address=127.0.0.1:53, [::1]:5353
+ ''',
+        'doc-new' : '''
+Local IP addresses to which we bind. Each address specified can
+include a port number; if no port is included then the
+:ref:`setting-local-port` port will be used for that address. If a
+port number is specified, it must be separated from the address with a
+':'; for an IPv6 address the address must be enclosed in square
+brackets.
+
+Example:
+
+.. code-block:: yaml
+
+  incoming:
+    listen:
+      - 127.0.0.1
+      - listen: '[::1]:5353'
+      - listen: '::'
  ''',
     },
     {