Feature/Bugfix Release 1.1.4

What's Changed

• Fix "Tenant Group" label for zone bulk import by @peteeckel in #419
• Added documentation for Zone/Record status customisation by @peteeckel in #421
• Added validation for TXT and SRV record values, and help with adding them to a zone by @peteeckel in #424
• Updated translations for PR #424 by @peteeckel in #425
• Added filter for Zone and Record "active" status by @peteeckel in #427
• ENG-3602 - Workflow trigger when netbox-plugin.yaml is modified by @natm in #422
• Made tests more compatible with NetBox 4.0 by @peteeckel in #428
• Added filtering by View to RecordFilterForm by @peteeckel in #431
• Housekeeping/code cleanup by @peteeckel in #432
• Fix typo "Plesase" instead of "Please" by @mathieumd in #433
• Re-enabled running lint and test on pull requests by @peteeckel in #434
• Removed the NetBox branching version from the incompatibility warning by @peteeckel in #435

New Contributors

• @natm made their first contribution in #422
• @mathieumd made their first contribution in #433

Full Changelog: 1.1.3...1.1.4

Feature Release 1.1.3

New Feature

This release adds gettext support to NetBox DNS, making it possible to translate the plugin to other languages. Initially, English and German are supported, but contributions of translation files are very welcome.

What's Changed

• Add an option to turn off optimisation for rebuild_dnssync by @peteeckel in #411
• Add gettext support to NetBox DNS by @peteeckel in #413
• Housekeeping: UI Cleanup by @peteeckel in #415

Full Changelog: 1.1.2...1.1.3

Feature Release 1.1.2

This release adds the feature of filtering IP addresses for a given view. This makes it possible to determine different sets of IP addresses to be considered for address record creation by view, so for example one can select only specific IP addresses to be resolvable in the external view. Thanks @alehaa for the suggestion!

What's Changed

• Added TLSA to the list of record types for which leading underscores are allowed by @peteeckel in #403
• Added test for correct functionality of the "Disable DNSsync" CF by @peteeckel in #404
• Reduce DB queries by @peteeckel in #405
• Remove unnecessary imports in the GraphQL schema definitions by @peteeckel in #406
• Added functionality to add IP address filters to DNS views for IPAM DNSsync by @peteeckel in #407
• Refer to ModelState to find whether an object is being changed by @peteeckel in #408

Full Changelog: 1.1.1...1.1.2

Bugfix Release 1.1.1

What's Changed

• Allow empty host label for DNSsync by @peteeckel in #384
• Clean up orphaned object changes for the renamed Contact model by @peteeckel in #386
• Documentation: Added warning for NetBox Branching by @peteeckel in #390
• Documentation: Added instructions for migrating from Coupling to DNSsync by @peteeckel in #391
• Show only managed DNS records in ManagedRecordListView by @freym in #395

New Contributors

• @freym made their first contribution in #395

Full Changelog: 1.1.0...1.1.1

Feature Release 1.1.0

What's Changed

• NetBox 4.0.11 adjustments by @peteeckel in #380
• Replace IPAM Coupling with IPAM DNSsync by @peteeckel in #376
• Rename the Contact model to RegistrationContact by @peteeckel in #373
• Release 1.1.0 by @peteeckel in #382

Breaking Changes

NetBox DNS contains two breaking changes.

IPAM DNSsync replaces IPAM Coupling

The IPAM DNSsync feature replaces the IPAM Coupling feature. IPAM Coupling will no longer work after the upgrade to 1.1.0, so if you are relying on it (which you shouldn't, as it was always marked as "experimental" :-)) and need time to plan the transition, do not upgrade beyond 1.0.x until the transition has been completed.

NetBox DNS 1.0 continues to work with NetBox 4.1, but at the current time is not guaranteed to work with NetBox 4.2. That defines the migration window, depending on your NetBox upgrade strategy.

Differences between IPAM Coupling and IPAM DNSsync

• IPAM DNSsync does not require manual zone/name selection for IP addresses. Just the prefix/view mapping needs to be maintained.
• IPAM DNSsync instead uses the 'DNS Name' field of the IP address object. Zone selection is automated by zone name, view and the assignment of IP prefixes to views.
• The 'DNS name' field of the IP address object will no longer be overwritten by NetBox DNS.
• IPAM DNSsync supports address records in multiple views, while IPAM Coupling only allowed one DNS record per IP address (this was the most severe shortcoming of IPAM Coupling)
• Unlike IPAM Coupling, IPAM DNSsync does not try to obey object permissions on DNS objects. The support for this was always incomplete and inconsistent, and trying to validate object permissions of complex operations like the ones NetBox DNS executes in the background was a major pain from the start. If you require that kind of validation, please implement it in Custom Validators tailored to your needs.
• Some IPAM Coupling data will be retained to ease migration, specifically the 'TTL' and 'Disable PTR' custom fields.
• The 'DNS Name' field filled by IPAM Coupling serves as an input field for IPAM DNSsync, so the resulting DNS records will be consistent with the old feature.

Contacts have been renamed to Registration Contacts

When the feature to enable the management of domain registration information was introduced, it seemed like a good idea to name the model for the Admin-C, Tech-C etc. 'Contact'. The idea was that namespacing by the plugin's application name would provide enough separation from the core 'Contact' model.

As it turned out, that idea was wrong. When Strawberry replaced the old GraphQL package in NetBox, the collisions became apparent as Strawberry does not observe the namespacing by app. This could be worked around, but error messages when creating the strawberry schema remained.

For this reason, this PR renames the "Contact" model to "RegistrationContact", which resolves the issue.

All REST and GraphQL API clients and custom scripts DNS registration contacts need to be adjusted to reflect the renamed model.

Full Changelog: 1.0.7...1.1.0

1.0.7

What's Changed

• Enabled searching for records by FQDN in quick search by @peteeckel in #353
• Fixed validation for RNAMEs containing a backslash by @peteeckel in #356
• Added FQDN to the record table column options by @peteeckel in #358
• Fixed the FQDN column name by @peteeckel in #359
• Added view to the record tables by @peteeckel in #361
• Removed redundant field declarations in tables by @peteeckel in #362
• Removed explicit API endpoints that can be replaced by filters by @peteeckel in #366
• Minor fixes to the model declarations by @peteeckel in #367
• Check against decrease by soa_serial_auto only if it gets enabled by @peteeckel in #370
• Added the feature to add Contacts to Zone, Record, View and NameServer by @ThomasADavis and @peteeckel in #374
• Use get_model_urls to reduce complexity in URL registration by @peteeckel in #375
• Perform proper authorisation checks on GraphQL queries by @peteeckel in #378
• Prepared release 1.0.7 by @peteeckel in #379

Full Changelog: 1.0.6...1.0.7

Beta Release 1.1.0b7

What's Changed

• Fixed validation for RNAMEs containing a backslash by @peteeckel in #356
• Fixed automatic conflict resolution for address records with non-matching TTL settings
• Improvement of performance for some long-running tasks such as changes to zone names and views

Beta Release 1.1.0b6

What's Changed

• Fixed a huge performance issue that lingered around for quite a while now. Some operations are five times as fast now.

Beta Release 1.1.0b5

What's Changed

• Some minor adjustments and a crucial fix to the prefix selector in the view edit form