SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-03-31 06:34:19 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

netbird dns resolution does not work with capital letters #1609

New Issue
Open
opened 2025-11-20 05:33:46 -05:00 by saavagebueno · 0 comments
saavagebueno commented 2025-11-20 05:33:46 -05:00
Owner
Copy Link

Originally created by @sarahsevee on GitHub (Feb 10, 2025).

Describe the problem

Netbird dns resolution only works, if all characters of a hostname are in lowercase on the client, irregardless how the name is capitalized in netbird. If a single letter of the name is capitalized, it will not find it. This happens in both Windows and MacOS, Linux does not seem to be affected. Tested with both nslookup and ping.

RDP/SSH also do not work, if used with capitalized names.

Once a lowercase name has been resolved on the client OS, capitalization is not an issue anymore, as long as the dns entry is cached.

nslookup output:

user@MacBook-Air ~ % nslookup
> TEST
Server:		100.84.255.254
Address:	100.84.255.254#53

** server can't find TEST: NXDOMAIN
> test
Server:		100.84.255.254
Address:	100.84.255.254#53

Non-authoritative answer:
Name:	test.nb.xxx
Address: 100.84.94.92
> Test
Server:		100.84.255.254
Address:	100.84.255.254#53

** server can't find Test: NXDOMAIN
> test
Server:		100.84.255.254
Address:	100.84.255.254#53

Non-authoritative answer:
Name:	test.nb.xxx
Address: 100.84.94.92
> tesT
Server:		100.84.255.254
Address:	100.84.255.254#53

** server can't find tesT: NXDOMAIN
> test
Server:		100.84.255.254
Address:	100.84.255.254#53

Non-authoritative answer:
Name:	test.nb.xxx
Address: 100.84.94.92
> TEST
#Server:		100.84.255.254
Address:	100.84.255.254#53

** server can't find TEST: NXDOMAIN

ping output:

user@MacBook-Air ~ % ping TEST
ping: cannot resolve TEST: Unknown host

user@MacBook-Air ~ % ping test
PING test.nb.xxx (100.84.94.92): 56 data bytes
64 bytes from 100.84.94.92: icmp_seq=0 ttl=64 time=88.732 ms

user@MacBook-Air ~ % ping TEST
PING test.nb.xxx (100.84.94.92): 56 data bytes
64 bytes from 100.84.94.92: icmp_seq=0 ttl=64 time=86.653 ms

Expected behavior

Any form of capitalization of a hostname should work.

Are you using NetBird Cloud?

Self-Hosted

NetBird version

OS: darwin/arm64
Daemon version: 0.36.5
CLI version: 0.36.5

Additional context

Add any other context about the problem here.

Originally created by @sarahsevee on GitHub (Feb 10, 2025). **Describe the problem** Netbird dns resolution only works, if all characters of a hostname are in lowercase on the client, irregardless how the name is capitalized in netbird. If a single letter of the name is capitalized, it will not find it. This happens in both Windows and MacOS, Linux does not seem to be affected. Tested with both nslookup and ping. RDP/SSH also do not work, if used with capitalized names. Once a lowercase name has been resolved on the client OS, capitalization is not an issue anymore, as long as the dns entry is cached. nslookup output: ```` user@MacBook-Air ~ % nslookup > TEST Server: 100.84.255.254 Address: 100.84.255.254#53 ** server can't find TEST: NXDOMAIN > test Server: 100.84.255.254 Address: 100.84.255.254#53 Non-authoritative answer: Name: test.nb.xxx Address: 100.84.94.92 > Test Server: 100.84.255.254 Address: 100.84.255.254#53 ** server can't find Test: NXDOMAIN > test Server: 100.84.255.254 Address: 100.84.255.254#53 Non-authoritative answer: Name: test.nb.xxx Address: 100.84.94.92 > tesT Server: 100.84.255.254 Address: 100.84.255.254#53 ** server can't find tesT: NXDOMAIN > test Server: 100.84.255.254 Address: 100.84.255.254#53 Non-authoritative answer: Name: test.nb.xxx Address: 100.84.94.92 > TEST #Server: 100.84.255.254 Address: 100.84.255.254#53 ** server can't find TEST: NXDOMAIN ```` ping output: ```` user@MacBook-Air ~ % ping TEST ping: cannot resolve TEST: Unknown host user@MacBook-Air ~ % ping test PING test.nb.xxx (100.84.94.92): 56 data bytes 64 bytes from 100.84.94.92: icmp_seq=0 ttl=64 time=88.732 ms user@MacBook-Air ~ % ping TEST PING test.nb.xxx (100.84.94.92): 56 data bytes 64 bytes from 100.84.94.92: icmp_seq=0 ttl=64 time=86.653 ms ```` **Expected behavior** Any form of capitalization of a hostname should work. **Are you using NetBird Cloud?** Self-Hosted **NetBird version** OS: darwin/arm64 Daemon version: 0.36.5 CLI version: 0.36.5 **Additional context** Add any other context about the problem here.
saavagebueno added the clientdns labels 2025-11-20 05:33:46 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
2021 Q4
2022 Q1
2022 Q1
accessibility
acl
agent
agent
Android
Android
api
authentik
automation
azure
battery-usage
bug
cache
client
client-ui
cloud
cloud-only
cloudflare
community
compatibility
config-idp
config-issue
connection
contribution
coturn
cross-vpn
dashboard
data-usage
distribution
dns
docker
documentation
duplicate
enhancement
enhancement
event-stream
feature-request
freebsd
getting-started
go
good first issue
gui
help wanted
home-assistant
idp
inconsistency
integration
integrations
ios
ipv6
jwt
k8s
keycloak
linux
login
macos
management-service
missing-docs
mobile
moved-internal
needs-review
netbird-ui
networking
new-platform
nginx
notification
okta
openwrt
packaging
peer-management
peer-management
peer-management
performance
postgres
posture-checks
psk
pull-request
Mirrored from GitHub Pull Request
 question
refactor
relay
release
rfc
routes
security
security-related
self-hosting
server
signal
sleep-issue
ssh
ssl
status
store
synology
system-compatibility-issue
test-suite
third-party-integration
triage
triage-needed
troubleshooting
UX
waiting-feedback
windows
wontfix
zitadel
No Label client dns
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#1609
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?