What's Changed
* Fixed duplicate record check for `enforce_unique_records` by peteeckel in https://github.com/peteeckel/netbox-plugin-dns/pull/193
* Fixed SOA Serial Auto behaviour with bulk imports by peteeckel in https://github.com/peteeckel/netbox-plugin-dns/pull/195
* Reduced the number of `save()` operations when a `Zone` object is saved by peteeckel in https://github.com/peteeckel/netbox-plugin-dns/pull/198
* Added the missing address field to registrar views by peteeckel in https://github.com/peteeckel/netbox-plugin-dns/pull/200
* Added filter tests by peteeckel in https://github.com/peteeckel/netbox-plugin-dns/pull/202
* New Feature: Ensure unique TTL for RRSets by peteeckel in https://github.com/peteeckel/netbox-plugin-dns/pull/206 (see below)
* Changed Feature: Enable enforcing record uniqueness by default by peteeckel in https://github.com/peteeckel/netbox-plugin-dns/pull/208 (see below)
* Updated installation documentation by tobiWu in https://github.com/peteeckel/netbox-plugin-dns/pull/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](https://www.rfc-editor.org/rfc/rfc2181#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](https://github.com/peteeckel/netbox-plugin-dns/blob/main/docs/using_netbox_dns.md#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](https://github.com/peteeckel/netbox-plugin-dns/blob/main/docs/using_netbox_dns.md#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 https://github.com/peteeckel/netbox-plugin-dns/pull/214
**Full Changelog**: https://github.com/peteeckel/netbox-plugin-dns/compare/0.22.4...0.22.5