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

"MagicDNS" equivalent for clients #289

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

Originally created by @alexlyee on GitHub (Mar 9, 2023).

Currently, it seems that one is subjected to the network-wide DNS configuration when they join a netbird network. But once we are able to connect to our own as well as our friends' coordination servers (#446), the only thing left that I would really need for my use-case is the ability to configure split-tunneling for the clients which I share between multiple networks.

For example, say my homelab is at my.homelab, and my friend's is homie.homelab. My devices are shared with both of our netbird instances, but I'd like to be able to route to both of our networks seamlessly. With #446 done, maybe we'll have to switch between the networks one at a time, fine, but ideally, the client could help us route between both networks at once.

If we got to that point, where one client beneath multiple coordination servers is possible, then I'd really love to be able to route all of my DNS to my.homelab's DNS, and whenever I try to resolve anything at homie.homelab (*.homie.homelab), I use my friend's DNS.

Originally created by @alexlyee on GitHub (Mar 9, 2023). Currently, it seems that one is subjected to the network-wide DNS configuration when they join a netbird network. But once we are able to connect to our own as well as our friends' coordination servers (#446), the only thing left that I would really need for my use-case is the ability to configure split-tunneling for the clients which I share between multiple networks. For example, say my homelab is at `my.homelab`, and my friend's is `homie.homelab`. My devices are shared with both of our netbird instances, but I'd like to be able to route to both of our networks seamlessly. With #446 done, maybe we'll have to switch between the networks one at a time, fine, but ideally, the client could help us route between both networks at once. If we got to that point, where one client beneath multiple coordination servers is possible, then I'd really love to be able to route all of my DNS to `my.homelab`'s DNS, and whenever I try to resolve anything at `homie.homelab` (`*.homie.homelab`), I use my friend's DNS.
saavagebueno commented 2025-11-20 05:09:10 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Mar 11, 2023):

Hello @alexlyee have you checked the creating-a-nameserver-for-specific-domains section of the documentation?

Generally the agent doesn't support multiple controller connection. You can run different agent instances with different configuration files as long as you configure different interface names and ports.

With that, if the host where you run such setup supports a good DNS policy (windows, macOS and Linux with systemd-resolved), you should be able to reach such a setup.

@mlsmaycon commented on GitHub (Mar 11, 2023): Hello @alexlyee have you checked the [creating-a-nameserver-for-specific-domains](https://netbird.io/docs/how-to-guides/nameservers#creating-a-nameserver-for-specific-domains) section of the documentation? Generally the agent doesn't support multiple controller connection. You can run different agent instances with different configuration files as long as you configure different interface names and ports. With that, if the host where you run such setup supports a good DNS policy (windows, macOS and Linux with systemd-resolved), you should be able to reach such a setup.
saavagebueno commented 2025-11-20 05:09:10 -05:00
Author
Owner
Copy Link

@alexlyee commented on GitHub (Mar 11, 2023):

I didn't know that multiple agent instances could be run at once. I'll have to figure out how to do that on my own. With that, I suppose then this isn't really an issue?

@alexlyee commented on GitHub (Mar 11, 2023): I didn't know that multiple agent instances could be run at once. I'll have to figure out how to do that on my own. With that, I suppose then this isn't really an issue?
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
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#289
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?