📣 Update: please use v4.3.1 instead of v4.3.0. Shortly after release, the community flagged two issues - a broken MySQL backfill query in the 4.3.0 upgrade script (#1159) and a missing-config error that wasn’t surfaced clearly (#1158). Huge thanks for the quick reports - both are fixed in v4.3.1. If you’ve already upgraded and the MySQL migration failed, re-run sql/poweradmin-mysql-update-to-4.3.0.sql from the v4.3.1 release.

Prefer to stay on the stable line? v4.2.2 remains the recommended release for production deployments that don’t need API backend mode or the other 4.3 features. It’s what the Docker stable tag points at, and it continues to receive bug and security fixes.

⚠️ Before upgrading: md5 and md5salt password hashing is no longer supported for new hashes. Existing hashes still validate, so current users can still log in. If your config has password_encryption set to md5 or md5salt, switch it to bcrypt before upgrading. Also: run the database migration script for your database before starting v4.3.0.

🌐 API backend mode

Poweradmin can now run in front of PowerDNS without direct access to its database. All DNS operations go through the PowerDNS HTTP API instead. This helps when the PowerDNS database is on a network you cannot reach, when PowerDNS is a managed or cloud service, or when you prefer API-first integration (#658).

How to enable it. New installs get a backend choice in the installer (”Database” or “API”). For existing installs, set dns.backend to api in config/settings.php and add your PowerDNS API URL and key:

return [
    'dns' => [
        'backend' => 'api',
        // ...
    ],
    'pdns_api' => [
        'url' => 'http://powerdns-server:8081',
        'key' => 'YOUR_API_KEY',
        'server_name' => 'localhost',
    ],
];

Both pdns_api.url and pdns_api.key are required - Poweradmin will refuse to run in API mode without them. In Docker, set PA_PDNS_BACKEND=api along with the API URL and key env vars.

Migration. Run the v4.3.0 database migration, add the pdns_api config, then switch dns.backend from sql to api. Your existing zone ownership, groups, and permissions are preserved. You can also revert by setting dns.backend back to sql. Full steps are in the upgrading guide and PowerDNS API configuration docs.

This mode needs community testing. It is a big change that affects how Poweradmin reads and writes data. I ran smoke tests, but there are many zone types, record types, permissions, and edge cases, so I cannot promise every case is covered. Big changes like this often have rough spots that only show up in real use. Please do not switch to API mode in production before trying it on a separate test instance, ideally with test data or a copy of your zones. Try the features you use most. If you find anything wrong, file an issue on GitHub with steps to reproduce it - community reports are the fastest way to make this stable.

Expect some slowdown. Every read and write in API mode makes one or more HTTP calls to PowerDNS, instead of a single SQL query. Pages that load many zones or records (dashboard, search, bulk operations) will be slower because they depend on PowerDNS API response time. Classic SQL mode is unchanged and still the default - only switch if you have a reason to.

📁 Zone metadata editor

A first-class editor for PowerDNS domainmetadata (#1117). Select from known kinds with inline guidance, enter custom kinds when needed, and manage multi-value kinds such as ALLOW-AXFR-FROM one row at a time. A read-only view is available for users without edit rights. Full API v2 CRUD is available at /v2/zones/{id}/metadata. SOA-EDIT-API is handled specially in API mode - surfaced from zone properties, editable inline, and removal propagated correctly.

📊 Audit logging and log pages

The AuditService now records structured events across user management, zone ownership, templates, DNSSEC, MFA, API keys, OIDC/SAML authentication (#1109), failed permission checks, and all API v2 operations. Every log page has been upgraded with filters (operation/event type, user, group, date range), CSV and JSON export with confirmation modal, a details modal with one-click copy, and client IP + auth method visible across all views. A dedicated API Logs page surfaces API-key events.

🔐 SSO permission template mapping

Running Poweradmin behind OIDC or SAML becomes easier:

• Permission template source tracked per user so external identity provider changes can revoke stale SSO mappings (#1095)

• New env vars for SSO permission template and group mappings (#1091)

• default_permission_template only applies to new SSO users, leaving existing users untouched (#1092)

• auth_method preserved when editing OIDC/SAML users (#1064)

🐳 Docker

• PA_PDNS_BACKEND selects SQL or API mode

• PA_TRUSTED_CA_FILE mounts custom CA certificates (#1065)

• PA_TRUSTED_PROXIES for real client IP behind reverse proxies (#1134)

• Env var support for module configuration (#1084)

• dns_wizards and email_previews togglable via env vars (#1116)

• Rootless container mode; port 80 binding restored in root mode (#1118)

🌍 DNS & content

• Custom TLD-to-server mapping for WHOIS and RDAP, with .za added (#1138)

• IDN/punycode support for record names and content, incl. HTTPS, SVCB, and LP (#1090)

• IPv6 batch PTR with correct nibble expansion (#1110)

• Selective zone template update instead of full replace

🛡️ Security hardening

• md5 and md5salt hashing removed for new passwords (existing hashes still validate)

• Default bcrypt cost bumped to 12

• CSRF validation required for API key toggle

• IpAddressRetriever hardened - X-Real-IP support, proxy headers matching REMOTE_ADDR skipped, parsing bugs fixed (#1134)

• API v1 formally deprecated with Sunset date announced via header and OpenAPI notice (#1146) - please migrate to v2

✨ Small touches

• Globe language switcher on the login page

• disabled field respected in bulk record CSV import

• Details modal with copy across log views

📦 Upgrading

• Back up your database before upgrading - 4.3.0 adds audit log tables and introduces the zone metadata schema

• Run the database migration for your database type before starting the new version:

  • sql/poweradmin-mysql-update-to-4.3.0.sql

  • sql/poweradmin-pgsql-update-to-4.3.0.sql

  • sql/poweradmin-sqlite-update-to-4.3.0.sql

• PHP 8.2+ required (unchanged); tested on 8.2 through 8.5

• PowerDNS 4.0+ through 5.x works as before; API backend mode requires the PowerDNS HTTP API enabled

• Docker: poweradmin/poweradmin:4.3.1 (or :4.3 for automatic patch updates). The stable tag still tracks the 4.2.x series (currently 4.2.2) - opt in to 4.3.x explicitly

• Full step-by-step guide in the v4.3.0 upgrading docs

Thanks to everyone who filed issues, tested, and contributed.

I’m consolidating the number of active branches. Maintaining four release branches (3.x, 4.0.x, 4.1.x, master) meant a lot of backporting overhead for a one-person project. Going forward, there’s one stable release branch, one development branch, and the 3.x LTS. The release/4.0.x and release/4.1.x branches will remain available for reference but won’t receive new releases.

I’m still iterating on the release process, so apologies if the Docker tags and branch structure have been a moving target lately. The goal is to keep things simple and predictable - I think we’re getting closer.

4.2.1

Bugfix release from master. Changes since v4.2.0:

• #1129 - SOA serial numbers weren’t reflecting local time. Timezone initialization was happening too late in the bootstrap process.

• #1122 - SOA serial was incrementing by 2 instead of 1 when adding a record inline. A duplicate increment call was being triggered.

• #1121 - Search was failing on PostgreSQL with a GROUP BY error (SQLSTATE[42803]). Switched to SQL standard GROUP BY with aggregates.

• #1118 - Docker container wouldn’t start due to port 80 binding errors. Restored port binding capability in root mode.

• #1116 - Docker entrypoint wasn’t setting env vars for DNS Wizards and Email Previews modules.

• #1113 - DNS Wizard button was missing from the zone edit toolbar. The module config was also missing its enabled key.

• #1112 - Users couldn’t access zones if they had group membership but no direct ownership. The zone listing query now checks both direct and group ownership.

• #1110 - IPv6 was disabled in the batch PTR form. Fixed the form and also corrected broken nibble expansion.

• #1109 - OIDC and SAML login events weren’t being logged to the database. Added database logging for SSO authentication.

• #1106 - TXT record validation errors weren’t shown on the add record page. The error was being swallowed silently.

• #1105 - Search was crashing with a SQL error and null type exception.

• #1104 - Matching record creation was broken since 4.1.1. Two issues: multi-record mode wasn’t triggering it at all, and forward zone lookup failed for subdomain zones.

• #1090 - IDN (punycode) support extended to record names and content, including HTTPS, SVCB, and LP record types.

• #1047 - Pagination and letter filter links in zone lists were missing the base URL prefix, causing 404s in subfolder deployments.

• #767 - API v1 PUT/PATCH/DELETE requests without an ID parameter were not properly rejected.

• DNSSEC page was missing the is_reverse_zone variable, so reverse zones weren’t showing the correct DNSSEC UI.

• API key regeneration link in the modern template was pointing to the wrong URL.

• Input validation hardened across all API controllers.

• Docker: macOS bind mount issue resolved by using PA_CONFIG_PATH.

• Docker: non-root and rootless container execution now supported.

4.1.3

Final bugfix release for the 4.1.x line. This branch is now in maintenance mode and won’t receive new releases. Changes since v4.1.2:

• #1122 - SOA serial incrementing by 2 instead of 1, backported from master.

• #1121 - PostgreSQL search GROUP BY error, backported from master.

• #1105 - Search SQL error and null type crash, backported from master.

• #1104 - Matching record creation broken in multi-record mode and for subdomain zones, backported from master.

• #1106 - TXT validation error not shown on add record page, backported from master.

• #1047 - Pagination and letter filter 404s in subfolder deployments, backported from master.

• Comment search query was referencing a non-existent record_comment_links table.

• Docker: macOS bind mount fix and non-root container support, backported from master.

• Locale fixes for plural form headers and format specifiers across multiple languages.

4.0.10

Final maintenance release for the 4.0.x line. This branch is now in maintenance mode and won’t receive new releases. Changes since v4.0.9:

• #1122 - SOA serial incrementing by 2 instead of 1, backported from master.

• Locale format specifier and plural header fixes across all locales.

Fewer branches going forward

I’m simplifying the branch structure:

• release/4.2.x - current stable release, patch releases tagged here

• master - next release development (4.3.x)

• develop - experimental features, may be unstable

• release/3.x - LTS, security fixes until December 2027

The release/4.0.x and release/4.1.x branches will remain available for reference but won’t receive new releases. If you’re tracking either of those, please switch to release/4.2.x or pin to a version tag.

Docker tags updated

The Docker tags have been updated to match the new branch structure:

• stable - release/4.2.x (recommended for production)

• latest - master (current development)

• dev - develop (experimental, not for production)

• lts - release/3.x (legacy)

• v* - Version-pinned tags (e.g., v4.2.1)

The main change: stable now tracks release/4.2.x instead of the retired release/4.0.x. The next tag has been removed since release/4.1.x is being retired. Everything else stays the same.

Images are published to both Docker Hub (poweradmin/poweradmin) and GitHub Container Registry (ghcr.io/poweradmin/poweradmin).

Thanks

These releases wouldn’t happen without the people who take the time to report issues. Thanks to @ramondelee, @firengate, @gbeine, @dginhoux, @SirGrady, @Verestchagin, @kuhball, @iram-computer, @torstenker-cloud, and @nlarenti for the bug reports that went into these releases.

As always, bug reports and feedback go to GitHub.

A word of caution: v4.2.0 is a feature-heavy release and may still have rough edges. I recommend testing it in a non-production environment first. I’m not marking it as the latest release on GitHub - instead, v4.1.x is now promoted to stable (it was previously a pre-release). The v4.0.x series may still receive some fixes, but I plan to stop supporting it at some point, so if you’re on 4.0.x consider planning an upgrade to 4.1.x.

Group Management

One of the most requested features is finally here. You can now create user groups, add members, assign zones to groups, and control permissions at the group level. Groups integrate directly into zone ownership - instead of assigning zones to individual users, you can assign them to a group and all members get access.

• Create and manage groups with a dedicated UI

• Assign zones to groups for shared ownership

• Group-based permission templates

• MFA enforcement per group

• SSO group mapping - automatically place users into groups based on OIDC/SAML claims

• Audit logging for all group operations

This feature was sponsored by stepping stone AG. See the User Groups documentation for full details.

Group list with permission templates and MFA enforcement settings.

Managing group members.

Assigning zones to a group.

Editing group settings.

Zone File Import & Export

I’ve added a module system that powers new zone file import and export functionality. You can import standard BIND zone files - either creating new zones or merging into existing ones with configurable conflict resolution. Export produces standard zone file format for backup or migration purposes.

See the Zone Import/Export documentation for setup details.

Expanded API v2

API v2 was introduced in v4.1.0. In this release I’ve added several new endpoint groups:

• Zone templates CRUD

• Zone owners management with batch assignment

• Group members and zone management

• PowerDNS zone metadata

See the API configuration docs for setup instructions.

MFA Enforcement

You can now enforce MFA at both user and group level. When enabled, users will be required to set up two-factor authentication on their next login.

See the Security Policies documentation for configuration options.

cert-manager Webhook

I’ve released a new companion project - cert-manager-webhook-poweradmin. It’s a cert-manager webhook solver that automates DNS-01 challenge validation for Let’s Encrypt and other ACME CAs. If you run Kubernetes with cert-manager, you can now use Poweradmin as your DNS provider for automatic certificate issuance.

Thanks to Menzel IT GmbH for sponsoring this.

Other Improvements

• SSO group mapping for OIDC and SAML providers

• Docker - custom CA certificates via TRUSTED_CA_FILE, expanded environment variable coverage, module configuration support. See the Docker installation docs

• 5 new languages - Indonesian, Korean, Swedish, Ukrainian, Vietnamese

Patch Releases

Alongside v4.2.0, I’m releasing patch updates for all active branches:

• v4.1.2 - OIDC group extraction fix, SSO user edit improvements, and other bug fixes

• v4.0.9 - bug fixes for the 4.0.x series. We’re jumping from v4.0.7 directly to v4.0.9 because the v4.0.7 build shipped with the version file already set to 4.0.8, making that version number unusable

• v3.9.10 - translation updates and compatibility fixes for the 3.x LTS series

Upgrading

Back up your database before upgrading. See the upgrade guide for detailed instructions.

From v4.1.x: Replace the application files, run the SQL migration script (sql/poweradmin-*-update-to-4.2.0.sql for your database), clear PHP opcache, and restart your web server.

From v4.0.x: Upgrade to v4.1.x first, then to v4.2.0.

From v3.x: Direct upgrades are not supported. Upgrade to v4.0.0 first, then follow the path above.

PHP Version Support

Poweradmin v4.2.0 requires PHP 8.2 or later (8.2, 8.3, 8.4, 8.5). PHP 8.1 is no longer supported.

Full changelog and download available on GitHub.

🛠️ 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 /login in 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_token instead 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.com instead of example.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 _token field 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 features

• release/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-safe

• next → release/4.1.x - Latest stable features

• latest → master - Will become unstable soon - switch to next or stable

• lts → release/3.x - Legacy, security fixes only

• dev → 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.

OIDC and SAML Authentication

One of the most requested features Single Sign-On via OpenID Connect and SAML 2.0 - is now fully supported. OIDC works out of the box with Google Workspace, Microsoft Entra ID, Okta, Keycloak, Auth0, and Authentik. SAML supports the same providers with SP-initiated SSO.

Both protocols include automatic user provisioning on first login, group-based permission mapping, and account linking for existing users - no need to create accounts manually.

DNS Record Wizards

New interactive wizards for DMARC, SPF, DKIM, CAA, TLSA, and SRV records. Instead of remembering record syntax, you fill in a form and the wizard generates the correct record. Input is validated in real-time, so you won’t end up with a broken SPF or DMARC record.

Redesigned Zone Editor

The zone editor got a rework - better layout, configurable columns, and sorting by owner, ID, or disabled status. You can now edit records inline and do bulk operations without leaving the page.

Granular Permission Controls

Zone Deletion Permissions

Zone deletion is now controlled by separate permissions, independent from edit permissions. Users can manage records without being able to delete entire zones.

• zone_delete_own - delete zones the user owns

• zone_delete_others - delete zones owned by other users

Existing users with edit permissions are automatically granted corresponding delete permissions during upgrade.

Pre-configured Permission Templates

Four new permission templates for common setups:

• Zone Manager - Full self-service zone management

• DNS Editor - Edit records but not SOA/NS (ideal for delegated management)

• Read Only - View-only access for auditors and viewers

• No Access - No permissions for inactive or pending accounts

Improved API

• API v2 with consistent response wrapping

• Permission validation for all API endpoints

• Better error handling across all endpoints, including non-JSON error responses

• PowerDNS ENT record filtering - invalid database entries are automatically excluded

Security Improvements

• Critical MFA bypass fix - v4.0.0 through v4.0.3 allowed bypassing MFA. If you’re running those versions, upgrade immediately.

• Permission enforcement - Non-superusers can no longer modify superuser accounts

• DNSSEC pre-flight validation before zone signing, so you don’t sign a misconfigured zone

Other Improvements

• Username recovery via email for forgotten usernames

• User avatars with OAuth and Gravatar integration

• Symfony Mailer replaces the custom SMTP implementation

• Custom TLD whitelist for CNAME validation

• RFC 2317 classless reverse delegation validation

• SSL/TLS database connections for MySQL and PostgreSQL

• DB_PORT and separate PowerDNS database configuration support

• Immutable container image support for Kubernetes and similar setups

• Improved container health checks and database initialization

• LDAP session caching to reduce authentication overhead

• Lots of bug fixes across DNS validation, DNSSEC, dark mode, PostgreSQL/SQLite compatibility, and more

Upgrading

From v4.0.x

1. Backup your database and files

2. Replace application files with the new release

3. Run the database migration script for your database type:

   # MySQL/MariaDB
mysql -u username -p database < sql/poweradmin-mysql-update-to-4.1.0.sql

# PostgreSQL
psql -h localhost -U username -d database -f sql/poweradmin-pgsql-update-to-4.1.0.sql

# SQLite
sqlite3 /path/to/poweradmin.db < sql/poweradmin-sqlite-update-to-4.1.0.sql

4. Clear PHP opcache and restart your web server

5. Verify login and basic operations

The configuration format is fully backward compatible - no changes to config/settings.php are required.

From v3.x or older

Direct upgrades to v4.1.0 are not supported. First upgrade to v4.0.0, then follow the v4.0.x steps above. For a detailed upgrade path from any version, see the full upgrade documentation.

Docker

Pull the latest image and restart:

docker pull poweradmin/poweradmin:4.1.0

For detailed upgrade instructions, visit docs.poweradmin.org/upgrading/v4.1.0.

PHP Version Notice

Poweradmin 4.1.x will be the last version to support PHP 8.1. Starting with version 4.2.x, the minimum required PHP version will be 8.2. If you’re still on PHP 8.1, now is a good time to upgrade.

Version Support and Branch Strategy

• If you’re on v4.0.x and prefer stability, stay on the release/4.0.x branch. It will continue to receive bug fixes and security updates.

• If you want the latest features, move to release/4.1.x. Initial quick fixes will land here as the release stabilizes through real-world usage.

• If you’re on v3.9.x LTS, the branch remains fully supported until December 2027.

• Avoid master in production - it will receive changes from the develop branch and may become unstable.

Once v4.1.x proves stable in production, it will become the recommended release.

Support the Project

If Poweradmin is useful to you, consider supporting its development via GitHub Sponsors, Open Collective, or PayPal.

Looking Forward

While v4.1.0 is a new release, some users have already been running these changes in production from the master branch. Still, preparing a release this size is exhausting - lots of checks to run from different angles, multiple times, and I’m sure something slipped through. If you hit any issues, please report them on GitHub and I’ll get a patch release out as soon as I can.

Thanks to everyone who reported issues and tested things on v4.0.x and master - it made a real difference. Next up: group-based user management and more API work.

Poweradmin v4.1.0 is available now on GitHub and Docker Hub. For installation instructions and documentation, visit docs.poweradmin.org.

Patch Releases: 4.0.6 and 3.9.9

Before diving into new features, a quick note on maintenance releases.

4.0.6 fixes zone deletion issues, IPv6 PTR record handling, disables MySQL SSL verification by default for backwards compatibility, and improves Docker healthchecks.

3.9.9 allows HTML characters in TXT records and fixes record name handling for those still on the 3.x LTS branch.

No database migrations needed for either - just update the files. If upgrading from 4.0.4 or earlier, run the 4.0.5 migration script first (sql/poweradmin-{mysql,pgsql,sqlite}-update-to-4.0.5.sql).

Q1: Wrapping Up 4.1 and Shipping 4.2

The first quarter is all about stabilization and one major new capability.

Version 4.1 (master branch) is in the final testing phase. This release has been a big one - over 50 issues closed. The highlights:

• Federated authentication - you can now log in via OIDC and SAML. Azure AD, Keycloak, Okta, whatever your org uses. No more managing separate passwords for DNS admins.

• Multi-factor authentication - TOTP-based MFA support.

• Password reset - proper account recovery flow.

• DNS record wizards - guided creation for DMARC, SPF, and DKIM records.

• UI improvements - zone comment tooltips, better template navigation, pagination on search results.

Version 4.2 (develop branch) lands with group-based permissions. This has been requested for years (#480 on GitHub if you want the history). Instead of assigning zones to individual users, you’ll be able to assign them to groups and manage membership. Much more practical for larger teams. I’m also fixing the Azure AD group sync issue that some folks hit with OIDC.

Q2: The Big One - PowerDNS API Integration

This is where things get interesting.

For historical reasons, Poweradmin has always talked directly to the PowerDNS database. Back when the project started, that was the only option. PowerDNS didn’t have a REST API. But it does now, and has for years, and it’s time to use it.

Moving to the PowerDNS API as the primary interface is the focus for Q2.

Why does this matter? Because it unlocks a bunch of features that people keep asking for:

• Remote PowerDNS servers - run Poweradmin on a different host than your DNS server. Proper separation.

• LMDB backend support - LMDB isn’t SQL-based, so there’s no way to support it with direct database access. API mode makes it possible.

• Multi-server management - manage multiple PowerDNS instances from a single Poweradmin. Internal servers, public-facing servers, whatever.

• ExternalDNS integration - for the Kubernetes folks who want automatic DNS records from their ingresses.

• Clean database separation - keep Poweradmin’s data completely separate from PowerDNS data. Different credentials, different hosts, whatever you need.

This is foundational work. Once the API layer is solid, a lot of other things become much easier to build.

What Comes After

If things go well with the API work, later in the year I’d like to tackle:

• Granular API key permissions (restrict keys to specific zones or read-only access)

• Domain metadata support (per-zone AXFR settings, TSIG keys)

• Dashboard improvements with actual metrics visualization

But let’s see how Q1 and Q2 go first. No point making promises about Q4 in February.

If you’re using Poweradmin and have thoughts on priorities, the GitHub issues are always open.

🛠️ What’s Fixed

🔒 Security Improvements

• Secure Delete Flows: Replaced GET confirmation links with POST forms to prevent CSRF attacks on delete operations

• Debug Output Protection: Properly escape debug output and use modern cryptographic functions

• Docker Security: Updated base packages to resolve security vulnerabilities

🌐 API & Core System

• API Crash Prevention: Fixed crash when PowerDNS API returns zone errors

• HTTP 204 Compliance: Return empty body for HTTP 204 responses per RFC 7231

• PHP 8.1 Compatibility: Removed PHP 8.3+ #[Override]attributes that broke older PHP versions

• Router Fix: Prevent page parameter collision with API pagination

• PostgreSQL Sequences: Sync sequences after explicit ID inserts (#942)

🌍 DNS Management

• HTML in TXT Records: Allow HTML characters in TXT records (#953)

• IDN Validation: Validate empty strings in IDN conversion

• Zone Templates: Fixed TypeError when zone_templ_id is NULL in PostgreSQL (#935)

• Record Ordering: Add table prefix to ORDER BY clause (#919)

• Template Lookup: Use domain_id for zone list lookup (#945)

🔒 DNSSEC

• Reverse Zone Detection: Add missing is_reverse_zonevariable to DNSSEC controllers

🐳 Docker & Infrastructure

• FrankenPHP Update: Upgraded to 1.10-php8.4-alpine base image (#877)

• Health Checks: Improved container health check and database initialization

• Admin User Creation: Fixed admin user insert capture before case statement ends

• PostgreSQL Config: Updated packages and removed baked-in config

🔧 Web Server Configuration

• API Routes: Added proper API routes and 204 response handling in Caddy/nginx configs

📧 Email & SMTP

• TLS/STARTTLS: Corrected connection handling for mail delivery (#861)

📦 Installation & Forms

• XML Extension Check: Added missing xml extension check in requirements step

• DNSSEC Default: Make DNSSEC opt-in instead of enabled by default

• Theme Fallback: Gracefully handle removed legacy themes (#899)

📊 Database Migration Required

This release includes database schema updates. Run the appropriate script for your database before upgrading:

# MySQL/MariaDB
mysql -u root -p powerdns < sql/poweradmin-mysql-update-to-4.0.5.sql

# PostgreSQL
psql -U postgres -d powerdns -f sql/poweradmin-pgsql-update-to-4.0.5.sql

# SQLite
sqlite3 /path/to/pdns.db < sql/poweradmin-sqlite-update-to-4.0.5.sql

The migration adds a primary key to the records_zone_templtable, required for MySQL InnoDB Cluster compatibility (#906).

📦 Upgrade Steps

1. Back up your database and configuration

2. Run the database migration script for your database type

3. Download and extract the new version

4. Copy your config/settings.php to the new installation

5. Verify web server configuration (especially if using Caddy)

🧪 Quality Assurance

This release has been thoroughly tested with 3,900 E2E tests across all three supported databases (MySQL, PostgreSQL, SQLite), ensuring stability and reliability.

🚀 What’s Next: v4.1.0

The 4.0.x branch will keep getting maintenance updates and critical fixes, but my main focus now shifts to v4.1.0. Here’s what’s coming:

• Modernized routing system with Symfony Router and API v2

• SAML Authentication with automatic user provisioning (#789)

• Generic OIDC Support for Authentik, Keycloak, and Okta (#918)

• Forgot Username feature (#578)

• Interactive DNS Wizards for DKIM, SPF, and DMARC records (#685)

• Separate Zone Deletion Permission from edit permissions (#97)

• Symfony Mailer replaces custom SMTP implementation (#774)

• Immutable Container Deployments support (#939)

I expect about a month to stabilize the release, finalize UI changes, and finish testing. Thanks for your patience!

🙏 Thank you to everyone who reported issues and contributed to this release!

Download: GitHub Releases

Documentation: docs.poweradmin.org

Docker: docker pull poweradmin/poweradmin:4.0.5

A Busy Year

This was one of the most productive years for the project. We shipped 13 releases, including the major v4.0.0 in July. That’s roughly 1,320 commits, 114 merged pull requests, and around 349 issues addressed. Thanks to the 30 contributors who made this possible.

What’s New in 4.0

The 4.0 release was a big one. Here’s what changed:

Authentication & Security — You can now log in via SAML or OIDC (Google, Azure AD). There’s multi-factor authentication with recovery codes, password reset via email, and a forgot username option. We also added reCAPTCHA support, login attempt tracking with account lockout, IP whitelist/blacklist, and password policies.

API — The API now has OpenAPI/Swagger docs. Non-admin users can manage their own API keys, which is handy if you’re using the Terraform/OpenTofu provider.

DNS — Record validators are stricter and follow RFCs properly. DNSSEC got CSK support. Batch PTR works with IPv6 now. You can import and export records via CSV. Zone templates support DOMAIN and TLD placeholders.

UI — The interface got a full refresh with better dark mode and mobile support. WHOIS lookup is built in. There’s a database consistency checker for when things go wrong.

Deployment — Docker now runs on FrankenPHP. You can use a separate PowerDNS database if needed.

Long-Term Support for 3.x

Not everyone wants to upgrade right away. With version 3.9.8, the 3.x branch enters long-term support. It will get bug fixes and security updates for at least two years. More patch releases may come if needed.

Coming Soon: 4.0.5

A patch release is on the way with bug fixes — PostgreSQL improvements, zone template fixes, and security hardening.

Coming in 4.1

The master branch has new stuff that needs testing before release:

• Wizards for complex DNS record types

• Reverse proxy support

• Immutable container deployments

• More OIDC providers (Authentik, Keycloak, Okta)

• API v2 with RRSet management and bulk operations

• Permission templates for common user roles

Testing everything takes time, but it has to be done.

Further Ahead: 4.2

Work on 4.2 is already happening in the develop branch — user groups, MFA enforcement, per-record comments, SSO group mapping, and better user management with pagination.

Get Involved

Testing — If you can, try the latest master branch. Feedback and bug reports on GitHub are welcome.

Donations — Running this project has costs. If Poweradmin is useful to you, consider supporting it:

• GitHub Sponsors

• Open Collective

• PayPal

Thanks to everyone who has contributed over the years.

I’m excited to announce the release of the Poweradmin Terraform Provider, now available on both the Terraform Registry and OpenTofu Registry. This provider brings Infrastructure as Code capabilities to Poweradmin, letting you manage your DNS infrastructure alongside your other resources.

What’s New

The provider allows you to declaratively manage Poweradmin resources through Terraform/OpenTofu configurations. Whether you’re setting up new DNS zones, managing records, or configuring Poweradmin itself, you can now do it all through your existing IaC workflows.

Registry Links

• Terraform Registry: registry.terraform.io/providers/poweradmin/poweradmin

• OpenTofu Registry: search.opentofu.org/provider/poweradmin/poweradmin/latest

Important Testing Note

The provider currently requires the latest unreleased master branch of Poweradmin, which includes the upcoming v2 API. I’ve wrapped the API responses to make them more Go-friendly and easier to work with in the provider code. If you’re running a stable release, you’ll need to use the latest Docker image for testing.

Looking for Testers

This is where you come in. I’m looking for community members to test the provider in different environments and use cases. Found a bug? Have an idea for improvement? Please open an issue in the GitHub repository at github.com/poweradmin/terraform-provider-poweradmin.

Real-world testing is invaluable for catching edge cases and ensuring the provider works smoothly across different Poweradmin configurations. Your feedback will help polish this tool before the next stable release.

Thanks for being part of the Poweradmin community, and happy testing!

🛠️ What’s Fixed

🔐 Authentication & LDAP Improvements:

• Fixed LDAP Authentication with MFA integration issues (#813)

• Resolved LDAP Authentication PHP compatibility problems (#812)

🔧 Core System Fixes:

• Fixed record comment not being saved while adding records (#814)

• Resolved SQL syntax error causing database access violations (#810)

• Fixed page crashes when clearing search field (#815)

• Added support for automatic splitting of long TXT records (e.g., DKIM) into 255-byte strings with configurable length options (#809)

🔒 DNSSEC Enhancements:

• Fixed DNSSEC zone signing functionality (#819)

• Resolved errors when using “DS and DNS keys” operations (#818)

🐳 Docker Namespace Migration

PowerAdmin Docker images have officially moved to the poweradmin/poweradmin namespace!

This is an important milestone for our project infrastructure:

What Changed:

• New official location: poweradmin/poweradmin on Docker Hub

• Previous location: edmondas/poweradmin (remains available for historical versions)

• All future releases will be published under the official namespace

For Users:

• Update your Docker Compose files and deployment scripts

• Pull the new image: docker pull poweradmin/poweradmin:4.0.4

• Historical tags remain at edmondas/poweradmin for previous releases

Docker Hub: https://hub.docker.com/r/poweradmin/poweradmin

📦 Upgrade Information

This maintenance release requires no database migrations - simply update your code.

Upgrade Steps:

1. Backup your current installation

2. Update to v4.0.4 code

3. Update Docker references to poweradmin/poweradmin if using containers

4. Clear any cached files if applicable

No database changes required.

🚀 Infrastructure as Code: Terraform Provider Development

I’m currently testing a Terraform provider for PowerAdmin that will bring Infrastructure as Code (IaC) capabilities to DNS management. This provider uses an enhanced version of our API and will enable teams to manage DNS records, zones, and configurations alongside their infrastructure deployments. The repository will be made public soon.

🙏 Community

Thank you to everyone who reported issues and provided feedback that made these improvements possible. The Docker namespace migration represents our commitment to professional infrastructure management.

Ready to upgrade? Download v4.0.4 from our GitHub releases page and update your Docker configurations to the official poweradmin/poweradmin namespace.

Remember to update the Docker references in your deployment scripts! 🐳

🛠️ What’s Fixed

🌐 DNS & API Enhancements

The backbone of Poweradmin received significant attention in this release:

SOA Serial Management: Fixed automatic SOA serial updates across all record operations (#804), ensuring DNS consistency and proper change tracking

API Flexibility: Made pagination optional for zones and users endpoints (#803), giving developers more control over data retrieval

LDAP Integration: Resolved Basic Auth TypeError issues when LDAP authentication is enabled (#799), improving hybrid authentication setups

Zone Management: Enhanced reverse zone handling by properly excluding them from forward zone listings for cleaner zone organization

Slave Zone Creation: Now allows slave zone creation with delegation NS records (#802), supporting more complex DNS hierarchies

PowerDNS Metrics: Added Basic Auth support for PowerDNS metrics endpoint (#800), securing monitoring access

🖥️ User Interface Polish

The interface received focused improvements for better usability:

Form Handling: Corrected checkbox behavior in multi-record add forms (#807), eliminating frustrating form submission issues

Dark Mode Support: Removed problematic color classes that were preventing proper dark mode visibility (#801), ensuring accessibility across all themes

📧 Email System Reliability

Email functionality became more robust:

Message Formatting: Fixed email rejection issues caused by long lines (#798), ensuring reliable message delivery across all SMTP servers

📦 Upgrade Information

This release requires no database migrations and can be deployed as a simple code update. All users are encouraged to upgrade for improved stability and functionality.

Upgrade Steps:

1. Backup your current installation

2. Update to v4.0.3 code

3. Clear any cached files if applicable

No database changes are required for this release.

🚀 Looking Ahead: Group-Based Permissions

The next major milestone for Poweradmin is the group-based permissions system (#480) - one of the most requested features from our community.

Target: Implementation before the new year

Key Features:

• Groups contain permissions and users as members

• Zones can be owned by groups, users, or both simultaneously

• Group permissions override individual user permissions

• New ‘Groups’ management tab with full administration capabilities

• Seamless LDAP integration with automatic group mapping

• Perfect compatibility with existing OIDC/SAML authentication

This will particularly benefit enterprise installations, LDAP environments, and organizations using modern authentication systems.

Additional Features Coming: The next version will also include forgot username functionality (#578), separate zone deletion permissions (#97), enhanced RFC 2317 classless reverse delegation (#85), and API key management for non-admin users.

Patch Release Possibility: If critical issues are discovered, another patch release (v4.0.4) may be issued alongside the group permissions development.

🙏 Community Impact

Poweradmin’s continued evolution is powered by our engaged community. Special recognition goes to everyone who reported issues #798 through #807, providing the detailed feedback that made these improvements possible.

Ready to upgrade? Download v4.0.3 from our GitHub releases page and experience these improvements today.

Stay tuned for more exciting updates as development continues toward the New Year group permissions milestone! 🎉

🛠️ Major Bug Fixes by Category

🗃️ Database & Records Management

This release includes important database improvements that enhance data integrity and MySQL compatibility:

• Enhanced Record Handling: Fixed invalid database entries being included in queries (#758), ensuring cleaner and more reliable data retrieval

• MySQL Strict Mode Compatibility: Standardized boolean parameter binding to work seamlessly with MySQL strict mode configurations

• Database Migration Improvements: Added comprehensive migration scripts to fix password_reset_tokens default values across all database types

• PTR Record Handling: Resolved null ptrZoneId issues in RecordCommentSyncService for more reliable reverse DNS management (#760)

🔐 Authentication & Security

Security and authentication received focused attention in this release:

• Recovery Code Validation: Corrected input validation length for recovery codes, ensuring proper two-factor authentication flows (#784)

• Password Reset Tokens: Enhanced password reset token creation to include the ‘used’ field, preventing potential security issues

🌐 DNS & Validation

DNS functionality and validation logic saw significant improvements:

• IP Address Validation: Enhanced IP address validation logic for better accuracy (#794)

• SPF Record Support: Now properly supports multiple instances of SPF mechanisms, improving email security configurations

• LUA Validator Enhancement: Added support for record type prefixes in the LUA validator (#770)

• SRV Record Compliance: Corrected SRV record validation to match PowerDNS format requirements exactly (#755)

• Error Handling: Improved error handling throughout the validation pipeline for better user feedback (#764)

🖥️ User Interface

The user interface received several quality-of-life improvements:

• Enhanced Sorting: Enabled sorting by owner, ID, and disabled status for better record management (#781)

• Form Security: Disabled browser autofill for user creation forms to prevent security issues (#782)

• State Management: Forms now properly clear data and errors when switching between zones (#769)

📧 Mail & SMTP

Email functionality is now more reliable:

• SMTP Authentication: Resolved authentication and response parsing issues that were causing email delivery problems

• Header Validation: Removed invalid SMTP headers that were causing server rejections (#774)

🔌 API & Infrastructure

Backend infrastructure improvements for better reliability:

• API Routing: Resolved routing and method validation issues that were affecting API reliability (#767)

• Docker Improvements: Fixed container startup validation logic for smoother deployments (#766)

📦 Upgrade Information

This is a recommended update for all Poweradmin users. The upgrade process requires running a database migration script specific to your database type.

⚠️ Important: Database Migration Required

Before upgrading, you must run the appropriate SQL migration file for your database:

• MySQL: sql/poweradmin-mysql-update-to-4.0.2.sql

• PostgreSQL: sql/poweradmin-pgsql-update-to-4.0.2.sql

• SQLite: sql/poweradmin-sqlite-update-to-4.0.2.sql

Migration Steps:

1. Backup your existing database

2. Run the appropriate SQL file for your database type

3. Update to v4.0.2

The migration scripts fix critical issues with password reset tokens and ensure your database schema is properly aligned with the new version.

🚀 What’s Cooking Next

The next major release of Poweradmin will bring significant enhancements across authentication, user interface, and system architecture. Here’s what’s coming:

🔐 Authentication & Security

• SAML Authentication: Full SAML support with automatic user provisioning (#789)

• OIDC/OAuth Integration: Support for Google, Azure AD, and Keycloak authentication (#791)

• User Avatars: Avatar support via OAuth providers and Gravatar integration

• User Preferences: Comprehensive user preferences management system

🔌 API Improvements

• Enhanced Security: Permission validation for all API endpoints

• User Empowerment: API key management permissions for non-admin users

🎨 Modern UI Theme (#746)

• Bootstrap 5: Complete migration to Bootstrap 5 with modern sidebar layout

🏗️ Routing & Architecture

• Symfony Router: Modern routing system replacing the legacy BasicRouter

• Clean URLs: Modern URL structure without query parameters for better SEO and usability

🔄 Compatibility Updates

• Legacy Cleanup: Removed support for legacy inc/config.inc.php configuration files

Stay tuned for more updates, and as always, your feedback and contributions help shape the future of Poweradmin!

Poweradmin continues to grow stronger thanks to our active community. Special thanks to all users who reported these issues through GitHub issues #755 through #794, helping us identify and resolve these critical problems. Your detailed bug reports and testing make Poweradmin better for everyone.

🐳 Enhanced Docker Support

The highlight of this release is improved MySQL database configuration support for Docker deployments. I've enhanced the Docker configuration system to allow for better separation of PowerDNS database configurations in containerized environments, making it easier for you to manage complex DNS infrastructures with dedicated database instances.

🛠️ Critical Bug Fixes

In this patch release, I've resolved several important issues that were affecting user experience:

Configuration & Migration Issues:

• Fixed configuration migration errors from v3.9.2 to v4.0.0 (#754) - If you were upgrading from older versions, you'll no longer encounter validation errors during the migration process

• Resolved config summary display problems when using custom configuration files - The configuration summary now properly displays your settings regardless of the config file location

User Interface & Experience:

• Fixed user preference persistence - Your preferences are now properly saved and loaded across sessions

• Corrected pagination calculations when filters are applied (#748) - Page navigation now works correctly when you're browsing filtered results

• Restored missing LDAP section in the Add User form (#750) - LDAP authentication options are now properly displayed where they should be

System Requirements & Performance:

• Added XML extension requirement check during installation (#745) - The installer now properly validates that the required XML extension is available on your system

• Optimized reverse zone filtering by moving logic from PHP to database level (#751) - This change significantly improves performance when you're working with reverse DNS zones

📦 Upgrade Information

This is a recommended update for all Poweradmin users, especially if you're:

• Upgrading from versions prior to v4.0.0

• Using Docker deployments with MySQL

• Experiencing pagination or user preference issues

• Working with reverse DNS zones regularly

The upgrade process is straightforward and maintains full backward compatibility with your existing configurations.

Poweradmin continues to evolve thanks to our active community. Special thanks to all users who reported these issues and helped me identify the root causes.

Key Improvements in DNS Management

Bulk Operations and Data Portability

The introduction of bulk record operations addresses one of our most requested features. You can now add multiple DNS records to a zone through a streamlined interface, significantly reducing the time spent on routine configurations.

The new CSV export functionality provides data portability, making it easier to backup, audit, or migrate your DNS configurations. Combined with our enhanced template zone management system, you can now view all domains using a specific template and manage zones more efficiently.

Enhanced Security Architecture

Security improvements in v4.0.0 reflect the evolving threat landscape:

• Flexible password reset controls allow organizations to align the system with their security policies

• Database-backed user preferences provide personalized experiences without compromising security

• Comprehensive password policy enforcement ensures consistent security standards

• User agreement system with complete audit trails for compliance requirements

• Optional reCAPTCHA integration provides additional protection against automated attacks

Interface Modernization

The user interface has been thoughtfully redesigned with a focus on usability. The new dashboard features a card-based layout that adapts to different screen sizes, while dark theme support reduces eye strain during extended use.

Small but impactful improvements include:

• Required field indicators that prevent submission errors

• Smart zone name suggestions that help avoid common mistakes

• Email template preview functionality with plain text fallback options

• An enhanced installer with clear progress indicators

Technical Foundation Upgrades

v4.0.0 introduces substantial architectural improvements:

• WHOIS/RDAP integration brings registration data into your workflow

• RESTful API with OpenAPI documentation enables automation and integration

• FrankenPHP deployment option for improved performance (Docker)

• Multi-database support across MySQL, PostgreSQL, and SQLite

• Symfony component adoption for robust validation and request handling

Notable Bug Fixes

This release resolves several persistent issues:

• PTR records now properly delete alongside their associated A records

• Duplicate PTR record creation has been eliminated

• CNAME validation correctly rejects non-FQDN content

• Root record CNAME warnings prevent invalid configurations

• Navigation highlighting and form structure inconsistencies have been resolved

Architecture and Standards

The codebase has undergone significant refactoring to improve maintainability:

• Centralized configuration management replaces scattered settings

• RFC-compliant validation ensures standard DNS behavior

• Improved input sanitization and permission checking throughout

• Consistent timezone handling across the application

This is by no means an exhaustive list - I'm not entirely sure I haven't missed something, and it would be difficult to describe all the features and fixes that made it into this release. For a more complete overview, you can explore the documentation at docs.poweradmin.org.

Migration Considerations

Upgrading from v3.x requires careful planning. I've prepared comprehensive documentation at docs.poweradmin.org/upgrading/v4.0.0/ that covers database migrations, configuration updates, and potential compatibility considerations.

Continued Support for v3.x

For organizations and people that prefer to stay with the stable and well-tested v3.x branch while evaluating v4.0.0, I've also released v3.9.5 as a minor patch update. This release ensures that production environments can continue running on the proven v3.x codebase while taking time to properly test the new v4.x features.

Community Contributions

This release benefited greatly from community involvement. Particular recognition goes to @michielvisser for extensive testing and feedback throughout the development cycle, and to @muckl for multiple code contributions.

Looking Forward

v4.0.0 establishes a foundation for future enhancements. The coming weeks will be dedicated to gathering user feedback and addressing any issues that arise from real-world usage. While I don't anticipate major feature additions in the immediate future, I'll focus on stability improvements and bug fixes based on your reports.

I'm particularly interested in understanding which improvements would be most valuable for your workflows, so please share your thoughts and experiences as you explore the new version.

A Personal Note

I'll be honest - this release has left me exhausted. v4.0.0 demanded enormous amounts of brain power and became the most expensive release I've ever produced. I invested in various AI tools to help improve the code and implement new features, spending both my money and countless hours to make Poweradmin better.

Whether this investment was worth it remains to be seen. If you find value in Poweradmin and want to support its continued development, donations through the available methods would be greatly appreciated. If you'd prefer to contribute in another way, please don't hesitate to get in touch.

Poweradmin v4.0.0 is available now. For installation instructions and documentation, visit our project page.

What's New

I've added pagination controls to the zone edit page with customizable rows per page. You can now choose between 10, 25, 50, or 100 records per page, making it much easier to navigate zones with lots of DNS records.

No more multiple clicks through hundreds of records - the interface is now much cleaner and faster.

What's Coming

I'm still working on finalizing the full 4.0.0 release. Right now I'm testing the migration process from older 3.9.x versions to make sure everything upgrades smoothly without any issues.

More updates coming soon once I finish the migration testing.

Enhanced Database Compatibility

This release significantly improves database compatibility across different environments:

PowerDNS Database Prefix Support - Added proper support for PowerDNS database prefixes in the has_similar_records method (#709), ensuring seamless integration with custom PowerDNS configurations that use table prefixes.

PostgreSQL Pagination Improvements - Enhanced PostgreSQL compatibility for domain pagination with complex sorting (#706), resolving issues that could affect large installations with sophisticated sorting requirements.

Improved Zone Management

Several zone management improvements enhance the user experience:

Case-Insensitive Navigation - Zone letter navigation is now case-insensitive (#707), making it easier to find zones regardless of how domain names are capitalized.

Domain Ownership Pagination - Fixed pagination issues with domains having multiple owners (#706), ensuring proper display and navigation when domains are shared across multiple users or groups.

Community Appreciation

I want to extend my sincere thanks to the community members who reported these issues and provided valuable feedback. Your detailed bug reports and suggested solutions make Poweradmin better for everyone.

What's Next

The upcoming 4.0.0 release is still in testing phase and includes multiple exciting new features along with significant UI overhaul changes. Given the scope of these improvements, I want to ensure the release is stable enough before making it available to the community. This requires additional time for thorough testing and validation.

For any issues or suggestions, please create new ticket or start discussion in GitHub.

Why I updated our contribution guidelines

I recently updated our contribution guidelines to better reflect the reality of maintaining this project. These updates include clearer attribution policies and more specific requirements for pull requests, helping contributors understand what makes for a successful submission. These changes aren't meant to discourage participation, but rather to create transparent expectations and ensure the project remains sustainable.

The reality behind the repository

What many don't see is that:

• All work on this project happens during my personal free time

• I review PRs, answer questions, investigate issues, and handle all maintenance tasks

• I personally cover financial costs including the domain, tools, and website hosting

• While I occasionally receive donations (which I greatly appreciate), they represent a small fraction of what the equivalent professional work would cost

Despite these challenges, we've built a stable tool used by organizations worldwide, with a growing user base and improved code quality with each release. The project continues to evolve thanks to community involvement.

I won't be making a code of conduct right now as I don't have the time or interest for this task. Instead, I've updated the existing guidelines which I believe sufficiently clarify expectations while maintaining the collaborative spirit that makes open source so valuable.

Finding joy and moving forward

Despite the challenges, there's something deeply rewarding about maintaining software that helps others. Seeing how people use the project and receiving positive feedback provides tremendous motivation and makes the effort worthwhile.

What keeps me going isn't individual recognition or credit, but knowing we're building something useful together. Your contributions, feedback, and acknowledgments provide the fuel that keeps this project moving forward. Donations also give me a boost of motivation, and I'm always thankful to those who provide this financial support - though this has never been my main target.

How you can help Poweradmin thrive

If you find Poweradmin valuable, here are specific ways you can help the project continue to grow:

• Contribute code - Address open issues or implement new features

• Improve documentation - Help make the project more accessible to new users

• Report bugs - Detailed bug reports with steps to reproduce are incredibly valuable

• Share your success stories - Let us know how Poweradmin helps in your environment

• Spread the word - Tell others about the project if it's been useful to you

Let's continue focusing on what matters most: creating something we can all be proud of that makes everyone's work a little easier.

Improved DNS Record Management

This release adds automatic quoting for TXT records (disabled by default). When enabled by setting $dns_txt_auto_quote = true, all content for TXT record types will be automatically quoted, simplifying DNS management without breaking existing configurations. The handling of quotes in DNS record content has also been improved for better display and storage.

Enhanced UI Experience

Several UI improvements enhance the user experience:

• The edit comment button is now hidden for users without sufficient permissions

• Fixed duplicate DNS record types appearing in dropdown selections (#639), ensuring each record type appears only once when combining multiple record type lists

• Fixed important issue with CAA records by correctly handling quotes in DNS record content (#635)

System Improvements

Several behind-the-scenes improvements enhance system reliability:

• Added post-create hook in Composer to clean up development artifacts

• Added archive exclusion rules for better package management

• Updated top level domain list

Technical Updates

The core dependencies receive important updates:

• Updated CakePHP components to latest patch versions

• Refreshed Symfony components

• Upgraded Twig from 3.18.0 to 3.20.0

These updates ensure better performance and security.

For any issues or suggestions, please create new ticket or start discussion in GitHub.

Improved DNS Record Visibility

DNS record management becomes clearer with disabled records now showing at reduced opacity, making it easier to understand a zone's complete configuration at a glance. This visual enhancement helps track both active and inactive records without cluttering the view.

Enhanced DNSSEC Management

The DNSSEC management experience receives significant improvements:

• Better error handling during key addition processes

• Improved form state persistence to prevent data loss

• Updated RSASHA1-NSEC3 algorithm naming to match PowerDNS format

These changes make DNSSEC configuration more reliable and user-friendly, reducing potential friction points in security setup.

Improved Record Comment Management

DNS record management becomes more robust with these fixes:

• Improved handling of record comments during zone updates

• Prevention of duplicate record comments

• More consistent comment retrieval for duplicate DNS records

System Improvements

Several behind-the-scenes improvements enhance system reliability:

• Restructured modal components for better user interaction (thanks to Riccardo Bessone)

• Improved error handling and display configuration - new experimental configuration file added at config/app.php allows enabling detailed error messages for debugging PowerDNS API issues. To enable debug mode, set display_errors to true in the configuration

  <?php
  
  // This file is experimental and may be renamed or have its configuration changed in the next release.
  
  return [
      'display_errors' => true, // Set to true to display error messages
  ];

• Enhanced database logging and templates

Technical Updates

The core dependencies receive important updates:

• Refreshed Symfony components

• Upgraded Twig to version 3.19.0

These updates ensure better performance and security.

For any issues or suggestions, please create new ticket or start discussion in GitHub.

The new release adds automatic domain record management with the $iface_add_domain_record setting (enabled by default). When enabled, you'll see a checkbox in the zone edit that lets you create matching A/AAAA records automatically. This makes it easier to keep forward and reverse records in sync.

Record Comments System

This version introduces two new settings for record comments. The $iface_record_comments setting turns comment visibility on or off in the interface. When it's on, you can see and edit comments for DNS records right in the interface.

The $record_comments_sync setting lets comments sync between A and PTR records. When this is on, any comment you add or change on an A record will automatically update on its matching PTR record, and vice versa. This helps keep record documentation consistent.

UI Enhancements

The interface has several improvements. The $iface_edit_show_id setting lets you show or hide record IDs in the edit form, which helps with record management and fixing issues.

You can now choose where new items appear in the record management interface. The $iface_edit_add_record_top setting lets you put new record fields at the top or bottom of the list. The $iface_edit_save_changes_top setting does the same for the save changes button, so you can set up the interface in a way that works best for you.

Installation Security Updates

The installation process now includes several security improvements. The $ignore_install_dir setting has been removed to make things more secure. You should now delete the installation directory after you finish installing.

There's a new config file at install/config.php that controls who can access the installer based on IP address. This is useful when you're installing in public spaces or on shared hosting. You can set specific IP addresses and IP ranges that are allowed to access the installer:

'ip_access' => [  
    'enabled' => false,  
    'allowed_ips' => [  
        '127.0.0.1',  
        '::1',  
    ],  
    'allowed_ranges' => [  
        //'192.168.0.0/16',  
        //'172.16.0.0/12',
        //'10.0.0.0/8'
    ]  
]

The installation wizard now includes CSRF protection to prevent unauthorized access to installation steps. You can turn this on or off with this setting:

For better security during installation:

• Turn on IP access control when installing in public spaces

• Keep CSRF protection on unless you're fixing specific problems

• Delete the installation directory when you're done

Database Changes

For MySQL (or derivatives):

ALTER TABLE zone_templ_records MODIFY COLUMN content varchar(2048) NOT NULL;

For PostgreSQL:

ALTER TABLE zone_templ_records ALTER COLUMN content TYPE varchar(2048), ALTER COLUMN content SET NOT NULL;

For SQLite:

There are more steps required. Please check the related migration file: poweradmin-sqlite-update-to-3.9.0.sql

Credits

Thanks to all individuals, IRAM (Institut de Radioastronomie Millimétrique), Orange Cyberdefense, and others who have contributed and supported this project. Your continuous feedback, bug reports and suggestions help improve this software and make it better for everyone.

What's Next

Time for a short break before starting on new features. Bug fixes for this release will be handled if needed. More features are planned for the future. If you'd like to prioritize specific features or discuss custom implementations, feel free to get in touch about collaboration, donation, or contract options.