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: ...
This release fixes an issue with security implications that has been recently reported in the HTTP remote backend of the PowerDNS Authoritative Server. Setups that are not using this backend are not impacted by t...
These two releases fix an issue with security implications that has been recently reported in the HTTP remote backend of the PowerDNS Authoritative Server. Setups that are not using this backend are not impacted ...
It has been too long a time since the release of PowerDNS Authoritative Server 4.2.0-alpha1. The Beta 1 release comes with a lot of bug fixes, improvements and also some new features: LMDB backend, Fixes for Open...
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 operational impact when upgrading from 4.1.x. However, several new features have bee...
This release fixes a single issue: the PowerDNS API would accept more than one CNAME record for the same name attribute and would return 204 instead of refusing and returning a 4xx error. The changelog: #7279: Pr...
We’re proud to release the first alpha version of the PowerDNS Authoritative Server 4.2 series. While some users have already deployed this version straight from our package builders or master repositories, this ...
