Skip to content

Releases: peteeckel/netbox-plugin-dns

Bugfix/Feature Release 1.1.6

21 Nov 20:00
5cf6b4f
Compare
Choose a tag to compare

What's Changed

  • Added GraphQL fields for reverse relations internal to NetBox DNS by @peteeckel in #471
  • Fixed change detection for custom fields by @peteeckel in #473
  • Convert ip_address to a netaddr.IPAddress object before checking for changes by @peteeckel in #477
  • Run delete() for nameserver objects, not a queryset on removal by @peteeckel in #478
  • Fixed logic for updating zone SOA SERIAL on record save() by @peteeckel in #479
  • Provided slightly more detailed debugging for rebuild_dnssync by @peteeckel in #481
  • Fixed the documentation regarding status names in settings.py by @peteeckel in #482

Full Changelog: 1.1.5...1.1.6

Feature/Bugfix Release 1.1.5

28 Oct 23:09
e1c0fc2
Compare
Choose a tag to compare

What's Changed

  • Added a warning when a CNAME value should be in NetBox DNS but is not by @peteeckel in #438
  • Changed default menu name from "NetBox DNS" to "DNS" by @peteeckel in #440
  • Only check for active zones for a CNAME value warning by @peteeckel in #442
  • Clarify docs for migration of IPEM Coupling to DNSsync by @Stathogon in #443
  • Added a warning when a record in a zone may be masked from view by a child zone by @peteeckel in #446
  • Clarify record import by @peteeckel in #454
  • Added a column for DNS address records to the IP address table by @peteeckel in #458
  • Fixed translations for "Views" by @peteeckel in #461
  • Added delegation record tables for zones by @peteeckel in #462
  • Detect misconfigured plugin config lists at start time by @peteeckel in #464

Full Changelog: 1.1.4...1.1.5

Feature/Bugfix Release 1.1.4

15 Oct 19:05
e0c6907
Compare
Choose a tag to compare

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

Full Changelog: 1.1.3...1.1.4

Feature Release 1.1.3

02 Oct 14:33
0e9ffda
Compare
Choose a tag to compare

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

Full Changelog: 1.1.2...1.1.3

Feature Release 1.1.2

27 Sep 00:08
8c1dec6
Compare
Choose a tag to compare

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

12 Sep 19:23
eaead49
Compare
Choose a tag to compare

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

Full Changelog: 1.1.0...1.1.1

Feature Release 1.1.0

03 Sep 19:12
586372a
Compare
Choose a tag to compare

What's Changed

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

29 Aug 14:46
fcf297e
Compare
Choose a tag to compare

What's Changed

Full Changelog: 1.0.6...1.0.7

Beta Release 1.1.0b7

21 Aug 18:08
Compare
Choose a tag to compare
Beta Release 1.1.0b7 Pre-release
Pre-release

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