Self-hosted service
poweradmin/poweradmin avatar
poweradmin/poweradmin

Poweradmin's own Dockerfile says it is for testing, and its quick start runs the latest tag

Web UI and REST API for PowerDNS: zones, records, DNSSEC, users, with Terraform and Kubernetes integrations

930 stars299 forksPHPGPL-3.0

At a glance

What is it?
Poweradmin is a web UI and REST API for PowerDNS, drivable through either or both, with API keys, an OpenAPI surface and four automation integrations around it. The parts worth reading closely are architectural: the default backend writes to PowerDNS's own database, the Dockerfile in the repository is marked for testing only, and the support matrix spans eight branches.
Who is it for?
Poweradmin suits an operator who has a PowerDNS authoritative server and wants a familiar web front end plus a scriptable API over the same validation, and who is comfortable with a tool that has direct write access to the DNS database. It does not suit you if you need the API backend or you are on an end-of-support branch, because 4.0.x and 4.1.x receive nothing further and 4.2.x is security updates only.
Can I use it commercially?
Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
Is it still maintained?
Yes. The repository received new commits within the last day.
What is it written in?
Mainly PHP, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • poweradmin/poweradmin930 ★ · +17
Star history
Repository2026-09-122026-11-15
poweradmin/poweradmin913930

17 Stars in the last 64 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The Dockerfile in the repository is marked for testing only

The first thing the file in the repository says about itself is that it is intended only for testing, followed by its own usage comments, the required `DB_TYPE` variable, the default DNS servers, and the note that no admin user is created unless you ask for one. Yet the quick start on the page tells you to run the published image:

bash
docker run -d --name poweradmin -p 8080:80 -e DB_TYPE=sqlite -e PA_CREATE_ADMIN=1 poweradmin/poweradmin:latest

So the build recipe a reader finds in the tree and the image the documentation points at are not the same thing, and the file will not tell you how the published one is produced. What it does show is the base, a FrankenPHP image pinned to php8.4 and locked by digest, and a license label of GPL-3.0-or-later, which is slightly wider than the GPL-3.0 the project page states. It also documents the Docker secrets convention of suffixing a variable name with `__FILE` to read the value from a mounted file.

The default backend writes to the PowerDNS database directly

This is the decision that matters most and it is easy to read past. In the default SQL backend, Poweradmin operates primarily at the database level with PowerDNS, and it uses the PowerDNS API for DNSSEC operations only. So the tool writes rows into your authoritative server's own schema, and the API is consulted for the cryptographic side. The justification offered is that the database schema stays relatively stable between PowerDNS releases, which is why compatibility is described as broad. API backend mode is the alternative: no direct database access at all, with every operation going through the PowerDNS HTTP API instead, and it is what you want if the database is off limits. Since 4.4.0 the interface also detects which PowerDNS version it is connected to and adjusts the available features to match.

The quick start runs latest, the installation note recommends stable

Two sections of the page give different advice about which artefact to run. The quick start uses the latest tag, and it appears twice in slightly different shapes, once on one line and once expanded with line continuations and the same four settings: the container name, port 8080 mapped to 80, `DB_TYPE=sqlite`, and `PA_CREATE_ADMIN=1`. The installation notes recommend the stable Docker tag for production, or the `release/4.3.x` branch, or a specific version tag such as `v4.3.4`. `DB_TYPE` is required, and the reason no admin user is created by default is given as security: with `PA_CREATE_ADMIN=1` a secure password is generated and shown in the container logs, so the logs become a credential you have to protect.

Three releases, three maintenance lines, thirteen seconds apart

The three most recent tags are v4.2.6, v4.3.5 and v4.4.1, and all three were published on 2026-09-04 within about thirteen seconds of each other. That pattern is the signature of a backfill rather than three separate releases: one patch is cut from each of the three maintained lines at the same moment, which is what a project maintaining several branches simultaneously looks like from the outside. The tags also carry the bare version number as both the tag and the release title, with no channel suffix, so nothing in the tag itself tells you which line it came from and only the minor number does. It also means the tag list is not a history of when work happened, it is a snapshot of which lines are still being fed. The most recent push to the default branch was 2026-10-01, so the branches moved after the tags were cut.

Eight branches, two of them finished, one alive until 2027

The support table is unusually long and worth reading before you install anything. `develop` is experimental 4.5.x work and may be unstable, and `master`, which is this repository's default branch, is 4.5.0 development after the develop merge and may also be unstable. That leaves `release/4.4.x` as the current line and still hardening, `release/4.3.x` as the recommended stable line taking patches and security updates, and `release/4.2.x` on security updates only and winding down. `release/4.1.x` and `release/4.0.x` are both marked end of support with no further updates, and both tell you to upgrade to 4.3.x rather than to 4.2.x, which is still alive for security fixes. The `release/3.x` long-term-support line runs until December 2027 on PHP 8.1, while 4.2.x onward requires PHP 8.2 or higher.

The end-to-end matrix is three databases times two backends

The Node manifest is not the application's version, it is the test harness, and it declares 1.0.0 while the project is at 4.4.1. What it does contain is a clean matrix of Playwright entry points, one per database per backend: MySQL, PostgreSQL and SQLite, each in a SQL variant and an API variant, pointed at ports 8080 through 8085 by setting `BASE_URL`. A seventh variant covers a subfolder deployment on 8086 and runs only that subdirectory of tests, which is the case that breaks most reverse-proxy setups. There are separate scripts for the three browser projects, for a headed run, for a debug run and for showing the report, and the API tests are a shell script of their own invoked from a tests directory. The matrix being explicit is the point: six backend combinations is exactly where a DNS admin tool quietly stops working on one database.

The root carries a vendored directory and eight analysis configurations

The tree explains the development setup in one pass. Two directories at the root are unusual for a PHP project: `vendor/`, which means Composer dependencies are committed, and `data/`, which is a runtime path that should not be in a repository at all. Alongside `dynamic_update.php` at the root, those three suggest the tree is also the layout a quick install drops into. Static analysis is layered eight ways, with a `.phan/` directory, three PHPStan files including a baseline and a separate complexity config, a Psalm config, a PHP_CodeSniffer config, a php-cs-fixer config, a phpDocumentor config, a Semgrep ignore and a Hadolint file for the Dockerfile. Two example web server configs sit at the root for Caddy and nginx, `cliff.toml` drives changelog generation, and `transifex.yml` is the source of the 43 translated locales.

Editorial conclusion

Poweradmin suits an operator who has a PowerDNS authoritative server and wants a familiar web front end plus a scriptable API over the same validation, and who is comfortable with a tool that has direct write access to the DNS database. It does not suit you if you need the API backend or you are on an end-of-support branch, because 4.0.x and 4.1.x receive nothing further and 4.2.x is security updates only. Before you install, pick the branch before the tag: the quick start uses the latest image while the page recommends the stable one, the repository's own Dockerfile is marked test-only, and the DNSSEC operations will reach the PowerDNS API even in SQL mode, so that host has to be reachable too.

Frequently asked questions

What is Poweradmin and what does it manage?

It is a DNS administration tool for PowerDNS that can be driven through a web UI, a REST API, or both at once, and can run headless after setup with the same validation on every path. It covers all zone types including master, native and slave, supermasters, zone templates, DNSSEC operations, bulk record and reverse DNS work, and secondary zone import over AXFR.

How does Poweradmin talk to PowerDNS?

In the default SQL backend it operates primarily at the database level and uses the PowerDNS API for DNSSEC operations, which keeps compatibility broad because the database schema changes little between server releases. API backend mode routes every operation through the PowerDNS HTTP API instead, so it needs no direct database access. Since 4.4.0 the interface detects the connected PowerDNS version and adjusts its features.

How do I run Poweradmin in Docker?

With `docker run -d --name poweradmin -p 8080:80 -e DB_TYPE=sqlite -e PA_CREATE_ADMIN=1 poweradmin/poweradmin:latest`. `DB_TYPE` is required and takes sqlite, mysql or pgsql, and no admin user is created unless you set `PA_CREATE_ADMIN=1`, which generates a secure password and prints it in the container logs.

Which Poweradmin branch should I use in production?

The page recommends the `release/4.3.x` branch or the stable Docker tag, and warns that the `master` branch, which is the default branch here, is 4.5.0 development and may be unstable, as is `develop`. `release/4.2.x` receives security updates only, `release/4.1.x` and `release/4.0.x` are end of support, and `release/3.x` is supported until December 2027 on PHP 8.1.

Does the Poweradmin REST API have documentation and scoped keys?

Yes. The REST API ships with OpenAPI documentation, and API keys can be made read-only, restricted to specific operations, or scoped to specific zones. It is exposed in the container with `PA_API_ENABLED=true` and `PA_API_DOCS_ENABLED=true`, and four ready-made integrations wrap it: a Terraform or OpenTofu provider, an ExternalDNS webhook for Kubernetes, a cert-manager DNS-01 solver and a Certbot plugin.

Official sources

  1. License: GPL-3.0
  2. poweradmin/poweradmin on GitHub
  3. Project website
  4. README
  5. Releases
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/poweradmin-poweradmin.svg)](https://hysenlabs.com/projects/poweradmin-poweradmin)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/poweradmin-poweradmin.svg)](https://hysenlabs.com/projects/poweradmin-poweradmin)

Was this useful?