-@ 86400 IN SOA pdns-public-ns1.powerdns.com. peter\.van\.dijk.powerdns.com. 2025082201 10800 3600 604800 10800
+@ 86400 IN SOA pdns-public-ns1.powerdns.com. peter\.van\.dijk.powerdns.com. 2025082802 10800 3600 604800 10800
@ 3600 IN NS pdns-public-ns1.powerdns.com.
@ 3600 IN NS pdns-public-ns2.powerdns.com.
recursor-4.9.6.security-status 60 IN TXT "3 Upgrade now, see https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2024-04.html"
recursor-4.9.7.security-status 60 IN TXT "3 Upgrade now, see https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2024-04.html"
recursor-4.9.8.security-status 60 IN TXT "3 Upgrade now, see https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2024-04.html"
-recursor-4.9.9.security-status 60 IN TXT "1 OK"
+recursor-4.9.9.security-status 60 IN TXT "3 Unsupported release (EOL and known vulnerabilities)"
recursor-5.0.0-alpha1.security-status 60 IN TXT "3 Unsupported pre-release (known vulnerabilities)"
recursor-5.0.0-alpha2.security-status 60 IN TXT "3 Unsupported pre-release (known vulnerabilities)"
recursor-5.0.0-beta1.security-status 60 IN TXT "3 Unsupported pre-release (known vulnerabilities)"
recursor-5.0.9.security-status 60 IN TXT "3 Upgrade now, see https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2025-04.html"
recursor-5.0.10.security-status 60 IN TXT "3 Upgrade now, see https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2025-04.html"
recursor-5.0.11.security-status 60 IN TXT "3 Upgrade now, see https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2025-04.html"
-recursor-5.0.12.security-status 60 IN TXT "1 OK"
+recursor-5.0.12.security-status 60 IN TXT "2 Unsupported release (EOL)"
recursor-5.1.0-alpha1.security-status 60 IN TXT "3 Superseded pre-release (known vulnerabilities)"
recursor-5.1.0-beta1.security-status 60 IN TXT "3 Superseded pre-release (known vulnerabilities)"
recursor-5.1.0-rc1.security-status 60 IN TXT "3 Superseded pre-release (known vulnerabilities)"
recursor-5.3.0-alpha1.security-status 60 IN TXT "3 Superseded pre-release (known vulnerabilities)"
recursor-5.3.0-alpha2.security-status 60 IN TXT "3 Superseded pre-release (known vulnerabilities)"
recursor-5.3.0-beta1.security-status 60 IN TXT "2 Superseded pre-release"
-recursor-5.3.0-rc1.security-status 60 IN TXT "1 Unsupported pre-release"
+recursor-5.3.0-rc1.security-status 60 IN TXT "2 Superseded pre-release"
+recursor-5.3.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://docs.powerdns.com/recursor/appendices/EOL.html"
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 5.2.
+The currently supported release train of the PowerDNS Recursor is 5.3.
-PowerDNS Recursor 5.1 will only receive critical updates and will be End of Life one year after PowerDNS Recursor 5.2 was released.
+PowerDNS Recursor 5.2 will only receive critical updates and will be End of Life one year after PowerDNS Recursor 5.3 was released.
-PowerDNS Recursor 5.0 will only receive critical updates and will be End of Life one year after PowerDNS Recursor 5.1 was released.
+PowerDNS Recursor 5.1 will only receive critical updates and will be End of Life one year after PowerDNS Recursor 5.2 was released.
-PowerDNS Recursor 4.0 through 4.9, 3.x, and 2.x are End of Life.
+PowerDNS Recursor 5.0, 4.x, 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
- Release date
- Critical-Only updates
- End of Life
+ * - 5.3
+ - August 28 2025
+ - ~ February 2026
+ - ~ February 2027
* - 5.2
- January 14 2025
- - ~ July 2025
- - ~ July 2026
+ - August 28 2025
+ - August 28 2026
* - 5.1
- July 10 2024
- January 14 2025
* - 5.0
- January 10 2024
- July 10 2024
- - July 10 2025
+ - EOL July 10 2025
* - 4.9
- June 30 2023
- January 10 2024
Before upgrading, it is advised to read the :doc:`../upgrade`.
+.. changelog::
+ :version: 5.3.0
+ :released: 28th of August 2025
+
+ .. change::
+ :tags: Bug Fixes
+ :pullreq: 16028
+ :tickets: 16010
+
+ Check for pubsuffix.cc presence when building with autotools, followup to #15782.
+
+ .. change::
+ :tags: Improvements
+ :pullreq: 16027
+ :tickets: 16011
+
+ Path.unlink(True) requires python 3.8, rewrite so it works on older versions.
+
+ .. change::
+ :tags: Improvements
+ :pullreq: 16026
+ :tickets: 16021
+
+ Include proper file in bridge.hh to avoid a case of creating a smart pointer to an incomplete class.
+
.. changelog::
:version: 5.3.0-rc1
:released: 21st of August 2025
:tags: Improvements
:pullreq: 15293
- Ddd libcap feature and sync build-and-test-all options with autotools variants.
+ Add libcap feature and sync build-and-test-all options with autotools variants.
.. change::
:tags: Improvements
Reloading ACLs using ``rec_control reload-acls`` now also reloads the proxy-protocol related settings.
The :program:`Recursor` now listens on ``::1`` in addition to ``127.0.0.1`` by default.
+It is not an error if listening on ``::1`` fails.
New Settings
^^^^^^^^^^^^
The :ref:`setting-yaml-recursor.event_trace_enabled` setting has gained a value to allow openTelemetry Trace data to be included in the Protobuf log stream.
-5.0.12, 5.1.6 and 5.2.4
------------------------
+5.0.12, 5.1.6, 5.2.4 and 5.3.0
+------------------------------
New settings
^^^^^^^^^^^^