PowerDNS: Authoritative Server, Recursor, and dnsdist
PowerDNS is a C++ repository that builds three separate DNS programs: the Authoritative Server, the Recursor, and the dnsdist load balancer. The Authoritative Server reads zone data from backends like BIND files, MySQL, or PostgreSQL instead of one fixed format. Reach for it if your DNS records already live in a database; skip it if you want a resolver with nothing to configure.
Understanding PowerDNS Components
PowerDNS is the name for a repository containing three related programs: the PowerDNS Authoritative Server, the PowerDNS Recursor, and dnsdist. The Authoritative Server serves DNS zones through swappable backends, with bind and gmysql compiled in by default and options like gpgsql or geoip added via the --with-modules configure flag.
Core Capabilities and Modularity
- ✓One repository builds three programs: the Authoritative Server, the Recursor, and dnsdist; outside this repo, each is also shipped on its own as a .deb, .rpm, or .tar.bz2 package.
- ✓Backend choice is a compile-time flag: bind and gmysql build in by default when --with-modules is left unset, and gpgsql, geoip, and others are added by naming them explicitly.
- ✓DNSSEC coverage includes ed25519 (algorithm 15), which the README says needs the --with-libsodium build option.
- ✓A docker-based build tool called pdns-builder runs via ./builder/build.sh after git submodule init and update, and prints a USAGE page with build instructions for each release.
- ✓The Recursor and dnsdist each keep their own README, under pdns/recursordist/ and pdns/dnsdistdist/, separate from the top-level build notes.
- ✓HTML documentation is generated with Sphinx from ReStructured Text files in docs/, run with make html-docs.
Building and Installing PowerDNS
Compiling the Authoritative Server needs Boost, OpenSSL, and Lua plus a compiler with C++17 support. On Debian, apt install covers g++, libboost-all-dev, libtool, default-libmysqlclient-dev, libssl-dev, and libluajit-5.1-dev, with autoconf, automake, ragel, bison, and flex added when building from git. Ubuntu needs a longer package list plus, depending on which backend you want, libsodium-dev for DNSSEC ed25519, libpq-dev for the gpgsql backend, or libmaxminddb-dev for geoip. Run autoreconf -vi to generate configure, then ./configure --with-modules="" --disable-lua-records && make for a minimal binary with no backend modules, or list modules explicitly like ./configure --with-modules="bind gmysql gpgsql". FreeBSD needs gmake instead of make, plus CXXFLAGS=-std=c++17. On macOS, brew install pdns gets you a prebuilt Authoritative Server, or compile it yourself after brew install boost lua pkg-config ragel openssl.
Strengths
- ✓One repository builds three separate DNS programs: the Authoritative Server, the Recursor, and dnsdist; each is also distributed on its own as a .deb, .rpm, or .tar.bz2 package.
- ✓Backend choice is a compile-time flag rather than a fork: bind, gmysql, gpgsql, and geoip are all named options for --with-modules.
- ✓DNSSEC support names specific algorithms, like ed25519 (algorithm 15), instead of leaving cryptographic coverage vague.
- ✓macOS users get a Homebrew package, brew install pdns, instead of only a from-source build.
- ✓The repository carries the hacktoberfest topic and a public issue tracker on GitHub, so the contribution path is visible.
Considerations for PowerDNS Deployment
- △Building from source pulls in a long dependency list, Boost, OpenSSL, Lua, and per-backend extras like libsodium-dev or libpq-dev, so a fully-loaded binary takes more than one command.
- △The top-level README says it can lag behind and points to doc.powerdns.com for the current changelog and compiling guide, so this file alone isn't the whole story.
- △Windows isn't mentioned in the build notes at all; only Linux (Debian/Ubuntu), FreeBSD, and macOS are covered.
- △The Recursor and dnsdist ship their own separate READMEs rather than being documented in the main one, so their build steps aren't visible from the top level.
- △No version number, release date, or roadmap appears in the facts available here, so there's nothing to gauge release cadence against.
Other DNS Server Options
Frequently Asked Questions about PowerDNS
PowerDNS is licensed under the GNU GPLv2, copyright PowerDNS.COM BV and contributors; the repository's NOTICE file spells out the specific license terms and exception in force, and GitHub lists it as GPL-2.0.
The PowerDNS repository contains three components: the PowerDNS Authoritative Server, the PowerDNS Recursor, and dnsdist, a DNS load balancer. A single checkout compiles all three, or you can install each one separately as its own package.
Compiling the PowerDNS Authoritative Server requires Boost, OpenSSL, and Lua plus a C++17 compiler; after installing dependencies, run autoreconf -vi, then ./configure with your chosen --with-modules list, followed by make.
PowerDNS documentation lives at doc.powerdns.com, with the Authoritative Server's changelog and compiling guide each linked from the repository's own README.
PowerDNS supports DNSSEC; the README specifically notes that ed25519 (algorithm 15) support requires building with the --with-libsodium configure option.
On macOS, Homebrew carries the Authoritative Server directly, so brew install pdns is enough, or it can be compiled manually after installing boost, lua, pkg-config, ragel, and openssl via Homebrew.
The problem it solves
Running your own DNS zones usually means picking between a resolver-style server tuned for caching lookups and a database-backed system that can generate records from application data. PowerDNS's Authoritative Server addresses the second case directly: it reads zone data out of MySQL, PostgreSQL, or BIND-style files through swappable backends chosen at compile time, instead of forcing every record into one static zone file format.
Best use cases
- •Hosting authoritative zones for a domain where records need to come from a database your application already writes to, using the gmysql or gpgsql backend instead of hand-edited zone files.
- •Running a DNS load balancer in front of other DNS servers with dnsdist, built from the same repository as the Authoritative Server and Recursor.
- •Standing up a resolver via the PowerDNS Recursor component, built separately with its own README under pdns/recursordist/.
- •Building a stripped-down Authoritative Server binary with no backend modules compiled in, using ./configure --with-modules="" --disable-lua-records, for a minimal footprint.
- •Installing on macOS through Homebrew (brew install pdns) for local testing of authoritative DNS setups without a full compile.
Who should try it — and who should skip
Try PowerDNS's Authoritative Server if you're already storing DNS records in PostgreSQL or MySQL and want zone data pulled from there instead of maintained by hand. It's also worth a look if you want dnsdist for load balancing in front of your DNS infrastructure. Skip it if you just want a caching resolver: that's the Recursor's job here, or reach for Unbound if you'd rather not deal with PowerDNS's own build process at all.
Related repositories
Is pdns worth your time?
ChatGPT, Claude and Perplexity can all read this page. Ask one of them what it makes of pdns.
