Compatibility Release: NetBox 4.0.0

What's Changed

• NetBox 4.0 support and dropped support for earlier versions up to 3.7.8
• Adjusted GitHub workflows to reflect dropped support for Python 3.8 and 3.9
• Replaced references to extras.plugins with netbox.plugins
• Replaced object references with a reference by object id/pk in cases where a potentially unsaved object is referenced in filter() expressions
• Removed the ready() method that accessed the database by calling ContentType.objects.get_for_model() because of a RuntimeWarning during initialisation
• Changed the actions attributes in tables to be dictionaries instead of tuples because of NetBox PR #14670
• Modified the 'Add Record' button in the base template for the zone detail view so it matches the rendition of the other buttons (using <button> instead of CSS on the <a> element
• Adjusted the menu item buttons to the new UI look by removing the colours
• Refactored filtersets to become compatible with htmx.ObjectSelectorView, specifically its _get_filterset_class() method.
• Added the brief_field attribute to all model serializers
• Added description to all models and to brief_fields for all serializers matching NetBox PR #15238
• Workaround for NetBox #15351: Remove validators from ZoneSerializer if nested=True
• Renamed ContentType to ObjectType and changed parameter name to object_type NetBox PR# 15327
• Added tests for all filter sets to make automated testing by the extended NetBox filter set test framework possible NetBox PR #15369
• Renamed the object_type attribute for the IPAM Coupling ipaddress_dns_zone_id CF to related_object_type NetBox PR #15366
• Added missing filters detected by the new NetBox test functionality from NetBox PR #15369
• Migrated old-style fieldsets to the new FieldSet class to remove 'fieldsets contains a non-FieldSet item' warnings NetBox PR #15415
• Reworked the whole GraphQL support to work with Strawberry NetBox PR #15141 and added GraphQL tests
• Views are no longer optional with this PR, but a new 'Default View' largely takes the role of the former view=None case.

What's Changed

• NetBox 4 Compatibility by @peteeckel in #153
• "Default View" concept by @peteeckel in #242

Feature/Bugfix Release

What's Changed

• Fixed typo in management command "cleanup_rrset_ttl" by @peteeckel in #236
• Added FQDN to global search by @peteeckel in #240
• Improved get_value_record() based on the new fqdn field by @peteeckel in #243
• Run super().clean() in custom clean() methods by @peteeckel in #249
• Always display tenant for records if defined, not only for unmanaged records by @peteeckel in #251
• Prepared release 0.22.9 by @peteeckel in #253

Full Changelog: 0.22.8...0.22.9

Pre-release: Compatibility with NetBox 4.0-beta2

What's Changed

• Fixed typo in management command "cleanup_rrset_ttl" by @peteeckel in #236
• Added FQDN to global search by @peteeckel in #240
• Improved get_value_record() based on the new fqdn field by @peteeckel in #243

Full Changelog: 1.0-beta1...1.0-beta2

Pre-Release: Compatibility with NetBox 4.0-beta1

Caution: Pre-Release

This release makes NetBox DNS compatible with NetBox 4 in its first pre-release 4.0-beta1.

It is provided for testing purposes only and should not be used in production. There may or may not be a migration path to the final release 1.0.0, so make sure you have a good backup when you install this version.

For a list of changes, please see #153. Full release notes will be published with the final release 1.0.0.

Feature/Bugfix Release

What's Changed

• Fixed the update logic for RFC2317 CNAMEs by @peteeckel in #226
• Backported tests from the NetBox 4 compatibility branch by @peteeckel in #227
• Swapped the order of name and zone in Record tables by @peteeckel in #228
• Enabled leaving "RFC2317 Parent Managed" untouched in bulk edit by @peteeckel in #230
• Added FQDN Filtering by @peteeckel in #232
• Fixed the name of the record FQDN migration by @peteeckel in #234

Release 0.22.7 was pulled because of #233.

Full Changelog: 0.22.6...0.22.8

Feature/Bugfix Release

What's Changed

• Fixed the update logic for RFC2317 CNAMEs by @peteeckel in #226
• Backported tests from the NetBox 4 compatibility branch by @peteeckel in #227
• Swapped the order of name and zone in Record tables by @peteeckel in #228
• Enabled leaving "RFC2317 Parent Managed" untouched in bulk edit by @peteeckel in #230
• Added FQDN Filtering by @peteeckel in #232

Full Changelog: 0.22.6...0.22.7

Feature/Bugfix Release

What's Changed

• Provide information about CNAME/target relationship in the record detail view by @peteeckel in #217
• Removed the ready() method by @peteeckel in #219

Full Changelog: 0.22.5...0.22.6

Feature/Bugfix Release

What's Changed

• Fixed duplicate record check for enforce_unique_records by @peteeckel in #193
• Fixed SOA Serial Auto behaviour with bulk imports by @peteeckel in #195
• Reduced the number of save() operations when a Zone object is saved by @peteeckel in #198
• Added the missing address field to registrar views by @peteeckel in #200
• Added filter tests by @peteeckel in #202
• New Feature: Ensure unique TTL for RRSets by @peteeckel in #206 (see below)
• Changed Feature: Enable enforcing record uniqueness by default by @peteeckel in #208 (see below)
• Updated installation documentation by @tobiWu in #214

Breaking Changes

This release contains two changes that might clash with data in existing installations of NetBox DNS.

The TTL for records in a record set (RRSet) is now enforced to be the same for all records

This is a feature that was requested in #205. RFC 2181, section 5.2 states that having RRSets with different TTLs for records of the same name, class and type is deprecated as it can create problems with the DNS caching infrastructure.

There is a new feature flag enforce_unique_rrset_ttl that is described in chapter Uniqueness of TTLs across RRSets of the documentation. This feature is enabled by default, which may conflict with existing data not satisfying the requirement.

One possible solution is to make existing DNS data compliant by using the management command cleanup_rrset_ttl, the other is to disable the enforcement by setting enforce_unique_rrset_ttl to False:

PLUGINS_CONFIG = {
    'netbox_dns': {
        ...
        'enforce_unique_rrset_ttl': False,
        ...
    },
}

Record uniqueness is now enforced by default

The other breaking change affects an older feature flag enforce_uniqe_records described in chapter Uniqueness of Records of the documentation. As it turned out, more users had problems without it being enabled that with it, so the new default is True, though having duplicate records is neither forbidden nor even marked as deprecated.

Should this be problematic, the feature can be disabled again by setting enforce_unique_records to False:

PLUGINS_CONFIG = {
    'netbox_dns': {
        ...
        'enforce_unique_records': False,
        ...
    },
}

New Contributors

• @tobiWu made their first contribution in #214

Full Changelog: 0.22.4...0.22.5

Bugfix Release

What's Changed

• Added nameservers to the bulk importable files for Zone by @peteeckel in #183
• Set more agreeable defaults for SOA Refresh and Expire by @peteeckel in #185
• Relativise record names to zone name by @peteeckel in #188
• Removed double save() for address records with PTR records by @peteeckel in #189
• Do not clear DNS name if no coupled DNS record has been set by @peteeckel in #191

Full Changelog: 0.22.3...0.22.4

🔥 Hotfix Release

Important Hotfix

This release must be installed on all systems running NetBox 3.7.3 or later. NetBox 3.7.3 pushed the netaddr dependency from 0.10.1 to 1.2.1, which breaks a crucial functionality NetBox DNS was relying on.

Please upgrade NetBox DNS as soon as possible to avoid data corruption and spurious errors!

What's Changed

• No longer rely on netaddr.IPNetwork partial IPv4 network completion by @peteeckel in #180

Full Changelog: 0.22.2...0.22.3