v3.0 Release Notes¶
This document describes all new features and changes in the release. The format is based on Keep a Changelog and this project adheres to Semantic Versioning.
Release Overview¶
- Changed DNS Zone names to ignore letter case for uniqueness.
- Updated TXT records text field to align with RFC 1035 and support up to 65535 bytes in total.
v3.0.0 (2026-11-10)¶
Breaking Changes¶
- #252 - Changed DNS Zone name uniqueness within a DNS View to ignore letter case.
- #252 - Changed the upgrade migration to abort while DNS Zones in the same DNS View have names that differ only by letter case; see the upgrade guide.
- #285 - Changed DNSRegistrar url field name to portal_url.
Added¶
- #252 - Added the
check_dns_zone_name_collisionsmanagement command to report DNS Zones whose names differ only by letter case.
Removed¶
- #295 - Dropped support for Python 3.10.
Fixed¶
- #247 - Fixed creating a DNS Zone through the API without specifying a DNS View (defaults to Default view).
- #259 - Fixed the
Auto-create PTR Recordscolumn in the DNS Zone table to render the same check/X icons as the detail view and the other boolean columns, instead of plain Unicode characters. - #265 - Fixed the SOA Retry field label in the DNS Zone bulk edit form.
- #266 - Fixed DNS Zone bulk edit rejecting valid SOA RNAME values.
- #271 - Fixed the IP Address field label on the A Record and AAAA Record forms displaying as "Ip address".
- #273 - Fixed
TXTRecord.textbeing limited to 256 characters, which rejected valid records such as 2048-bit DKIM keys. TXT content now follows RFC 1035 §3.3.14: up to 65535 bytes in total, split into<character-string>values of up to 255 bytes each. Long values are split automatically, and explicit DNS presentation format ("part one" "part two") is accepted to control where the boundaries fall.