PowerDNS Authoritative Server 4.1.0 Release Candidate 3 Available

We present what should be our last release candidate for PowerDNS Authoritative Server 4.1.0: Release Candidate 3!

If no major issues are found we expect to release the final version within the next two weeks.

Thanks to everyone who tested the previous release candidates.

This release features various bug fixes, some improvements to pdnsutil, documentation improvements by Christian Hofstaedtler and logging message improvements by Job Snijders.

The Raspbian packages will follow Monday since the builder is still working on them.

The full changelog looks like this:

New Features

  • #5936: Make it possible to disable DNSSEC via the API, this is equivalent to doing pdnsutil disable-dnssec.
  • #5883: Add add-meta command to pdnsutil that can be used to append to existing metadata without clobbering it.


  • #5616: Better support for deleting entries in NetmaskTree and NetmaskGroup.
  • #5935: Throw exception for metadata endpoint with wrong zone. Before, We would happily accept this POST.
  • #5879: Warn if records in a zone are occluded.

Bug Fixes

  • #5917: Use _exit() when we really really want to exit, for example after a fatal error. This stops us dying while we die. A call to exit() will trigger destructors, which may paradoxically stop the process from exiting, taking down only one thread, but harming the rest of the process.
  • #5884: Fix messages created by pdnsutil generate-tsig-key.
  • #5928: Add back missing output details to rectifyZone.
  • #5905: Use 302 redirects in the webserver for ringbuffer reset or resize. With the current 301 redirect it is only possible to reset or resize once. Every next duplicate action is replaced by the destination cached in the browser.

The tarball is available on downloads.powerdns.com (signature) and packages for CentOS 6 and 7, Debian Jessie and Stretch, Ubuntu Artful, Trusty, Xenial and Zesty are available from repo.powerdns.com. (The Raspbian packages will come later, possibly Monday, because they are still building.)

We invite you to test this release candidate and send us all feedback and issues you might have via the mailinglist, or in case of a bug, via GitHub.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s