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

Having more than 64 characters in virtual-machine-name field #1619

New Issue
Closed
opened 2025-12-29 16:33:32 +01:00 by adam · 2 comments
adam commented 2025-12-29 16:33:32 +01:00
Owner
Copy Link

Originally created by @mabazyar on GitHub (Mar 9, 2018).

Issue type

[X] Feature request
[] Bug report
[ ] Documentation

Environment

  • Python version: 3.5.2
  • NetBox version: v2.3.1

Description

It would be great if the virtual-machine-name length could be bumped up to 100 to support super-long FQDNs.

Putting more details, I face the following API error for such use cases.

"name": ["Ensure this field has no more than 64 characters."]
Originally created by @mabazyar on GitHub (Mar 9, 2018). ### Issue type [X] Feature request [] Bug report [ ] Documentation ### Environment * Python version: 3.5.2 * NetBox version: v2.3.1 ### Description It would be great if the virtual-machine-name length could be bumped up to 100 to support super-long FQDNs. Putting more details, I face the following API error for such use cases. ``` "name": ["Ensure this field has no more than 64 characters."] ```
adam closed this issue 2025-12-29 16:33:32 +01:00
adam commented 2025-12-29 16:33:33 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 12, 2018):

The name field is only for the VM's hostname, not its entire FQDN. 64 characters is sufficient for this purpose. Any implementation of a domain info would fall under #166.

@jeremystretch commented on GitHub (Mar 12, 2018): The name field is only for the VM's hostname, not its entire FQDN. 64 characters is sufficient for this purpose. Any implementation of a domain info would fall under #166.
adam commented 2025-12-29 16:33:33 +01:00
Author
Owner
Copy Link

@kartiksubbarao commented on GitHub (Oct 2, 2019):

I don't see how you can add VMs named test.domain1.example.com and test.domain2.example.com into Netbox if you only use the hostname portion of the FQDN. Once you added the first one as 'test', Netbox would not allow you to add another VM named 'test'.

I think it would be highly valuable if Netbox tolerated FQDNs in the name field and correspondingly increased the name length to 255 (as per RFC 1035).

@kartiksubbarao commented on GitHub (Oct 2, 2019): I don't see how you can add VMs named **test.domain1.example.com** and **test.domain2.example.com** into Netbox if you only use the hostname portion of the FQDN. Once you added the first one as 'test', Netbox would not allow you to add another VM named 'test'. I think it would be highly valuable if Netbox tolerated FQDNs in the name field and correspondingly increased the name length to 255 (as per RFC 1035).
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#1619
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?