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

add DNS name per interface #5226

New Issue
Closed
opened 2025-12-29 19:25:38 +01:00 by adam · 6 comments
adam commented 2025-12-29 19:25:38 +01:00
Owner
Copy Link

Originally created by @rafalfitt on GitHub (Aug 24, 2021).

NetBox version

v2.11.7

Feature type

New functionality

Proposed functionality

a new option would be useful: DNS name per interface

In my setup I have separately DNS entries (A + AAAA) assigned to specific addresses (for example 192.168.1.2 + xxxx::102) and registered as ip-1-2.example.com - I want to treat it as a fixed triad.

Use case

it covers a scenario of the multiple ipv4 + ipv6 addresses assigned to a given interface.
+
MS Windows devices have a "Register this connection's addresses in DNS" option

Database changes

No response

External dependencies

No response

Originally created by @rafalfitt on GitHub (Aug 24, 2021). ### NetBox version v2.11.7 ### Feature type New functionality ### Proposed functionality a new option would be useful: DNS name per interface In my setup I have separately DNS entries (A + AAAA) assigned to specific addresses (for example 192.168.1.2 + xxxx::102) and registered as ip-1-2.example.com - I want to treat it as a fixed triad. ### Use case it covers a scenario of the multiple ipv4 + ipv6 addresses assigned to a given interface. + MS Windows devices have a "Register this connection's addresses in DNS" option ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 19:25:38 +01:00
adam closed this issue 2025-12-29 19:25:38 +01:00
adam commented 2025-12-29 19:25:39 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Aug 24, 2021):

If you need more advanced DNS management, I think either custom fields or a custom plugin would be best suited for your use case.

@DanSheps commented on GitHub (Aug 24, 2021): If you need more advanced DNS management, I think either custom fields or a custom plugin would be best suited for your use case.
adam commented 2025-12-29 19:25:39 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 24, 2021):

In my setup I have separately DNS entries (A + AAAA) assigned to specific addresses (for example 192.168.1.2 + xxxx::102) and registered as ip-1-2.example.com - I want to treat it as a fixed triad.

You'll need to assign DNS entries to the IPs associated with the interface(s). There's no direct correlation between a DNS record and an interface in the real world.

@jeremystretch commented on GitHub (Aug 24, 2021): > In my setup I have separately DNS entries (A + AAAA) assigned to specific addresses (for example 192.168.1.2 + xxxx::102) and registered as ip-1-2.example.com - I want to treat it as a fixed triad. You'll need to assign DNS entries to the IPs associated with the interface(s). There's no direct correlation between a DNS record and an interface in the real world.
adam commented 2025-12-29 19:25:39 +01:00
Author
Owner
Copy Link

@rafalfitt commented on GitHub (Aug 25, 2021):

"There's no direct correlation between a DNS record and an interface in the real world."

MS Windows devices have a "Register this connection's addresses in DNS" option - is it the real world?

@rafalfitt commented on GitHub (Aug 25, 2021): "There's no direct correlation between a DNS record and an interface in the real world." MS Windows devices have a "Register this connection's addresses in DNS" option - is it the real world?
adam commented 2025-12-29 19:25:39 +01:00
Author
Owner
Copy Link

@rafalfitt commented on GitHub (Aug 25, 2021):

"If you need more advanced DNS management, I think either custom fields or a custom plugin would be best suited for your use case."

well, there is a DNS name field in properties of an address. Adding a similar DNS name field as an interface property is not an advanced management, I hope.

@rafalfitt commented on GitHub (Aug 25, 2021): "If you need more advanced DNS management, I think either custom fields or a custom plugin would be best suited for your use case." well, there is a DNS name field in properties of an address. Adding a similar DNS name field as an interface property is not an advanced management, I hope.
adam commented 2025-12-29 19:25:40 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 25, 2021):

MS Windows devices have a "Register this connection's addresses in DNS" option - is it the real world?

Exactly: it's registering the connection's addresses, not the connection itself. NetBox supports this to the extent that DNS names can be applied to IP addresses. Anything beyond that is out of scope for the product currently.

@jeremystretch commented on GitHub (Aug 25, 2021): > MS Windows devices have a "Register this connection's addresses in DNS" option - is it the real world? Exactly: it's registering the connection's _addresses_, not the connection itself. NetBox supports this to the extent that DNS names can be applied to IP addresses. Anything beyond that is out of scope for the product currently.
adam commented 2025-12-29 19:25:40 +01:00
Author
Owner
Copy Link

@rafalfitt commented on GitHub (Aug 25, 2021):

but the setting and the name granularity is per interface, not per IP address.
it is enabled or disabled for the interface.

@rafalfitt commented on GitHub (Aug 25, 2021): but the setting and the name granularity is per interface, not per IP address. it is enabled or disabled for the interface.
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 type: feature
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#5226
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?