Available the release of the cache DNS server powerdns recursor 4.7 , responsible for recursive transformation of names. Powerdns Recursor is built on one code base with powerdns authorite server , but recursive and Authoritative DNS servers PowerDNS are developed as part of different development cycles and are produced in the form of individual products. Project code is distributed under the GPLV2 license.
server provides remedy for statistics, supports instant restart, has a built -in engine for connecting handlers In the Lua language, the DNSSEC, DNS64, RPZ (Response Policy Zones) fully supports, it allows you to connect black lists. It is possible to record resolving results in the form of BIND zones. To ensure high performance, modern mechanisms of multiplexing compounds in FreeBSD, Linux and Solaris (Kqueue, Epoll,/DEV/Poll), as well as a high-performance DNS packet Parser capable of processing tens of thousands of parallel query.
are used.
In the new version:
- implemented The ability to add additional records to the client sent answers for useful information without the need to send a separate Requests (for example, to the answers to a request for MX records, you can configure the attachment of related records A and AAAA).
- The requirements of RFC 9156 in the implementation of supporting the Request mechanism (Qname Minimization) were implemented. Confidentiality due to the termination of sending the full original Qname name to a higher server.
- A resolving IPV6 of the addresses of DNS servers not listed in GR (Glue Record) records through which the registrar transmits information about the DNS servers’ domain.
- proposed Experimental implementation of a unilateral support for support for DNS server DOT (DNS Over tls).
- added the possibility of a rollback to the parent recruitment of ns, if servers in the set NS subsidiaries do not answer.
- Added support for checking the correctness of the RR-records of Zonemd ( RFC 8976 ) obtained from the cache.
- added The possibility of attaching the Lua handlers caused by the completion of the resolving (for example , in such handlers, you can change the answer returned to the client).