[Pdns-dev] PowerDNS development plans: 4.x DNSSEC, C++ 2011!
bert.hubert at powerdns.com
Fri Feb 20 08:58:35 CET 2015
In this post, we’d like to share our current plans for .. PowerDNS 4.x! We
are first sharing this with you, the PowerDNS-development community, and
after we’ve gathered your feedback and adjusted our plans, we’ll announce it
on pdns-users, the blog, twitter etc. So please read the following
carefully, and realise now is the time to let us know what you think!
Either reply here, or join the discussion on #powerdns-dev on irc.oftc.net.
The tl;dr: For the next few months we will be spring cleaning git master,
and stable code and releases can be found in the auth-3.4 and recu-3.7
branches. We'll also be moving to C++ 2011. Now read on for the whole
First some background. PowerDNS is a 15 year old software project, and over
these 1.5 decades, we have built up some ‘technical debt’
(http://en.wikipedia.org/wiki/Technical_debt), and it is time for a spring
cleaning in our code.
Meanwhile, we are broadening what our code does, to include for example
smart, DNS-native, load balancing and further denial of service mitigation.
And of course, the major work of bringing carrier-grade DNSSEC to the
Finally, we’ve fallen in love with C++ 2011, and we would like to start
taking advantage of this now 4 year old revision of C++.
All this means some important changes. For one, where it used to be the case
that our git ‘master’ was usually fit to run in production (and people
actually did this), for the coming few months please consider our master
branch a ‘heavy development zone’. While we’ll try to keep things working,
it might break for hours or even days at a time. Even though there will
be somewhat of a wild-west aspect to development, major changes will be
implemented as pull requests from separate branches that can be studied by
Meanwhile, PowerDNS 3.x development and maintenance will continue on
separate release branches. The latest 3.x releases will remain actively
supported until 4.x is more powerful, more stable, and can be compiled on
Debian Stable (more about this later). Active support means more than
passive maintenance, if there are pressing things that need to happen, they
will happen. But the focus for new things will shift to 4.x.
Things we will be addressing during our spring cleaning include:
* We treat DNS names as ASCII strings, which we escape and unescape
repeatedly. DNS names are not ascii strings, and we keep finding
issues related to us treating them like strings.
* The PowerDNS Authoritative Server distributes queries to multiple
* The PowerDNS Recursor cache is both slower and less memory efficient
than it could be
* DNSSEC in the PowerDNS Recursor
* Move our own atomic, locking and semaphore infrastructure to C++ 2011
The somewhat bad news about the spring cleaning is that we’ll come out of it
as a C++ 2011 project, which means that to compile PowerDNS, you’ll need GCC
4.8 (released in March 2013). Gcc 4.8 is not currently the default in
Debian stable or RHEL/CentOS 6. It is the default in RHEL7 and in what will
become the next Debian stable. It also ships in Ubuntu 14. We will also be
targeting clang 3.5. We have chosen C++ 2011 for a variety of reasons, many
of which are described in an earlier blogpost
NOTE: PowerDNS 4.x products WILL run on older distribution releases of
course! However, on older distros, compiling with the system default
compiler may not work.
To clarify, the 4.x branch will not fundamentally alter PowerDNS. This
should not be compared to BIND 9 to BIND 10, for example (or even 8 to 9).
Fundamentally we think the PowerDNS design is sound, it just needs a decent
spring cleaning. This will come in especially handy when deploying our
So how long will it take until 4.x is production ready? We’ll let you know
once we get there, but we are hoping to finish the cleanup in several
months, after which we expect further work to iron out remaining issues. In
any case, 3.x will remain supported until gcc 4.8 is widely available on
currently shipping distributions.
Thanks, and please again let us know your thoughts about this proposed plan.
We’d like to share it more broadly within two weeks, or as soon as we think
the plan is ok.
More information about the Pdns-dev