Software Update: PowerDNS Recursor 4.5.6 / 4.4.6

PowerDNS is a dns server with a database as backend, which makes 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 name server, to allow faster and more targeted release of a new version, the developers said.

When you perform a dns lookup, a recursor initially starts by 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 released PowerDNS Recursor 4.5.6 and 4.4.6 a few days ago. The changes to these releases are as follows:

Version 4.5.6 – Bug Fixes

• Do not use DNSKEYs found below an apex for validation.
• Detect a loop when the denial of the DS comes from the child zone.
• Match ordering of PacketID using the Birthday vs non-Birthday comparator.
• Pass the Lua context to follow up queries (follow CNAME, dns64).
• Only the DNAME records are authoritative in DNAME answers.
• Use the correct RPZ policy name for statistics when loading via XFR.
• Fix the aggressive cache returning duplicated NSEC3 records.
• NS from the cache could be a forwarder, take that into account for throttling decision.
• Check in more places if the policy has been updated before using or modifying it.

Version 4.4.6 – Bug Fixes

• Use the correct RPZ policy name for statistics when loading via XFR.
• NS from the cache could be a forwarder, take that into account for throttling decision.
• Check in more places if the policy has been updated before using or modifying it.