-@ 86400 IN SOA pdns-public-ns1.powerdns.com. peter\.van\.dijk.powerdns.com. 2025040701 10800 3600 604800 10800
+@ 86400 IN SOA pdns-public-ns1.powerdns.com. peter\.van\.dijk.powerdns.com. 2025040900 10800 3600 604800 10800
@ 3600 IN NS pdns-public-ns1.powerdns.com.
@ 3600 IN NS pdns-public-ns2.powerdns.com.
recursor-5.0.7.security-status 60 IN TXT "3 Upgrade now, see https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2024-04.html"
recursor-5.0.8.security-status 60 IN TXT "3 Upgrade now, see https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2024-04.html"
recursor-5.0.9.security-status 60 IN TXT "1 OK"
+recursor-5.0.10.security-status 60 IN TXT "1 OK"
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.1.1.security-status 60 IN TXT "3 Upgrade now, see https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2024-04.html"
recursor-5.1.2.security-status 60 IN TXT "1 OK"
recursor-5.1.3.security-status 60 IN TXT "1 OK"
+recursor-5.1.5.security-status 60 IN TXT "1 OK"
recursor-5.2.0-alpha1.security-status 60 IN TXT "3 Superseded pre-release (known vulnerabilities)"
recursor-5.2.0-beta1.security-status 60 IN TXT "3 Superseded pre-release (known vulnerabilities)"
recursor-5.2.0-rc1.security-status 60 IN TXT "3 Superseded pre-release (known vulnerabilities)"
recursor-5.2.0.security-status 60 IN TXT "3 Upgrade now, see https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2025-01.html"
recursor-5.2.1.security-status 60 IN TXT "1 OK"
+recursor-5.2.2.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/"
Before upgrading, it is advised to read the :doc:`../upgrade`.
+.. changelog::
+ :version: 5.0.10
+ :released: 9th of April 2025
+
+ .. change::
+ :tags: Improvements
+ :pullreq: 15281
+ :tickets: 15254
+
+ If we see both a CNAME and answer records, follow CNAME and discard the answer records.
+
+ .. change::
+ :tags: Improvements
+ :pullreq: 15214
+ :tickets: 14525
+
+ Add new root trust anchor.
+
.. changelog::
:version: 5.0.9
:released: 3rd of October 2024
Before upgrading, it is advised to read the :doc:`../upgrade`.
+.. changelog::
+ :version: 5.1.4
+ :released: 9th of April 2025
+
+ .. change::
+ :tags: Improvements
+ :pullreq: 15280
+ :tickets: 15254
+
+ If we see both a CNAME and answer records, follow CNAME and discard the answer records.
+
+ .. change::
+ :tags: Improvements
+ :pullreq: 15215
+ :tickets: 14525
+
+ Add new root trust anchor.
+
.. changelog::
:version: 5.1.3
:released: 5th of November 2024
Before upgrading, it is advised to read the :doc:`../upgrade`.
+.. changelog::
+ :version: 5.2.2
+ :released: 9th of April 2025
+
+ .. change::
+ :tags: Improvements
+ :pullreq: 15279
+ :tickets: 15254
+
+ If we see both a CNAME and answer records, follow CNAME and discard the answer records.
+
+ .. change::
+ :tags: Improvements
+ :pullreq: 15212
+ :tickets: 15203
+
+ Switch back to serde_yaml as serde_yml is maintained poorly.
+
+ .. change::
+ :tags: Improvements
+ :pullreq: 15211
+ :tickets: 15072
+
+ Adjust Content-Type header for Prometheus endpoint to include version.
+
+ .. change::
+ :tags: Improvements
+ :pullreq: 15210
+ :tickets: 15063
+
+ Include cstdint to get uint64_t.
+
+ .. change::
+ :tags: Bug Fixes
+ :pullreq: 15209
+ :tickets: 15023
+
+ Remove spurious ] in configure.ac.
+
.. changelog::
:version: 5.2.1
:released: 7th of April 2025