netbox-plugin-dns 1.0b1__tar.gz → 1.0b2__tar.gz

{netbox_plugin_dns-1.0b1 → netbox_plugin_dns-1.0b2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: netbox-plugin-dns
-Version: 1.0b1
+Version: 1.0b2
 Summary: NetBox DNS is a NetBox plugin for managing DNS data.
 Home-page: https://github.com/peteeckel/netbox-plugin-dns
 License: MIT
@@ -34,16 +34,30 @@ The NetBox DNS plugin enables NetBox to manage operational DNS data such as name
 <a href="https://pepy.tech/project/netbox-plugin-dns"><img alt="Downloads/Month" src="https://static.pepy.tech/badge/netbox-plugin-dns/week"></a>
 </div>
 
-## Features
+## Objectives
+NetBox DNS is designed to be the 'DNS Source of Truth' analogous to NetBox being the 'Network Source of Truth'.
 
-* Manage name servers, zones and records
-* Automatically generate SOA and NS records for zones
-* Automatically create and update PTR records for IPv4 and IPv6 address records
-* Organize DNS zones in views for split horizon DNS and multi-site deployments
-* Manage domain registrar and registrant information for domains related to zones
-* Manage RFC2317 reverse zones for IPv4 prefixes with a network mask length longer than 24 bits
+The plugin holds information about DNS name servers, DNS Views and Zones, and DNS Records, making it a data source for automatically provisioning DNS instances. Registrarion information about DNS registrars and contacts for DNS domains can also be stored and associated with zones.
 
-NetBox DNS is using the standardized NetBox plugin interface, so it also takes advantage of the NetBox tagging and change log features.
+The main focus of the plugin is to ensure the quality of data stored in it. To achieve this, many validation and automation mechanisms are in place:
+
+* Validation of record names and values
+* Automatic maintenance of PTR records for IPv6 and IPv4 address records
+* Automatic generation of SOA records, optionally including the serial number of the zone data
+* Validation of record types such as CNAME and singletons, to ensure DNS zone validity
+* [RFC 2317](https://datatracker.ietf.org/doc/html/rfc2317) support for delegation of PTR zones for IPv4 subnets longer than 24 bits
+
+Other main features are:
+
+* Support for BIND views, providing lightweight namespaces for zones
+* Support for IDN, inclucing the validation of punycode names
+* Fully supported NetBox REST and GraphQL API
+* Support for all major NetBox features like Global Search, Tenancy, Change Logs, Tagging, Journaling etc.
+
+## Non-Objectives
+In the same way in which NetBox is not a network management application, NetBox DNS does not provide functionality to manage specific name servers or DNS service providers or generate input like configuration and zone files for them. The focus is on the completeness and integrity of the data needed to run DNS zones, not on the peculiarities of a plethora of servers and services actually using the data. This functionality is left to specialized integration tools, or in many cases it can be easily implemented using Ansible or similar tools based on NetBox DNS data. Example code for some simple use cases is provided.
+
+For integration with a large number of DNS server implementations integration tools like [octodns-netbox-dns](https://pypi.org/project/octodns-netbox-dns/) are available.
 
 ## Requirements
 

{netbox_plugin_dns-1.0b1 → netbox_plugin_dns-1.0b2}/README.md

@@ -14,16 +14,30 @@ The NetBox DNS plugin enables NetBox to manage operational DNS data such as name
 <a href="https://pepy.tech/project/netbox-plugin-dns"><img alt="Downloads/Month" src="https://static.pepy.tech/badge/netbox-plugin-dns/week"></a>
 </div>
 
-## Features
+## Objectives
+NetBox DNS is designed to be the 'DNS Source of Truth' analogous to NetBox being the 'Network Source of Truth'.
 
-* Manage name servers, zones and records
-* Automatically generate SOA and NS records for zones
-* Automatically create and update PTR records for IPv4 and IPv6 address records
-* Organize DNS zones in views for split horizon DNS and multi-site deployments
-* Manage domain registrar and registrant information for domains related to zones
-* Manage RFC2317 reverse zones for IPv4 prefixes with a network mask length longer than 24 bits
+The plugin holds information about DNS name servers, DNS Views and Zones, and DNS Records, making it a data source for automatically provisioning DNS instances. Registrarion information about DNS registrars and contacts for DNS domains can also be stored and associated with zones.
 
-NetBox DNS is using the standardized NetBox plugin interface, so it also takes advantage of the NetBox tagging and change log features.
+The main focus of the plugin is to ensure the quality of data stored in it. To achieve this, many validation and automation mechanisms are in place:
+
+* Validation of record names and values
+* Automatic maintenance of PTR records for IPv6 and IPv4 address records
+* Automatic generation of SOA records, optionally including the serial number of the zone data
+* Validation of record types such as CNAME and singletons, to ensure DNS zone validity
+* [RFC 2317](https://datatracker.ietf.org/doc/html/rfc2317) support for delegation of PTR zones for IPv4 subnets longer than 24 bits
+
+Other main features are:
+
+* Support for BIND views, providing lightweight namespaces for zones
+* Support for IDN, inclucing the validation of punycode names
+* Fully supported NetBox REST and GraphQL API
+* Support for all major NetBox features like Global Search, Tenancy, Change Logs, Tagging, Journaling etc.
+
+## Non-Objectives
+In the same way in which NetBox is not a network management application, NetBox DNS does not provide functionality to manage specific name servers or DNS service providers or generate input like configuration and zone files for them. The focus is on the completeness and integrity of the data needed to run DNS zones, not on the peculiarities of a plethora of servers and services actually using the data. This functionality is left to specialized integration tools, or in many cases it can be easily implemented using Ansible or similar tools based on NetBox DNS data. Example code for some simple use cases is provided.
+
+For integration with a large number of DNS server implementations integration tools like [octodns-netbox-dns](https://pypi.org/project/octodns-netbox-dns/) are available.
 
 ## Requirements
 

{netbox_plugin_dns-1.0b1 → netbox_plugin_dns-1.0b2}/netbox_dns/__init__.py

@@ -1,6 +1,6 @@
 from netbox.plugins import PluginConfig
 
-__version__ = "1.0-beta1"
+__version__ = "1.0-beta2"
 
 
 class DNSConfig(PluginConfig):

{netbox_plugin_dns-1.0b1 → netbox_plugin_dns-1.0b2}/netbox_dns/api/serializers_/zone.py

@@ -13,17 +13,6 @@ from netbox_dns.models import Zone
 
 
 class ZoneSerializer(NetBoxModelSerializer):
-    # +
-    # This is a hack to avoid the exception raised by the UniqueTogetherValidator
-    # after NetBox commit https://github.com/netbox-community/netbox/commit/78e284c
-    #
-    # See https://github.com/netbox-community/netbox/issues/15351 for details.
-    # -
-    def __init__(self, *args, **kwargs):
-        super().__init__(*args, **kwargs)
-        if self.nested:
-            self.validators = []
-
     url = serializers.HyperlinkedIdentityField(
         view_name="plugins-api:netbox_dns-api:zone-detail"
     )

{netbox_plugin_dns-1.0b1 → netbox_plugin_dns-1.0b2}/netbox_dns/management/commands/cleanup_rrset_ttl.py

@@ -32,7 +32,7 @@ class Command(BaseCommand):
         ttl_records = (
             Record.objects.filter(ttl__isnull=False)
             .exclude(type=RecordTypeChoices.SOA)
-            .exclude(type=RecordTypeChoices.PTR, maanged=True)
+            .exclude(type=RecordTypeChoices.PTR, managed=True)
         )
         for record in ttl_records:
             records = Record.objects.filter(

{netbox_plugin_dns-1.0b1 → netbox_plugin_dns-1.0b2}/netbox_dns/models/record.py

@@ -754,7 +754,8 @@ class Record(NetBoxModel):
 class RecordIndex(SearchIndex):
     model = Record
     fields = (
-        ("name", 100),
+        ("fqdn", 100),
+        ("name", 120),
         ("value", 150),
         ("zone", 200),
         ("type", 200),

{netbox_plugin_dns-1.0b1 → netbox_plugin_dns-1.0b2}/netbox_dns/views/record.py

@@ -41,22 +41,15 @@ class RecordView(generic.ObjectView):
     queryset = Record.objects.all().prefetch_related("zone", "ptr_record")
 
     def get_value_records(self, instance):
-        value_fqdn = dns_name.from_text(instance.value_fqdn)
-        value_zone_names = [
-            value_fqdn.split(length)[1].to_text().rstrip(".")
-            for length in range(2, len(value_fqdn) + 1)
-        ]
-
-        value_zone = (
-            Zone.objects.filter(instance.zone.view_filter, name__in=value_zone_names)
-            .order_by(Length("name").desc())
-            .first()
+        view_filter = (
+            Q(zone__view__isnull=True)
+            if instance.zone.view is None
+            else Q(zone__view=instance.zone.view)
         )
-        if not value_zone:
-            return None
 
-        value_name = value_fqdn.relativize(dns_name.from_text(value_zone.name))
-        cname_targets = Record.objects.filter(zone=value_zone, name=value_name)
+        value_fqdn = dns_name.from_text(instance.value_fqdn)
+
+        cname_targets = Record.objects.filter(view_filter, fqdn=value_fqdn)
 
         if cname_targets:
             return RelatedRecordTable(

{netbox_plugin_dns-1.0b1 → netbox_plugin_dns-1.0b2}/pyproject.toml

@@ -1,6 +1,6 @@
 [tool.poetry]
 name = "netbox-plugin-dns"
-version = "1.0-beta1"
+version = "1.0-beta2"
 description = "NetBox DNS is a NetBox plugin for managing DNS data."
 authors = ["Peter Eckel <pete@netbox-dns.org>"]
 homepage = "https://github.com/peteeckel/netbox-plugin-dns"