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 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.2 and 4.4.4 few days ago. The announcement of these releases looks like this: PowerDNS Recursor 4.4.4 and 4.5.2 Released We are proud to announce the release of PowerDNS Recursor 4.4.4. and 4.5.2. Both releases contain mostly smaller bug fixes. For the 4.5.2 release the default value of nsec3-max-iterations has been lowered to 150, in accordance with new guidelines and in coordination with other vendors. Furthermore, an issue affecting the “refresh almost expired” function has been fixed. Please refer to the change logs for the 4.4.4 and 4.5.2 release for additional details. Please send us all feedback and issues you might have via the mailing list, or in case of a bug, via GitHub. The tarballs (4.4.4, 4.5.2) and signatures (4.4.4, 4.5.2) are available from our download server and packages for several distributions are available from our repository. With the previous 4.5.1 release, the 4.2.x releases will be EOL and the 4.3.x and 4.4.x releases will go into critical fixes only mode. Consult the EOL policy for more details. We would also like to announce that with this release we will stop supporting systems using 32-bit time. This includes 32-bit Linux platforms like arm6, arm7, and i386. 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.