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

dns support only routing domain but not search domain #316

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

Originally created by @lfarkas on GitHub (Apr 30, 2023).

if add a domain with nameserver in the DNS tab it's add only routing only domain (at least on linux). eg if i add foo.com to 1.2.3.4 then i see something like this on the resolvectl output:

Link 5 (wt0)
    Current Scopes: DNS
         Protocols: +DefaultRoute LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 100.76.24.179
       DNS Servers: 100.76.24.179
        DNS Domain: netbird.cloud ~foo.com

this result that if i try to resolve a name with:
resolvectl query bar.foo.com
than it's working, BUT if i try with short name only eg:
resolvectl query bar or ping bar
than it's not working. and currently I'm not able to solve it.

it'd be nice if i can add search domains too. The best would be if i can configure whether add routing or search domain in the DNS tab.

Originally created by @lfarkas on GitHub (Apr 30, 2023). if add a domain with nameserver in the DNS tab it's add only routing only domain (at least on linux). eg if i add foo.com to 1.2.3.4 then i see something like this on the resolvectl output: ``` Link 5 (wt0) Current Scopes: DNS Protocols: +DefaultRoute LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported Current DNS Server: 100.76.24.179 DNS Servers: 100.76.24.179 DNS Domain: netbird.cloud ~foo.com ``` this result that if i try to resolve a name with: `resolvectl query bar.foo.com` than it's working, BUT if i try with short name only eg: `resolvectl query bar` or `ping bar` than it's not working. and currently I'm not able to solve it. it'd be nice if i can add search domains too. The best would be if i can configure whether add routing or search domain in the DNS tab.
saavagebueno added the client label 2025-11-20 05:09:32 -05:00
saavagebueno commented 2025-11-20 05:09:32 -05:00
Author
Owner
Copy Link

@gigovich commented on GitHub (May 1, 2023):

Hello, @lfarkas. When Netbird DNS name resolving is enabled, a short domain name search works only for netbird.cloud zone. So you can resolve as short names only peers in the Netbird network. For all other queries, you need to use FQDN domain names.

@gigovich commented on GitHub (May 1, 2023): Hello, @lfarkas. When Netbird DNS name resolving is enabled, a short domain name search works only for `netbird.cloud` zone. So you can resolve as short names only peers in the Netbird network. For all other queries, you need to use FQDN domain names.
saavagebueno commented 2025-11-20 05:09:33 -05:00
Author
Owner
Copy Link

@lfarkas commented on GitHub (May 2, 2023):

it seems the situation was not clear enough.
if we got a domain and a dns for it than the given zone probably contains many fqdn hostname in the dns (otherwise we do't use a dns).
we probably have a netbird client in the given network but not all of the host has a netbird client (otherwise the .netbird.cloud zone resolution would be enough).
so when we'd like to manage dns in netbird, then we've a routed network with a gateway netbird clinet inside this network.
if i'd like to use dns in netbird then i'd like to be able to resolve all host in that domain.
of course as a the routing only domain it's better then nothing since if i use fqdn then it resolve it but if i'd like to resolve short names than it's not working what's more there is no way to resolve short names for these domains.

that's why i'd propose that by default these domains should have to be search domain or at least it should have to be configurable to be routing only dns or search dns.

@lfarkas commented on GitHub (May 2, 2023): it seems the situation was not clear enough. if we got a domain and a dns for it than the given zone probably contains many fqdn hostname in the dns (otherwise we do't use a dns). we probably have a netbird client in the given network but not all of the host has a netbird client (otherwise the .netbird.cloud zone resolution would be enough). so when we'd like to manage dns in netbird, then we've a routed network with a gateway netbird clinet inside this network. if i'd like to use dns in netbird then i'd like to be able to resolve all host in that domain. of course as a the routing only domain it's better then nothing since if i use fqdn then it resolve it but if i'd like to resolve short names than it's not working what's more there is no way to resolve short names for these domains. that's why i'd propose that by default these domains should have to be search domain or at least it should have to be configurable to be routing only dns or search dns.
saavagebueno commented 2025-11-20 05:09:33 -05:00
Author
Owner
Copy Link

@lfarkas commented on GitHub (Oct 28, 2023):

fixed in the latest release

@lfarkas commented on GitHub (Oct 28, 2023): fixed in the latest release
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
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#316
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?