Prep for rec-4.9.0

diff --git a/docs/secpoll.zone b/docs/secpoll.zone
index eaaaa7b20bcdf5eece156a2c51c2cb355363f879..90cace64d84859e016d54a9eb401efa20d6bb5b0 100644 (file)
--- a/docs/secpoll.zone
+++ b/docs/secpoll.zone
@@ -1,4 +1,4 @@
-@       86400   IN  SOA pdns-public-ns1.powerdns.com. peter\.van\.dijk.powerdns.com. 2023061501 10800 3600 604800 10800
+@       86400   IN  SOA pdns-public-ns1.powerdns.com. peter\.van\.dijk.powerdns.com. 2023063001 10800 3600 604800 10800
 @       3600    IN  NS  pdns-public-ns1.powerdns.com.
 @       3600    IN  NS  pdns-public-ns2.powerdns.com.
 
@@ -330,7 +330,7 @@ recursor-4.6.2.security-status                          60 IN TXT "3 Upgrade now
 recursor-4.6.3.security-status                          60 IN TXT "3 Upgrade now, see https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2023-02.html"
 recursor-4.6.4.security-status                          60 IN TXT "3 Upgrade now, see https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2023-02.html"
 recursor-4.6.5.security-status                          60 IN TXT "3 Upgrade now, see https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2023-02.html"
-recursor-4.6.6.security-status                          60 IN TXT "1 OK"
+recursor-4.6.6.security-status                          60 IN TXT "2 Unsupported release (EOL)"
 recursor-4.7.0-alpha1.security-status                   60 IN TXT "3 Unsupported pre-release (known vulnerabilities)"
 recursor-4.7.0-beta1.security-status                    60 IN TXT "3 Unsupported pre-release (known vulnerabilities)"
 recursor-4.7.0-rc1.security-status                      60 IN TXT "3 Unsupported pre-release (known vulnerabilities)"
@@ -349,9 +349,10 @@ recursor-4.8.1.security-status                          60 IN TXT "3 Upgrade now
 recursor-4.8.2.security-status                          60 IN TXT "3 Upgrade now, see https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2023-02.html"
 recursor-4.8.3.security-status                          60 IN TXT "3 Upgrade now, see https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2023-02.html"
 recursor-4.8.4.security-status                          60 IN TXT "1 OK"
-recursor-4.9.0-alpha1.security-status                   60 IN TXT "1 Unsupported pre-release"
-recursor-4.9.0-beta1.security-status                    60 IN TXT "1 Unsupported pre-release"
-recursor-4.9.0-rc1.security-status                      60 IN TXT "1 Unsupported pre-release"
+recursor-4.9.0-alpha1.security-status                   60 IN TXT "2 Unsupported pre-release"
+recursor-4.9.0-beta1.security-status                    60 IN TXT "2 Unsupported pre-release"
+recursor-4.9.0-rc1.security-status                      60 IN TXT "2 Unsupported pre-release"
+recursor-4.9.0.security-status                          60 IN TXT "1 OK"
 
 ; Recursor Debian
 recursor-3.6.2-2.debian.security-status                 60 IN TXT "3 Upgrade now, see https://doc.powerdns.com/3/security/powerdns-advisory-2015-01/ and https://doc.powerdns.com/3/security/powerdns-advisory-2016-02/"

diff --git a/pdns/recursordist/docs/appendices/EOL.rst b/pdns/recursordist/docs/appendices/EOL.rst
index d4dab6877313a542d7638d81b935930b4130a6f6..e826a14f25340ce5535d205192e0345f30d8e686 100644 (file)
--- a/pdns/recursordist/docs/appendices/EOL.rst
+++ b/pdns/recursordist/docs/appendices/EOL.rst
@@ -10,15 +10,15 @@ The two releases before that get critical updates only.
 Older releases are marked end of life and receive no updates at all.
 Pre-releases do not receive immediate security updates.
 
-The currently supported release train of the PowerDNS Recursor is 4.8.
+The currently supported release train of the PowerDNS Recursor is 4.9.
+
+PowerDNS Recursor 4.8 will only receive critical updates and will be
+end of life after PowerDNS Recursor 4.11 or 5.1 is released.
 
 PowerDNS Recursor 4.7 will only receive critical updates and will be
 end of life after PowerDNS Recursor 4.10 or 5.0 is released.
 
-PowerDNS Recursor 4.6 will only receive critical updates and will be
-end of life after PowerDNS Recursor 4.9 is released.
-
-PowerDNS Recursor 4.0 through 4.5, 3.x, and 2.x are End of Life.
+PowerDNS Recursor 4.0 through 4.6, 3.x, and 2.x are End of Life.
 
 Note: Users with a commercial agreement with PowerDNS.COM BV or Open-Xchange
 can receive extended support for releases which are End Of Life. If you are
@@ -34,9 +34,13 @@ for details.
      - Release date
      - Critical-Only updates
      - End of Life
+   * - 4.9
+     - June 30 2023
+     - ~ December 2023
+     - ~ December 2024
    * - 4.8
      - December 12 2022
-     - ~ June 2023
+     - June 30 2023
      - ~ June 2024
    * - 4.7
      - May 30 2022
@@ -45,7 +49,7 @@ for details.
    * - 4.6
      - December 17 2021
      - May 30 2022
-     - ~ June 2023
+     - EOL June 30 2023
    * - 4.5
      - May 11 2021
      - December 17 2021

diff --git a/pdns/recursordist/docs/changelog/4.9.rst b/pdns/recursordist/docs/changelog/4.9.rst
index e6128ed64d68c780223d596839c97346e8b6ac5c..263fb23579afa766c99b66cab485b2e0e3468841 100644 (file)
--- a/pdns/recursordist/docs/changelog/4.9.rst
+++ b/pdns/recursordist/docs/changelog/4.9.rst
@@ -1,5 +1,30 @@
 Changelogs for 4.9.X
 ====================
+.. changelog::
+  :version: 4.9.0
+  :released: 30th of June 2023
+
+  .. change::
+    :tags: Bug Fixes
+    :pullreq: 12968
+    :tickets: 12963
+
+    Fix qname length getting out-of-sync with qname-minimization iteration count.
+
+  .. change::
+    :tags: Bug Fixes
+    :pullreq: 12936
+    :tickets: 12933
+
+    Rewrite and fix loop that checks if algorithms are available.
+
+  .. change::
+    :tags: Bug Fixes
+    :pullreq: 12932
+    :tickets: 12928
+
+    Fix daemonize() to properly background the process.
+
 .. changelog::
   :version: 4.9.0-rc1
   :released: 15nd of June 2023

diff --git a/pdns/recursordist/docs/performance.rst b/pdns/recursordist/docs/performance.rst
index 5ab0ea07f366b843a8f3e9ad250b2dbcd8fa1b5a..4f5f6e76d15eeac4c8603f8e016f4f2f06bb3726 100644 (file)
--- a/pdns/recursordist/docs/performance.rst
+++ b/pdns/recursordist/docs/performance.rst
@@ -34,6 +34,8 @@ If ``SO_REUSEPORT`` support is available and :ref:`setting-reuseport` is set to
 default since version 4.9.0, separate listening sockets are opened for each worker thread and the query distributions is handled by the kernel, avoiding any thundering herd issue as well as preventing the distributor thread from becoming the bottleneck.
 The next section discusses how to determine if the mechanism is working properly.
 
+.. _worker_imbalance:
+
 Imbalance
 ^^^^^^^^^
 Due to the nature of the distribution method used by the kernel imbalance with the new default settings of :ref:`setting-reuseport` and :ref:`setting-pdns-distributes-queries` may occur if you have very few clients.

diff --git a/pdns/recursordist/docs/upgrade.rst b/pdns/recursordist/docs/upgrade.rst
index 233a6ea95906391fa82c2b801bae9a6e3eaf836f..5f433dd30871b1266343ec7a010bed27c67ad36e 100644 (file)
--- a/pdns/recursordist/docs/upgrade.rst
+++ b/pdns/recursordist/docs/upgrade.rst
@@ -30,9 +30,8 @@ New settings
 Changed settings
 ~~~~~~~~~~~~~~~~
 The first two settings below have effect on the way the recursor distributes queries over threads.
-In some rare cases, this can have negative performance impact.
-In those cases it might be needed to change these settings.
-See :doc:`performance`.
+In some cases, this can lead to imbalance of the number of queries process per thread.
+See :doc:`performance`, in particular the :ref:`worker_imbalance` section.
 
 - The :ref:`setting-pdns-distributes-queries` default has been changed to ``no``.
 - The :ref:`setting-reuseport` default has been changed to ``yes``.