Welcome to the PowerDNS Blog
Second Beta Release of PowerDNS Recursor 4.3.0
Hello! We are proud to announce the second beta release of what should become PowerDNS Recursor 4.3.0. Compared to the first beta release, this release fixes two bugs related to DNSSEC validation. Additionally, a...
First Beta Release of PowerDNS Recursor 4.3.0
Hello! We are proud to announce the first beta release of what should become PowerDNS Recursor 4.3.0. Compared to the third alpha release, this release enables QName-Minimization by default and introduces a less ...
PowerDNS Recursor 4.2.1 Released
This is a maintenance release that fixes a few issues. In particular, a very slow creeping memory leak is plugged and an rare failure to resolve specific names when the dnssec configuration is set to validate has...
PowerDNS Recursor 4.1.15 Released
This is a maintenance release that fixes a few issues. In particular, a very slow creeping memory leak is plugged and an rare failure to resolve specific names when the dnssec configuration is set to validate has...
Third alpha release of PowerDNS Recursor 4.3.0
We’re proud to announce the third alpha release for the PowerDNS Recursor 4.3 release train. Note that a second alpha was tagged, but never released due to an issue found. A few major features are introduced: The...
First alpha release of PowerDNS Recursor 4.3.0
We’re proud to announce the first alpha release for the PowerDNS Recursor 4.3 release train. Two major features are introduced: A relaxed form of QName Minimization as described in rfc7816bis-01 has been implemen...
PowerDNS Recursor 4.2.0 Released
We’re proud to announce version 4.2.0 for the PowerDNS Recursor 4.2 release train. The 4.2.0 release of the PowerDNS Recursor brings a lot of small, incremental changes over the 4.1.x releases. We expect little o...
PowerDNS Recursor 4.2.0 Release Candidate 2
We’re proud to announce Release Candidate 2 for the PowerDNS Recursor 4.2 release train. There have been some minor changes since release candidate 1: #7955: Handle short reads from our random device #7953: Check...