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

Convention on DNS Name Field #2682

New Issue
Closed
opened 2025-12-29 18:21:05 +01:00 by adam · 2 comments
adam commented 2025-12-29 18:21:05 +01:00
Owner
Copy Link

Originally created by @hSaria on GitHub (Jun 21, 2019).

Environment

  • Python version: Example: 3.6.8
  • NetBox version: Example: 2.6.0

This issue is just to point out the difference in case you missed; if this is intentional, just close the issue :)

Steps to Reproduce

  1. Edit an IP address (e.g. netbox.example.com/ipam/ip-addresses/1/edit)

Expected Behavior

It follows the current field naming convention and says (notice name is lower case):

DNS name

The help text reads:

Hostname or FQDN (case-insensitive)

Observed Behavior

Field name is:

DNS Name

Help text is:

Hostname or FQDN (not case-sensitive)
Originally created by @hSaria on GitHub (Jun 21, 2019). ### Environment * Python version: Example: 3.6.8 * NetBox version: Example: 2.6.0 This issue is just to point out the difference in case you missed; if this is intentional, just close the issue :) ### Steps to Reproduce 1. Edit an IP address (e.g. `netbox.example.com/ipam/ip-addresses/1/edit`) ### Expected Behavior It follows the current field naming convention and says (notice `name` is lower case): ``` DNS name ``` The help text reads: ``` Hostname or FQDN (case-insensitive) ``` ### Observed Behavior Field name is: ``` DNS Name ``` Help text is: ``` Hostname or FQDN (not case-sensitive) ```
adam closed this issue 2025-12-29 18:21:05 +01:00
adam commented 2025-12-29 18:21:06 +01:00
Author
Owner
Copy Link

@hSaria commented on GitHub (Jun 21, 2019):

Any required changes should be at line 581 in ./netbox/ipam/models.py.

@hSaria commented on GitHub (Jun 21, 2019): Any required changes should be at line 581 in `./netbox/ipam/models.py`.
adam commented 2025-12-29 18:21:06 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 21, 2019):

This is fine as-is.

@jeremystretch commented on GitHub (Jun 21, 2019): This is fine as-is.
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#2682
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?