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

DNS server doesn't handle domain name capitalisation correctly #980

New Issue
Open
opened 2025-11-20 05:20:57 -05:00 by saavagebueno · 2 comments
saavagebueno commented 2025-11-20 05:20:57 -05:00
Owner
Copy Link

Originally created by @tillnelown on GitHub (Jun 14, 2024).

Describe the problem

When a DNS query uses random capitalisation like the one which is used to prevent cache poisoning Netbird will respond with NXDOMAIN.

To Reproduce

Steps to reproduce the behavior:

  1. Connect to a Netbird network
  2. Run a DNS query to the local resolver for a hostname
    dig @10.74.x.y <hostname>.<domain> works but dig @10.74.x.y <hOstName>.<dOmAin> does not
    dig @10.74.42.7 me.client.netbird works but dig @10.74.42.7 Me.Client.netbird does not

Expected behavior

Netbird should ignore these capitalisations as they are not relevant in this context.

Are you using NetBird Cloud?

I'm using the selfhosted instance though this seems like a client issue.

NetBird version

netbird version
0.27.10

Originally created by @tillnelown on GitHub (Jun 14, 2024). **Describe the problem** When a DNS query uses random capitalisation like the one which is used to prevent cache poisoning Netbird will respond with NXDOMAIN. **To Reproduce** Steps to reproduce the behavior: 1. Connect to a Netbird network 2. Run a DNS query to the local resolver for a hostname `dig @10.74.x.y <hostname>.<domain>` works but `dig @10.74.x.y <hOstName>.<dOmAin>` does not `dig @10.74.42.7 me.client.netbird` works but `dig @10.74.42.7 Me.Client.netbird` does not **Expected behavior** Netbird should ignore these capitalisations as they are not relevant in this context. **Are you using NetBird Cloud?** I'm using the selfhosted instance though this seems like a client issue. **NetBird version** `netbird version` 0.27.10
saavagebueno added the clientwaiting-feedbackdns labels 2025-11-20 05:20:57 -05:00
saavagebueno commented 2025-11-20 05:20:58 -05:00
Author
Owner
Copy Link

@nazarewk commented on GitHub (Apr 23, 2025):

@tillnelown can you check whether this is still not worknig for you with the latest NetBird version?

Seems like it works fine for me when using Network Resources:

kdn@brys ~> ssh anji-vm-macos-01 dig +short sElF.nb.test @100.83.255.254
192.168.100.10
kdn@brys ~> ssh anji-vm-macos-01 dig +short self.nb.test @100.83.255.254
192.168.100.10
@nazarewk commented on GitHub (Apr 23, 2025): @tillnelown can you check whether this is still not worknig for you with the latest NetBird version? Seems like it works fine for me when using Network Resources: ``` kdn@brys ~> ssh anji-vm-macos-01 dig +short sElF.nb.test @100.83.255.254 192.168.100.10 kdn@brys ~> ssh anji-vm-macos-01 dig +short self.nb.test @100.83.255.254 192.168.100.10 ```
saavagebueno commented 2025-11-20 05:20:58 -05:00
Author
Owner
Copy Link

@tillnelown commented on GitHub (Apr 27, 2025):

@nazarewk I went back to a pure Wireguard mesh for now so I can't test it as the original setup doesn't exist anymore.
I'll try to migrate back to Netbird once a few other issues have been resolved, feel free to close this issue if you feel you've tested it enough and I'll open it again if i encounter it.

If anyone wants to replicate the exact setup:
I had a Netbird network that was connected to a wireguard mesh through routing, to better facilitate client communication I set up the Technitium DNS Server where the inside IPs of the peers where added. I wanted to point at Netbird as an upstream dns server to automatically get the Netbird client IPs to serve to the Wireguard clients but Technitium used DNS-0x20 encoding for upstream servers which Netbird didn't answer.

@tillnelown commented on GitHub (Apr 27, 2025): @nazarewk I went back to a pure Wireguard mesh for now so I can't test it as the original setup doesn't exist anymore. I'll try to migrate back to Netbird once a few other issues have been resolved, feel free to close this issue if you feel you've tested it enough and I'll open it again if i encounter it. If anyone wants to replicate the exact setup: I had a Netbird network that was connected to a wireguard mesh through routing, to better facilitate client communication I set up the [Technitium DNS Server](https://github.com/TechnitiumSoftware/DnsServer) where the inside IPs of the peers where added. I wanted to point at Netbird as an upstream dns server to automatically get the Netbird client IPs to serve to the Wireguard clients but Technitium used DNS-0x20 encoding for upstream servers which Netbird didn't answer.
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 waiting-feedback
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#980
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?