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

permit mixed case in dns_name field #7391

New Issue
Closed
opened 2025-12-29 20:22:48 +01:00 by adam · 5 comments
adam commented 2025-12-29 20:22:48 +01:00
Owner
Copy Link

Originally created by @olafhering on GitHub (Dec 20, 2022).

NetBox version

v3.3.7

Feature type

Change to existing functionality

Proposed functionality

As noted in #11220 all data arriving in the dns_name field are forced to lower case.
commit e1bca52d57 gave no reason why it was done that way.

All hostnames, and also all FQDN, are meant for human consumption. A DNS zone admin is free to send any (valid) FQDN string for the reverse lookup of an IP address, which includes mixed case.

(DNS itself of course remains to be case-insensitive. The Net would be cumbersome to work with if the names were case sensitive...)

Use case

My usage of netbox will include building the zone files for a DNS zone from data in a local netbox instance. This is currently blocking me because existing mixed-case strings would be corrupted, by being forced to be all lower case.

Database changes

No response

External dependencies

No response

Originally created by @olafhering on GitHub (Dec 20, 2022). ### NetBox version v3.3.7 ### Feature type Change to existing functionality ### Proposed functionality As noted in #11220 all data arriving in the `dns_name` field are forced to lower case. commit e1bca52d57440ceecded5387d35a82e17a77f845 gave no reason why it was done that way. All hostnames, and also all FQDN, are meant for human consumption. A DNS zone admin is free to send any (valid) FQDN string for the reverse lookup of an IP address, which includes mixed case. (DNS itself of course remains to be case-insensitive. The Net would be cumbersome to work with if the names were case sensitive...) ### Use case My usage of netbox will include building the zone files for a DNS zone from data in a local netbox instance. This is currently blocking me because existing mixed-case strings would be corrupted, by being forced to be all lower case. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 20:22:48 +01:00
adam closed this issue 2025-12-29 20:22:48 +01:00
adam commented 2025-12-29 20:22:50 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 22, 2022):

This is currently blocking me because existing mixed-case strings would be corrupted, by being forced to be all lower case.

DNS itself is case-insensitive. Why would you need store case-sensitive records?

@jeremystretch commented on GitHub (Dec 22, 2022): > This is currently blocking me because existing mixed-case strings would be corrupted, by being forced to be all lower case. DNS itself is case-insensitive. Why would you need store case-sensitive records?
adam commented 2025-12-29 20:22:52 +01:00
Author
Owner
Copy Link

@olafhering commented on GitHub (Dec 22, 2022):

The command host 1.2.3.4 will return MyHostName.sub.dom.tld. because such info is stored in the reverse zone of sub.dom.tld.
I would like to store such hostname in netbox verbatim, to be able to build the relevant DNS zones from netbox data.

@olafhering commented on GitHub (Dec 22, 2022): The command `host 1.2.3.4` will return `MyHostName.sub.dom.tld.` because such info is stored in the reverse zone of `sub.dom.tld`. I would like to store such hostname in netbox verbatim, to be able to build the relevant DNS zones from netbox data.
adam commented 2025-12-29 20:22:52 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 22, 2022):

to be able to build the relevant DNS zones from netbox data

This isn't a supported use case for the core NetBox application; the dns_name field exists merely as a means of correlation for external consumers. If you're interested in managing DNS records in NetBox, consider the netbox-dns plugin.

@jeremystretch commented on GitHub (Dec 22, 2022): > to be able to build the relevant DNS zones from netbox data This isn't a supported use case for the core NetBox application; the `dns_name` field exists merely as a means of correlation for external consumers. If you're interested in managing DNS records in NetBox, consider the [netbox-dns](https://github.com/auroraresearchlab/netbox-dns) plugin.
adam commented 2025-12-29 20:22:53 +01:00
Author
Owner
Copy Link

@olafhering commented on GitHub (Dec 22, 2022):

Sorry, I already have my tooling to maintain dns.
Until the dns_name field returns verbatim data, I will use the existing description field, which returns the data entered into it verbatim.

@olafhering commented on GitHub (Dec 22, 2022): Sorry, I already have my tooling to maintain dns. Until the `dns_name` field returns verbatim data, I will use the existing `description` field, which returns the data entered into it verbatim.
adam commented 2025-12-29 20:22:53 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 22, 2022):

Sounds like you've found a solution that fits your needs then. I'll go ahead and close this out.

@jeremystretch commented on GitHub (Dec 22, 2022): Sounds like you've found a solution that fits your needs then. I'll go ahead and close this out.
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#7391
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?