Changelog¶
1.5.0 (October 2, 2023)¶
DEPLOYMENT NOTES¶
Zone names are now normalized when parsing them from the API or UI. In the past Curl scripts used for migrations at customers used zones without a dot at the end. These will still work but realize the zone will always get a dot at the end inside ZoneControl now.
Database tables for zone audit logs and zone history at customers may still have entries without a dot at the end. This release comes with a migration to append a dot to zones without a dot (at the end) in the audit log and zone history tables. Please test this migration in a non-production environment first!
The HTTP status response code for a successful POST
call to api/v1/servers/«SERVER_ID»/zones
has been changed from 200
to 201
. This is the API call for creating a zone.
This might affect software and scripts that check for an exact 2xx status response instead of checking for a success response code.
It is now possible to override the Gunicorn config with an /etc/zonecontrol/gunicorn_overrides.py
file. This procedure is similar to how it is done in the Platform Filter and is already implemented in the ZoneControl Ansible role.
BUG FIXES¶
Fix silent failure when adding a zone with non-canonical nameservers (no dot at the end) !294
Normalize zone names when receiving them from the API or UI !286
Make background opaque on template dropdown UI element !285
Check for AnonymousUser in more places, preventing stack traces !284
Make ZoneControl API status code for creating a zone equal that of the Authoritative API !276
NEW FEATURES¶
Support Gunicorn config overrides !277
IMPROVEMENTS¶
Remove the DNSSEC dialog flicker when opening a zone for the second (or more) time; this also removes a lot of errors on the dev console !287
Fix several build issues making them less flaky and faster !289, !282, !281
Adapt PDNS Auth API tests for ZoneControl, adding a new test suite !280
Add documentation for zone templates !292
1.4.2 (May 19, 2023)¶
DEPLOYMENT NOTES¶
ZONECONTROL_NSEC3PARAM_DEFAULT
can be changed in settings.py
, but it is advised to keep it at the default of "1 0 0 -"
.
BUG FIXES¶
Support for PEP 440 compliant version numbers so RPM packages built again !270
NEW FEATURES¶
NSEC3 support in DNSSEC settings for zones !271
IMPROVEMENTS¶
1.4.1 (September 2, 2022)¶
BUG FIXES¶
1.4.0 (March 10, 2022)¶
From this release onwards Debian Buster is no longer supported.
NEW FEATURES¶
IMPROVEMENTS¶
1.3.4 (October 14, 2021)¶
BUG FIXES¶
1.3.3 (July 09, 2021)¶
NEW FEATURES¶
Implement the search API endpoint with permission checking (ZC-120, !249).
BUG FIXES¶
1.3.2 (March 25, 2021)¶
IMPROVEMENTS¶
BUG FIXES¶
1.3.1 (January 21, 2021)¶
NEW FEATURES¶
PostGreSQL support has been added and can be enabled by installing
zonecontrol-postgresql
(!245)
BUG FIXES¶
IMPROVEMENTS¶
zonecontrol-cache
has been split into a seperate package for Debian, as was the case for EL
1.3.0 (November 26, 2020)¶
Alpha 1: September 22, 2020
NEW FEATURES¶
BUG FIXES¶
IMPROVEMENTS¶
1.2.0 (June 15, 2020)¶
Alpha 1: February 26 2020
Beta 1: March 16 2020
RC 1: April 22, 2020
NEW FEATURES¶
The zones list can be cached in Redis, drastically improving performance of the web-interface when PowerDNS is serving many domains (!206)
This requires the
zonecontrol-cache
service to be runningThis caching can be controlled by the the
ZONECONTROL_CACHE_ZONES_*
settings
The DNSSEC information is not longer requested by default for the zone-overview, improving performance of the frontend (!203)
This can be controlled with the
ZONECONTROL_ZONE_OVERVIEW_DNSSEC
configuration option
The ‘edited’ serial is now displayed in the zone-overview (ZC-40, !201)
New distribution support:
RHEL/CentOS/OL 8
Debian Buster
BUG FIXES¶
IMPROVEMENTS¶
Permission management has been tightened (ZC-1, !194)
Users with these permissions and staff status can add users to their groups:
auth | group | Can change group
auth | user | Can change user
The same user can not see groups they don’t belong to
Staff users with ‘Can change user’ permissions can no longer - See or give staff status - See or give superuser status - Edit user permissions
No one but superuser can now edit - User permissions - Group permissions
Users can only see users from their groups in the user-admin, but they can add them to their groups in the group-admin
Several fields in the administrative interface have been hidden as a result
Zone and server permissions are now enforced for staff-users in the administrative backend (ZC-14, !216)
Several visuals in the frontend have been harmonized and improved (!215)
Django is updated to the latest LTS version, 2.2 (!204)
Javascript components are upgraded. Most importantly, Angular is now at version 7.2 (!193)
Documentation has been updated with all new features and sections on the permissions model
1.1.1 (July 10, 2019)¶
BUG FIXES¶
Don’t have an empty result when the per-RRset limits list is longer than 1 (!199)
1.1.0 (June 24, 2019)¶
Alpha 1: internal only
Alpha 2: internal only
Alpha 3: May 20 2019
Beta 1: May 23 2019
BREAKING CHANGES¶
NEW FEATURES¶
Ability to limit the kinds of zones that are allowed to be created. By default, all 3 kinds are allowed. This limit can be set in the settings.py file by the system administrator. (!172)
The zone overview is paginated, showing 25 zones per page. (PDNS-37, !171)
The records overview is paginated, showing 200 records per page. (PDNS-37, !171)
PTR records can be automatically generated by appending a ‘*’ after the ip address. This feature can be disabled in the settings.py by the system administrator. (PDNS-158, PDNS-189, !174)
The zone settings dialog has been extended with buttons to queue NOTIFY messages (for master zones) and retrieve the zone (for slave zones). The system administrator can disable this feature in settings.py. (!173)
The DNSSEC dialog shows what kind of keys will be created once the user clicks “Enable DNSSEC”. (PDNS-39, !175)
An ‘advanced DNSSEC’ role permission has been added. Users with this permission have a tab in the DNSSEC dialog that allows manipulation of all keys. (PDNS-39, !175)
Per-RRSet role-based access control has been added. This feature allows roles to be restricted to records of certain names and types. By default, all records are allowed when a role has access to a zone. (PDNS-165, PDNS-35, !178)
BUG FIXES¶
1.0.1 (July 17, 2018)¶
NEW FEATURES¶
Implement rolebased API “pass through” (#128)
Comments for zone records (#122) - Tool to import comments from PowerDNS Authoritative Server
roles: Granular permissions for zone settings, DNSSEC and version restores (#104)
IMPROVEMENTS¶
pkg: Let yum figure out which mysql lib to pull in (#144)
pkg: Add MySQL support package for CentOS 7 (#127)
admin: More user-friendly role admin UI (#104)
dnssec: When enabling DNSSEC, the configured DNSSEC server defaults are now honored (#105)
BUG FIXES¶
Fix API error when adding or removing zone (#139)
Catch SOA entries that do not exist (#133)
backend: Fix 500 error when adding non-template zone (cf0393e)
builder: Fix missing styling in built packages, debian build fixes (#95)
1.0.0 (September 20, 2017)¶
First release.
NEW FEATURES¶
Zone version history and restore (#56)
Zone templates (#63)
builder: New build system, CentOS 7 and Debian Stretch packages (#70)
IMPROVEMENTS: - libs: Upgraded to Angular 4.3.6 and Webpack 3.5.5
BUG FIXES: - dnssec: Correct handling of ksk/zsk keys in UI (#65)