PowerDNS Blog

Second Release Candidate of PowerDNS Recursor 4.4.0 | PowerDNS Blog

Written by Otto Moerbeek | Oct 6, 2020 4:00:00 AM

Hello!

We are proud to announce the second release candidate of what should become PowerDNS Recursor 4.4.0.

Compared to the first release candidate, this release contains a few enhancements and fixes a few bugs. In particular, DS records of forwarded zones are handles properly and the parsing of unknown record types has been made more strict. Note that the recursor only parses these types if read from a zone file.

Please refer to the changelog for details.

Compared to the 4.3 release of PowerDNS Recursor, this release contains these major enhancements:

  • Native DNS64 support, without the need to use Lua.
  • The ability to add custom tags to RPZ hits.
  • Names encountered while resolving CNAMEs are now subject to RPZ processing.
  • More detailed information about RPZ handling is now available while tracing, in Lua and in the protobuf logging messages.
  • To allow more efficient use, the record cache is now shared between threads.
  • A routing tag can be added in Lua code, which will be used as an additional record cache key instead of of an EDNS subnet mask, enabling for a simpler record cache structure which will enhance query processing where the EDNS subnet mask is relevant.
  • The Proxy Protocol version 2 has been implemented to allow for a structured exchange of information between a client (typically dnsdist) and the Recursor. See the documentation for details.

We are grateful to all reporters of bugs, issues, feature requests, and submitters of fixes and features. We also like to thank anybody who tested the pre-releases, and invite you to contribute to the testing of this release candidate!

The tarball (signature) is available at downloads.powerdns.com and packages for CentOS 7 and 8, Debian Stretch and Buster, Ubuntu Xenial, Bionic and Focal are available from repo.powerdns.com.

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