Allow Multiple DNS Names for a Single IP Address (Convert dns_name to List Field) #11922

Closed
opened 2025-12-29 21:51:32 +01:00 by adam · 1 comment
Owner

Originally created by @xxixo on GitHub (Dec 12, 2025).

NetBox version

v4.4.8

Feature type

Change to existing functionality

Proposed functionality

Currently, the IPAddress model supports only a single dns_name value (string field).
I propose extending this design to enable assigning multiple DNS names to a single IP address.

Use case

Many operational environments map multiple DNS records to the same IP address, such as:

  • multiple A-records for applications (e.g., www.example.com, api.example.com);
  • multiple service-specific hostnames pointing to one reverse proxy or load balancer;

Database changes

Modify the IPAddress model by replacing the existing dns_name field (string) with a list-type field capable of storing multiple DNS names.

  • Convert the current dns_name (CharField) to ArrayField(CharField)

External dependencies

No new external dependencies are required.

Originally created by @xxixo on GitHub (Dec 12, 2025). ### NetBox version v4.4.8 ### Feature type Change to existing functionality ### Proposed functionality Currently, the IPAddress model supports only a single `dns_name` value (string field). I propose extending this design to enable assigning multiple DNS names to a single IP address. ### Use case Many operational environments map multiple DNS records to the same IP address, such as: - multiple A-records for applications (e.g., www.example.com, api.example.com); - multiple service-specific hostnames pointing to one reverse proxy or load balancer; ### Database changes Modify the IPAddress model by replacing the existing `dns_name` field (string) with a list-type field capable of storing multiple DNS names. - Convert the current dns_name (`CharField`) to `ArrayField(CharField)` ### External dependencies No new external dependencies are required.
adam added the type: featurenetbox labels 2025-12-29 21:51:32 +01:00
adam closed this issue 2025-12-29 21:51:32 +01:00
Author
Owner

@jeremystretch commented on GitHub (Dec 14, 2025):

The proposed functionality is beyond the intended scope of the IPAddress model. If you need to manage more complex DNS records, consider a plugin such as netbox-plugin-dns.

@jeremystretch commented on GitHub (Dec 14, 2025): The proposed functionality is beyond the intended scope of the IPAddress model. If you need to manage more complex DNS records, consider a plugin such as [netbox-plugin-dns](https://github.com/peteeckel/netbox-plugin-dns).
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#11922