Download PowerDNS Authoritative Server 3.0 rc2

PowerDNS is a dns server with a database as the back end, which makes it easy to manage a large number of dns entries. The developers decided in April 2006 to release the two parts that make up PowerDNS, a recursor and an authoritative name server, separately. This allows new versions to be released faster, according to the developers. The developers have released the second release candidate of PowerDNS Authoritative Server 3.0. The accompanying announcement and list of changes look like this:

PowerDNS Authoritative Server 3.0 Release Candidate 2 available

Hi everybody,

Release Candidate 2 of the PowerDNS Authoritative Server 3.0 is available from:
pdns-3.0-rc2.tar.gz
deb/pdns-static_3.0-rc2-1_i386.deb
deb/pdns-static_3.0-rc2-1_amd64.deb
rpm/pdns-static-3.0rc2-1.i386.rpm
rpm/pdns-static-3.0rc2-1.x86_64.rpm

RC1 received thorough testing by the community, for which we are very grateful! Issues addressed between RC1 and RC2:

• Zone2sql sent out the wrong ‘COMMIT’ statement in sqlite mode. In addition, in this mode, zone2sql would not emit statements to update the domains table unless the ‘slave’ setting was chosen. Code in commit 2167.
• We dropped the Authoritative Answer flag on an out-of-bailiwick CNAME referral, which was unneccessary. Code in commit 2170.
• Kees Monshouwer discovered that we failed to detect the location of PostgreSQL on RHEL/CentOS. Fix in commit 2144. In addition, commit 2162 eases detection of MySQL on RHEL/CentOS 64 bit systems.
• Marc Laros re-reported an old bug in the internally used ‘pdns’ backend where details of the SOA record were not filled out correctly. Resolved in commit 2145.
• Jan-Piet Mens found that our TSIG signed SOA zone fresheness check was signed incorrectly. Fixed in commit 2147. Improved error messages that helped debug this issue in commit 2148, commit 2149.
• Jan-Piet Mens helped debug an issue where some servers were “almost always” unable to transfer a TSIG signed zone correctly. Turns out that the TSIG signing code used an internal timestamp and not the remote timestamp. Because of good NTP synchronization this quite often was not a problem. Fix in commit 2159.
• Thor Spruyt of Telenet discovered that the PowerDNS code would try to emit DNS answers over TCP or over 65535 bytes long, which failed. We now truncate such answers properly. Code in commit 2150.
• The Slave engine now reuses an existing database connection, removing the need to create a new database connection every minute (and worse, log about it). Code in commit 2153.
• Fix a potential Year 2106 bug in the TSIG signing code. Because we care (commit 2156).

Two new features:

• Added experimental support for the ‘DANE’ TLSA record which is used to authenticate SSL certificates via DNSSEC. commit 2161.
• Added experimental support for the MongoDB ‘NoSQL’ backend, contributed by fredrik danerklint in commit 2162.

You are cordially invited to (carefully) test this Release Candidate for correct behaviour. Please study for guidance.

Full release notes, with clickable links, are available from: