Poweradmin 4.1.1 & 4.0.7
patch releases, branch cleanup, and what's coming
Two patch releases went out this week. Nothing dramatic, just fixes I wanted to get out before moving on to bigger things.
🛠️ 4.1.1
This is a bugfix release for the 4.1.x line. Changes since v4.1.0:
#994 - DNSSEC wasn’t working for RFC 2317 classless reverse DNS domains. Zone names with slashes weren’t being URL-encoded in PowerDNS API calls.
#993 - 404 on
/loginin 4.1.0. Routing issue that showed up right after the release.#992 - IPv6 addresses were rejected when editing or deleting supermasters. The validation was too strict.
#991 - LUA record verification was failing. Records with a type prefix and explicit return mode weren’t handled correctly.
🔒 CSRF token fix in PowerDNS status forms - the field was named
csrf_tokeninstead of_token. Also added a CI check so this doesn’t happen again.✨ Wizard link added to the zone edit toolbar.
🌍 Zone apex (
@) symbol was not resolved to the zone name when adding multiple records at once. Entering@as the record name resulted in@.example.cominstead ofexample.com. Backported to all active branches.
🛠️ 4.0.7
Maintenance release for the 4.0.x line. Changes since v4.0.6:
#995 - Invalid CSRF token when deleting a DNSSEC key. Same
_tokenfield name issue as in 4.1.x, but affecting different forms. Added a CI check to catch this going forward.#985 - MFA setup was reusing old TOTP secrets instead of generating fresh ones. If you tried to set up app-based MFA and the first attempt failed, retrying would use the same secret, which could cause verification errors.
#992 - IPv6 addresses were rejected when editing or deleting supermasters, backported from 4.1.1.
#991 - LUA record handling fix for records with type prefix and explicit return mode, backported from 4.1.1.
🌍 Zone apex (
@) symbol fix in multi-record add form, backported from 4.1.x.
🌿 The release/4.x branch is gone
I’ve been maintaining separate release/4.0.x and release/4.1.x branches for a while now, and the old release/4.x branch is no longer needed. If you were tracking it, switch to one of:
release/4.0.x- backported bug fixes and security patches only, no new featuresrelease/4.1.x- current stable release line, bug fixes and minor improvements
⚠️ Heads up if you’re tracking master
I’ll be merging the develop branch into master soon. This includes groups support and a bunch of other features that have been in the works for a while. Things will likely be unstable for a bit during that transition. If you’re running off master in production (I know some of you do), I’d recommend switching to release/4.1.x before that happens.
🐳 Docker tags
Here’s how Docker image tags map to branches, for reference:
stable→release/4.0.x- Conservative, production-safenext→release/4.1.x- Latest stable featureslatest→master- Will become unstable soon - switch tonextorstablelts→release/3.x- Legacy, security fixes onlydev→develop- Experimental, not for production
Version-pinned tags like v4.1.1 and v4.0.7 are also available if you prefer locking to a specific release.
Images are published to both Docker Hub (poweradmin/poweradmin) and GitHub Container Registry (ghcr.io/poweradmin/poweradmin).
As always, bug reports and feedback go to GitHub.