SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-07-29 17:32:35 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

Netbird sets itself as default dns resolution #384

New Issue
Closed
opened 2025-11-20 05:10:34 -05:00 by saavagebueno · 4 comments
saavagebueno commented 2025-11-20 05:10:34 -05:00
Owner
Copy Link

Originally created by @JavierLeventan on GitHub (Jun 27, 2023).

Describe the problem
When trying to resolve a DNS query to a machine on another VPN only by name (without the domain), the domain used is the one set on netbird.

To Reproduce

  1. Connect to a VPN that has a DNS server configured.
  2. Connect to a Netbird VPN.
  3. Ping to a machine on the other VPN, without using the domain

Expected behavior
Netbird domain should be the last one used for domain resolution (or, at least, have an option to be) to avoid beaking DNS querys to other domains on different networks.

Additional context
Detected while using Wireguard or OpenVPN while using Netbird at the same time.

Originally created by @JavierLeventan on GitHub (Jun 27, 2023). **Describe the problem** When trying to resolve a DNS query to a machine on another VPN only by name (without the domain), the domain used is the one set on netbird. **To Reproduce** 1. Connect to a VPN that has a DNS server configured. 2. Connect to a Netbird VPN. 3. Ping to a machine on the other VPN, without using the domain **Expected behavior** Netbird domain should be the last one used for domain resolution (or, at least, have an option to be) to avoid beaking DNS querys to other domains on different networks. **Additional context** Detected while using Wireguard or OpenVPN while using Netbird at the same time.
saavagebueno added the bug label 2025-11-20 05:10:34 -05:00
saavagebueno commented 2025-11-20 05:10:35 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Jul 22, 2023):

Hello @apika just to confirm the behavior, this happens when you have an all-domain resolver set in the dashboard, right? In other words, you are not limiting the domains that netbird is responsible to respond to?

@mlsmaycon commented on GitHub (Jul 22, 2023): Hello @apika just to confirm the behavior, this happens when you have an all-domain resolver set in the dashboard, right? In other words, you are not limiting the domains that netbird is responsible to respond to?
saavagebueno commented 2025-11-20 05:10:35 -05:00
Author
Owner
Copy Link

@JavierLeventan commented on GitHub (Aug 8, 2023):

No, i wasn't limiting the domains that netbird should respond. Sadly I don't have netbird anymore so I can't expand much more on this issue.

Something that I forgot to add to the issue is that the computer was a joined to a Windows AD and the domain that I couldn't reach was the one from the AD.

@JavierLeventan commented on GitHub (Aug 8, 2023): No, i wasn't limiting the domains that netbird should respond. Sadly I don't have netbird anymore so I can't expand much more on this issue. Something that I forgot to add to the issue is that the computer was a joined to a Windows AD and the domain that I couldn't reach was the one from the AD.
saavagebueno commented 2025-11-20 05:10:35 -05:00
Author
Owner
Copy Link

@MobileManiC commented on GitHub (Aug 14, 2023):

Same issue on Windows I would say... In a lot of cases AD DNS suffix is needed to work properly, otherwise local services will not work at all... (This seens to include AD as well.)

It's OK to add netbird.cloud search domain, but original computer defined domain should be recognized as well....

@MobileManiC commented on GitHub (Aug 14, 2023): Same issue on Windows I would say... In a lot of cases AD DNS suffix is needed to work properly, otherwise local services will not work at all... (This seens to include AD as well.) It's OK to add netbird.cloud search domain, but original computer defined domain should be recognized as well....
saavagebueno commented 2025-11-20 05:10:35 -05:00
Author
Owner
Copy Link

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

I believe this was addressed in one of recent releases, feel free to comment if it's still relevant for you and we'll reopen.

@nazarewk commented on GitHub (Apr 17, 2025): I believe this was addressed in one of recent releases, feel free to comment if it's still relevant for you and we'll reopen.
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 bug
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#384
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?