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

NAPALM Hostname split at . #7029

New Issue
Closed
opened 2025-12-29 19:48:04 +01:00 by adam · 2 comments
adam commented 2025-12-29 19:48:04 +01:00
Owner
Copy Link

Originally created by @b66renr on GitHub (Sep 26, 2022).

NetBox version

v3.3.4

Feature type

Change to existing functionality

Proposed functionality

Hello! I'm setting up Netbox for an existing ISP network, and have run into the issue mentioned in #1810, where hostnames are split at the first .
I see an open issue for this with interface names, but only the previous one for device hostname. Apologies if I've missed any.

I understand the issue, where devices are adding their domain name to the end (and our Juniper devices do it), but this adds an issue depending on how hostnames are built (not an easy change). Random examples, rtr1.london.uk, and rtr1.nyc.us both become rtr1.

There were a few comments after #1810 was rejected with some suggestions. Would it be possible to look into either of these options, being:

  • Platforms can have options to not strip domain (less friendly as it requires putting the domain into the device name)
  • Having a configuration option somewhere to specify the domain name section of the hostname, that will then be removed.

Thanks

Use case

Hostnames with . in would work correctly in LLDP neighbors. Currently, all devices show in red in the LLDP neighbors page indicating a mismatch.

Database changes

Likely new field(s) in Platforms, if done this way, or maybe new config option "NAPALM_DOMAIN_NAME".

External dependencies

No response

Originally created by @b66renr on GitHub (Sep 26, 2022). ### NetBox version v3.3.4 ### Feature type Change to existing functionality ### Proposed functionality Hello! I'm setting up Netbox for an existing ISP network, and have run into the issue mentioned in #1810, where hostnames are split at the first . I see an open issue for this with interface names, but only the previous one for device hostname. Apologies if I've missed any. I understand the issue, where devices are adding their domain name to the end (and our Juniper devices do it), but this adds an issue depending on how hostnames are built (not an easy change). Random examples, rtr1.london.uk, and rtr1.nyc.us both become rtr1. There were a few comments after #1810 was rejected with some suggestions. Would it be possible to look into either of these options, being: - Platforms can have options to not strip domain (less friendly as it requires putting the domain into the device name) - Having a configuration option somewhere to specify the domain name section of the hostname, that will then be removed. Thanks ### Use case Hostnames with . in would work correctly in LLDP neighbors. Currently, all devices show in red in the LLDP neighbors page indicating a mismatch. ### Database changes Likely new field(s) in Platforms, if done this way, or maybe new config option "NAPALM_DOMAIN_NAME". ### External dependencies _No response_
adam added the type: featurestatus: blocked labels 2025-12-29 19:48:04 +01:00
adam closed this issue 2025-12-29 19:48:05 +01:00
adam commented 2025-12-29 19:48:05 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 2, 2022):

Marking as blocked pending #10520

@jeremystretch commented on GitHub (Nov 2, 2022): Marking as blocked pending #10520
adam commented 2025-12-29 19:48:05 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 16, 2023):

Closing this out as NAPALM integration is being moved to a plugin in NetBox v3.5.

@jeremystretch commented on GitHub (Mar 16, 2023): Closing this out as NAPALM integration is being moved to a plugin in NetBox v3.5.
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 status: blocked 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#7029
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?