Download PowerDNS Recursor 4.7.4 / 4.6.5 / 4.5.12

PowerDNS is a DNS server with a database as the backend, making it easy to manage a large number of DNS entries. The developers have previously decided to release the two parts that make up PowerDNS, a recursor and an authoritative nameserver, separately, so that a new version can be released faster and more targeted, according to the developers.

When you perform a DNS lookup, a recursor initially starts by asking the lookup query to a DNS root server. It can then redirect to other servers, from where it can redirect to other servers and so on, until finally a server is reached that knows the answer or knows that the look-up is not possible. The latter can be the case if the name does not exist or the servers do not respond. The process of traversing several authoritative servers is called recursion. The developers have released PowerDNS Recursor 4.5.12, 4.6.5 and 4.7.4 with the following announcement:

PowerDNS Recursor 4.5.12, 4.6.5 and 4.7.4 Released

Hello,

Today we have released a maintenance release of PowerDNS Recursor 4.5.12, 4.6.5 and 4.7.4, containing fixes for a few minor issues. In particular, RPZ IXFRs now time out if the server becomes unresponsive. For more details on the other fixes, consult the changelogs available at 4.5.12, 4.6.5, 4.7.4.

The source tarballs (4.5.12, 4.6.5, 4.7.4) and signatures (4.5.12, 4.6.5, 4.7.4) are available from our download server. Packages for various distributions are available from our repository.

Note that PowerDNS Recursor 4.4.x and older releases are End of Life. Consult the EOL policy for more details.

We would also like to repeat that starting with the 4.5 release branch we stopped supporting systems using 32-bit time. This includes most 32-bit Linux platforms.

We are grateful to the PowerDNS community for the reporting of bugs, issues, feature requests, and especially to the submitters of fixes and implementations of features.

Please send us all feedback and issues you might have via the mailing list, or in case of a bug, via GitHub.