starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Allow two hostnames under DNS Name #3345

New Issue
Closed
opened 2025-12-29 18:28:04 +01:00 by adam · 1 comment
adam commented 2025-12-29 18:28:04 +01:00
Owner
Copy Link

Originally created by @rivest1000 on GitHub (Feb 19, 2020).

Environment

  • Python version: Python 2.7.13
  • NetBox version: v2.6.7

Proposed Functionality

Please allow multiple FQDN's (separated by commas) under DNS name field so that we can have many A records in DNS for one IP address

Use Case

We have a python script that scrapes our netbox API everyday for IP addresses and their hostnames associated with them. It creates zone files that is used for unbound/nsd. Right now, in order to have two A records for one IP, we have to create a VIP role for that IP and assign the IP twice and create a hostname for each one. It would make it much easier to have the IP listed in the DB one time with two hostnames associated with it.

Database Changes

External Dependencies

Originally created by @rivest1000 on GitHub (Feb 19, 2020). <!-- Request for allowing 2 Hostnames or FQDNs under DNS Name field in IP address edit. --> ### Environment * Python version: Python 2.7.13 * NetBox version: v2.6.7 ### Proposed Functionality Please allow multiple FQDN's (separated by commas) under DNS name field so that we can have many A records in DNS for one IP address ### Use Case We have a python script that scrapes our netbox API everyday for IP addresses and their hostnames associated with them. It creates zone files that is used for unbound/nsd. Right now, in order to have two A records for one IP, we have to create a VIP role for that IP and assign the IP twice and create a hostname for each one. It would make it much easier to have the IP listed in the DB one time with two hostnames associated with it. ### Database Changes <!-- N/A --> ### External Dependencies <!-- N/A -->
adam closed this issue 2025-12-29 18:28:05 +01:00
adam commented 2025-12-29 18:28:05 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 19, 2020):

NetBox is not intended to be used as a full DNS management application. The dns_name field is provided as a convenience to hold a single name only, and employs validation to enforce this.

@jeremystretch commented on GitHub (Feb 19, 2020): NetBox is not intended to be used as a full DNS management application. The `dns_name` field is provided as a convenience to hold a single name only, and employs validation to enforce this.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#3345
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?