PowerDNS daemon 2.9.20 review

PowerDNS daemon Nameserver is a advanced, modern and high performance authoritative-only nameserver. It is written from scratch an

License: GPL (GNU General Public License) File size: 2751K Developer: PowerDNS.COM BV

0

PowerDNS daemon Nameserver is a advanced, modern and high performance authoritative-only nameserver.

It is written from scratch and conforms to all relevant DNS standards documents. Furthermore, PowerDNS interfaces with almost any database.

The PowerDNS Nameserver utilizes, a flexible backend architecture can access DNS information from any data source. This includes file formats, Bind zone files, relational databases or LDAP directories.

If you have specific needs for your DNS infrastructure then you can use the Backend Developers Kit to write the 'glue' between PowerDNS and your data or logic.

There is one master database that is replicated to two slave databases. The slave databases are read-only and are updated immediately when the master database changes.

For sites that do not yet have an existing database infrastructure we recommend the MySQL database. MySQL is very easy to setup and handles replication well.

If your nameservers are located on different physical networks then you immediately take advantage of the distributed nature of DNS. Questions will be load balanced on your array of servers. If a server is down then one of the other servers is queried.

PowerDNS is by default configured to serve all information directly from a database, which results in unmatched maintainability of your DNS information.

PowerDNS has developed a complete suite of technologies surrounding Internet Naming and email. Internet Naming is at the core of all online activities and is involved in each and every transaction on the net. Email remains the killer application of the Internet.

What's New in This Release:
This release adds a contributed OpenDBX backend with high-end features like failover and load balancing.
An order of magnitude speed increase in the recursor was attained by properly indexing the caches for cleanup and optimizing many operations.
Several major bugs were fixed, including some that could make two common forms of in-addr.arpa delegations fail.
Upgrading is highly recommended.