Software Update: PowerDNS Recursor 4.1.13

PowerDNS is a dns server with a database as backend, which makes it easy to manage a large number of dns entries. The developers previously decided to release the two parts that make up PowerDNS, a recursor and an authoritative name server, to make a new version faster and more targeted, the developers said.

When you perform a dns lookup, a recursor initially starts asking the lookup query to a dns root server. This 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 going through different authoritative servers is called recursion. The developers have released PowerDNS Recursor 4.1.13. The changes in this release are as follows:

PowerDNS Recursor 4.1.13 Released

This is a maintenance release to optionally reduce the performance impact of memory-statistics collection and a fix in the DNSSEC processing of wildcard records.

The change log:

• #7673: Add the disable-real-memory-usage setting to skip expensive collection of detailed memory usage info,
• #7816: Fix DNSSEC validation of wildcards expanded onto themselves.

The tarball (signature) is available at downloads.powerdns.com and packages for CentOS 6 and 7, Debian Jessie and Stretch, Ubuntu Trusty, Xenial and Bionic 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.

PowerDNS Recursor 4.1.12 Released

This is a maintenance release with improvements for high-performance sites (and a wild bug fix appeared).

The change log:

• #7634: Use a bounded load-balancing algo to distribute queries.
• #7651: Implement a configurable ECS cache limit so responses with an ECS scope more specific than a certain threshold and a TTL smaller than a specific threshold are not inserted into the records cache at all.
• #7647: Provide CPU usage statistics per thread (worker & distributor).
• #7495: Correctly interpret an empty AXFR response to an IXFR query.