Skip to content

Releases: peteeckel/netbox-plugin-dns

Beta Release 1.1.0b4

16 Aug 10:04
Compare
Choose a tag to compare
Beta Release 1.1.0b4 Pre-release
Pre-release

What's Changed

  • The feature formerly planned to be called "IPAM AutoDNS" is now called "IPAM DNSsync". The best way to deal with lawyers is not to wake them while they're asleep.

Bugfix Release 1.0.6

14 Aug 15:21
c97aa84
Compare
Choose a tag to compare

What's Changed

  • Include record templates if zone templates are cloned by @peteeckel in #329
  • Fixed filtering of zones by nameserver in the GUI by @peteeckel in #332
  • Implemented filtering nameservers by zone and SOA zone by @peteeckel in #333
  • Replaced list comprehension over objects by leaner query for pk by @peteeckel in #334
  • Fixed tests for NetBox 4.0.8 (new Strawberry release) by @peteeckel in #335
  • Updated the version matrix for NetBox 4.0.8 by @peteeckel in #336
  • disable_ptr must be a BooleanField in RecordForm by @peteeckel in #338
  • Fixed wrong casing of all by @peteeckel in #339
  • Check for changed custom fields in ObjectModificationMixin by @peteeckel in #342
  • Do not overwrite the contents of SOA SERIAL in ZoneForm by @peteeckel in #344
  • Properly handle custom field data when validating zone views by @peteeckel in #347
  • RRset TTL with inactive records by @peteeckel in #349
  • Modified event rule tests so they work both with NetBox 4.0.x and 4.1.x by @peteeckel in #351

Full Changelog: 1.0.5...1.0.6

New beta release 1.1b3

14 Aug 07:16
Compare
Choose a tag to compare
Pre-release

What's Changed

  • Error message on trying to change a prefix (prefix or VRF) instead of silently dropping it from all views. I't better to make users aware that they are potentially creating huge DNS changes than to just do it.
  • Added a button in the prefix detail view that can be used to assign views to a prefix. Previously you had to visit all affected views to make changes to the assignment for a given prefix.
  • Added a warning when creating duplicate IP addresses with the same DNS name and unique records are enforced. Previously this resulted in a 500 error.
  • Some additional permission checks, e.g. when accessing views from a prefix and vice versa.
  • Updated the documentation to the NetBox 4.1 theme.
  • Some minor fixes and improvements.

If all is going according to plan (and if I continue to receive exactly zero bug reports or other feedback, nudge, nudge!) this will be the release candidate for when NetBox 4.1 gets released as well.

1.1.0-beta2

07 Aug 21:17
Compare
Choose a tag to compare
1.1.0-beta2 Pre-release
Pre-release

Beta Release: Support for NetBox 4.1.0-beta1

05 Aug 21:43
Compare
Choose a tag to compare

Beta Release 1.1.0-beta1

Caution: This is a pre-release and must not be used in production environments! It may contain bugs, and there may not be an upgrade path to a later production release. Using this release in production may result in operational problems and data loss. Make sure to have a backup of your existing test installation, and did I mention it: Don't use it in production!

New Feature: IPAM AutoDNS

Release 1.1.0 drops support for the experimental IPAM Coupling feature and replaces it by the final version of IPAM integration, IPAM AutoDNS. The main differences are:

  • IPAM AutoDNS does not require manual interaction when an IP address is created or updated. Particularly it ist not necessary to manually define the name and the zone of the address record for an IP address, but only a value in the 'DNS Name' field and a mapping from prefixes to DNS views
  • IPAM AutoDNS does not require any custom fields on IPAddress objects, but supports the relevant part of the IPAM Coupling custom fields ('Disable PTR' and 'TTL') and adds a new field 'Disable AutoDNS' to make it possible to exempt IP addresses from record generation
  • IPAM AutoDNS is not limited to one DNS record per IP address, which was a major limitation in split horizon DNS settings. It is now possible to create multiple records in zones in different views for the same IP address
  • With IPAM Coupling it was possible to create inconsistent date, i.e. by first adding a record name1.zone1 in zone example.com and then adding a new zone zone1.example.com to the DNS model. This creates a situation where the old address record can no longer be found due to the zone hierarchy. IPAM AutoDNS automatically migrates the record(s) in such cases.
  • IPAM AutoDNS no longer overwrites the 'DNS Name' field of IP addresses but uses it to create DNS records. There is one downside to this, which is that IDNs cannot be entered directly but have to be formulated in Punycode, but on the upside the 'DNS Name' field is now properly validated.

Currently there is no support for checking NetBox DNS-related permissions in IPAM actions such as creating or modifying IP addresses or prefixes. Support for model-level permissions is planned for the final release, but support for object-level permissions is probably not going to come back because of the shortcomings of Djangos permission model, which only works on form level, not on model level, while much of the actions NetBox DNS is doing behind the scenes are on model level.

Breaking Change: IPAM Coupling is deprecated and was removed

The main reason for this is that to make the migration as smooth as possible, many components of IPAM Coupling were re-used for IPAM AutoDNS. Unfortunately that breaks the IPAM Coupling functionality in a way that makes it impossible to have both installed side by side.

What's Changed

  • Include record templates if zone templates are cloned by @peteeckel in #329
  • Fixed filtering of zones by nameserver in the GUI by @peteeckel in #332
  • Implemented filtering nameservers by zone and SOA zone by @peteeckel in #333
  • Replaced list comprehension over objects by leaner query for pk by @peteeckel in #334
  • Fixed tests for NetBox 4.0.8 (new Strawberry release) by @peteeckel in #335
  • Updated the version matrix for NetBox 4.0.8 by @peteeckel in #336
  • disable_ptr must be a BooleanField in RecordForm by @peteeckel in #338
  • Fixed wrong casing of all by @peteeckel in #339
  • Check for changed custom fields in ObjectModificationMixin by @peteeckel in #342
  • Do not overwrite the contents of SOA SERIAL in ZoneForm by @peteeckel in #344

Full Changelog: 1.0.5...1.1.0-beta1

What's Changed

  • Include record templates if zone templates are cloned by @peteeckel in #329
  • Fixed filtering of zones by nameserver in the GUI by @peteeckel in #332
  • Implemented filtering nameservers by zone and SOA zone by @peteeckel in #333
  • Replaced list comprehension over objects by leaner query for pk by @peteeckel in #334
  • Fixed tests for NetBox 4.0.8 (new Strawberry release) by @peteeckel in #335
  • Updated the version matrix for NetBox 4.0.8 by @peteeckel in #336
  • disable_ptr must be a BooleanField in RecordForm by @peteeckel in #338
  • Fixed wrong casing of all by @peteeckel in #339
  • Check for changed custom fields in ObjectModificationMixin by @peteeckel in #342
  • Do not overwrite the contents of SOA SERIAL in ZoneForm by @peteeckel in #344

Full Changelog: 1.0.5...1.1.0-beta1

Feature Release: Zone Templates

22 Jul 11:52
5422db9
Compare
Choose a tag to compare

What's Changed

Full Changelog: 1.0.4...1.0.5

Bugfix Release

25 Jun 09:03
Compare
Choose a tag to compare

What's Changed

  • Fixed the nameservers representation in the GraphQL type for Zone by @peteeckel in #303

Full Changelog: 1.0.3...1.0.4

Feature/Bugfix Release

19 Jun 19:18
Compare
Choose a tag to compare

What's Changed

  • Implemented Parent/Child information in the Zone detail view by @peteeckel in #290
  • Fixed manually coded "linkify" in Zone template by @peteeckel in #291
  • Fixed rendering for the RFC2317 card in the Zone detail view by @peteeckel in #293
  • Removed additional instances of manually-coded linkify by @peteeckel in #294
  • Made the plugin menu more configurable by @peteeckel in #297
  • Provide an option to allow additional characters in zone labels by @peteeckel in #300

Full Changelog: 1.0.2...1.0.3

Deprecation Notice

The configuration variable tolerate_underscores_in_hostnames has been renamed to the more correct name tolerate_underscores_in_labels. The old name will still be accepted, but its use is deprecated. Planned removal: Version 1.2.0 (Spring 2025).

1.0.2 - Feature/Bugfix Release

06 Jun 20:46
Compare
Choose a tag to compare

What's Changed

  • Improve Documentation by @Stathogon in #274
  • Add Ansible named.conf.local generation example by @Stathogon in #276
  • Avoid saving records when nothing has changed in their values by @peteeckel in #279
  • Made default_view a boolean column in the view table by @peteeckel in #282
  • Fixed __str__ for unsaved Record objects by @peteeckel in #284
  • Added leading underscores in all labels to valid domain name patterns by @peteeckel in #286
  • Added tests for the correct handling of event rules by @peteeckel in #281

Full Changelog: 1.0.1...1.0.2

1.0.1 - Feature Release

23 May 15:23
Compare
Choose a tag to compare

What's Changed

  • Introduced stricter validation of domain names as part of record values by @peteeckel in #257
  • Re-allowed @ as value for CNAME records by @peteeckel in #259
  • Updated using_netbox_dns.md by @Stathogon in #260
  • Added validation of SOA SERIAL changes by @peteeckel in #267
  • Minor UI cleanup actions for consistency by @peteeckel in #268
  • Added documentation for SOA SERIAL checks by @peteeckel in #270
  • Included playbook to create zone files for all active zones from NetBox DNS by @Stathogon in #265

New Contributors

Full Changelog: 1.0.0...1.0.1