This release fixes several bugs and makes a few features more robust or intuitive. It also contains a few performance improvements for API users. Please see the changelog for more details. The tarball (signature)...
PowerDNS Authoritative server 4.2 supports over 15 different backends. While reviewing the existing backends we came to the conclusion that the sheer amount of them holds us back from developing the core of the A...
Hello DNS enthusiasts and other developers, After a successful and packed DNS devroom at FOSDEM 2018 and 2019, we are happy to announce a half-day DNS devroom at FOSDEM 2020. As with the last years, we hope to ho...
Hello everybody! We are very happy to announce the release of Authoritative Server 4.2.0. Besides a ton of bug fixes (please see the Changelog), this release also offers a nice collection of new features. This re...
Thanks to an overwhelming amount of testing by our fabulous user community, this release candidate contains a ton of bug fixes (and a few improvements) compared to the previous one. We hope this has shaken out al...
The 4.1.12 release was skipped due to a packaging issue. This is a bugfix release for high traffic setups using the pipebackend or remotebackend. It contains the following changes: gpgsqlbackend: add missing sche...
Hello, Last Tuesday we published PowerDNS Security Advisory 2019-06, which called for a schema update if you are using PostgreSQL with the Authoritative Server. We have now released updated packages for the 4.0.x...
This maintenance release of the PowerDNS Authoritative Server has the following changes: by popular demand, the option to disable superslave support has been backported from 4.2.0 to 4.1.9 (#7922) pdnsutil b2b-mi...
We are pleased to announce the second Release Candidate for Authoritative Server version 4.2.0. Many of our users have given RC1 a spin, and we very much appreciate their feedback. RC2 contains a host of minor ro...
This release contains a bunch of backports, improvements and bug fixes that we wanted in the 4.1.x release channel after the 4.1.7 security release was out of the door. Please see the changelog for full details: ...
