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

Devices - Virtual Chassis Domain Name field length #9481

New Issue
Closed
opened 2025-12-29 20:50:32 +01:00 by adam · 1 comment
adam commented 2025-12-29 20:50:32 +01:00
Owner
Copy Link

Originally created by @mprindle8598 on GitHub (Apr 15, 2024).

NetBox version

v3.7.3

Feature type

Change to existing functionality

Proposed functionality

Per bug entry #15713 the domain name field length is limited to 30 characters by design. Per RFC 1035, section 2.3.4 the maximum size of the name can be "255 octets or less". After taking into account encoding, this could leave a potential max of 253 usable characters.

I would propose increasing the max of the Device - Virtual Chassis - Domain Name field length to 253. This would be in-line with the RFC.

Use case

This would allow longer FQDN's to be used and still fall with in the RFC spec for naming. In our use case we utilize a multitude of domain names with multiple subdomains under them. In several cases the FQDN is longer than the current field length preventing us from fully documenting the FQDN associated with the chassis.

Database changes

No response

External dependencies

No response

Originally created by @mprindle8598 on GitHub (Apr 15, 2024). ### NetBox version v3.7.3 ### Feature type Change to existing functionality ### Proposed functionality Per bug entry #15713 the domain name field length is limited to 30 characters by design. Per [RFC 1035, section 2.3.4](https://datatracker.ietf.org/doc/html/rfc1035#section-2.3.4) the maximum size of the name can be "255 octets or less". After taking into account encoding, this could leave a potential max of 253 usable characters. I would propose increasing the max of the Device - Virtual Chassis - Domain Name field length to 253. This would be in-line with the RFC. ### Use case This would allow longer FQDN's to be used and still fall with in the RFC spec for naming. In our use case we utilize a multitude of domain names with multiple subdomains under them. In several cases the FQDN is longer than the current field length preventing us from fully documenting the FQDN associated with the chassis. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 20:50:32 +01:00
adam closed this issue 2025-12-29 20:50:32 +01:00
adam commented 2025-12-29 20:50:33 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 15, 2024):

A virtual chassis domain is not a domain name and thus RFC 1035 has no relevance. (The VC domain field should not be confused with a device's configured domain name used for DNS resolution.) Cisco IOS, for instance, permits the configuration of a numeric domain ID; other platforms may permit other formats but will employ a domain for the same reasons.

@jeremystretch commented on GitHub (Apr 15, 2024): A virtual chassis domain is not a domain name and thus RFC 1035 has no relevance. (The VC `domain` field should not be confused with a device's configured domain name used for DNS resolution.) Cisco IOS, for instance, permits the configuration of a numeric domain ID; other platforms may permit other formats but will employ a domain for the same reasons.
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#9481
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?