The release of the authoritative DNS server PowerDNS Authoritative Server 4.6 has been announced, designed for managing DNS zones. According to the project developers, PowerDNS Authoritative Server handles about 30% of all domains in Europe (if considering only domains with DNSSEC signatures, that number rises to 90%). The project's code is distributed under the GPLv2 license.
PowerDNS Authoritative Server provides the capability to store domain information in various databases, including MySQL, PostgreSQL, SQLite3, Oracle, and Microsoft SQL Server, as well as in LDAP and plain text files in BIND format. Answer responses can also be further filtered (for example, to block spam) or redirected using custom handlers in languages such as Lua, Java, Perl, Python, Ruby, C, and C++. Notable features also include tools for remote statistics collection, including via SNMP or through a Web API (with an embedded HTTP server for statistics and management), instant restart, an integrated engine for connecting handlers in Lua, and the ability to balance loads based on the client's geographical location.
Key innovations:
- Support for PROXY protocol headers in incoming requests has been implemented, allowing a load balancer to run in front of the PowerDNS server while preserving the transmission of client IP address information to the load balancer, such as dnsdist.
- Support for the EDNS Cookies mechanism (RFC 7873) has been added, which allows for the verification of correctness an IP address through the exchange of Cookies between the DNS server and the client aimed at protecting against IP address spoofing, DoS attacks, using DNS as a traffic amplifier, and cache poisoning attempts.
- A new interface has been added to the pdnsutil utility and API for managing autoprimary servers, used for automating the deployment and updating of zones on secondary DNS servers without manual configuration of secondary zones. It's sufficient to define a primary zone on the autoprimary server for a new domain, and the secondary servers will automatically pick up and configure a secondary zone for that new domain. servers and configure a secondary zone for it.
Source: opennet.ru
