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

Not using defined DNS #1287

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

Originally created by @choldi on GitHub (Sep 25, 2024).

Describe the problem

Peers in group not using defined dns

To Reproduce

Steps to reproduce the behavior:

  1. Create a group of peers. In my case "Convidats"
  2. Define a peer (vm1) as exit node
  3. Install dockerized pihole (dns server) in exit node. Expose port 53 tcp/udp
  4. Create a dns and assign to group "convidats" pointing to exit node, default port, no domains
  5. Using a peer in group convidats with nslookup, server vm1 resolves address
  6. requests from peers in group convidats don't use dns server from vm1

Expected behavior

DNS request from peers of group convidads should go to defined DNS for group

Are you using NetBird Cloud?

Yes, using netbird cloud

NetBird version
0.28 android client
0.29.4 vm1 (server, dockerized)

NetBird status -dA output:

Server:

/ # ps aux
PID USER TIME COMMAND
1 root 0:45 /usr/local/bin/netbird up
82 root 0:00 sh
110 root 0:00 ps aux
/ # netbird status -dA
Error: failed to connect to daemon error: context deadline exceeded
If the daemon is not running please run:
netbird service install
netbird service start

Do you face any (non-mobile) client issues?
Not resolving dns correctly

Screenshots

Additional context

Originally created by @choldi on GitHub (Sep 25, 2024). **Describe the problem** Peers in group not using defined dns **To Reproduce** Steps to reproduce the behavior: 1. Create a group of peers. In my case "Convidats" 2. Define a peer (vm1) as exit node 3. Install dockerized pihole (dns server) in exit node. Expose port 53 tcp/udp 4. Create a dns and assign to group "convidats" pointing to exit node, default port, no domains 5. Using a peer in group convidats with nslookup, server vm1 resolves address 6. requests from peers in group convidats don't use dns server from vm1 **Expected behavior** DNS request from peers of group convidads should go to defined DNS for group **Are you using NetBird Cloud?** Yes, using netbird cloud **NetBird version** 0.28 android client 0.29.4 vm1 (server, dockerized) **NetBird status -dA output:** Server: / # ps aux PID USER TIME COMMAND 1 root 0:45 /usr/local/bin/netbird up 82 root 0:00 sh 110 root 0:00 ps aux / # netbird status -dA Error: failed to connect to daemon error: context deadline exceeded If the daemon is not running please run: netbird service install netbird service start **Do you face any (non-mobile) client issues?** Not resolving dns correctly **Screenshots** **Additional context**
saavagebueno added the dns label 2025-11-20 05:27:31 -05:00
saavagebueno commented 2025-11-20 05:27:32 -05:00
Author
Owner
Copy Link

@mgarces commented on GitHub (Sep 27, 2024):

Hi @choldi ,
just a quick check, is pihole ports 53 bounded to which IP? Can you please show the output for

netstat -tunelp | grep 53

Also, how are you assigning your Nameserver in the dashboard, and do you have a Policy that allows Convidats peers to access that TCP/UDP port for the vm1 host?

@mgarces commented on GitHub (Sep 27, 2024): Hi @choldi , just a quick check, is `pihole` ports 53 bounded to which IP? Can you please show the output for ``` netstat -tunelp | grep 53 ``` Also, how are you assigning your Nameserver in the dashboard, and do you have a Policy that allows `Convidats` peers to access that TCP/UDP port for the `vm1` host?
saavagebueno commented 2025-11-20 05:27:32 -05:00
Author
Owner
Copy Link

@choldi commented on GitHub (Sep 27, 2024):

Hello, thanks @mgarces
pihole:

tcp        0      0 0.0.0.0:53              0.0.0.0:*               LISTEN      11438/docker-proxy
tcp        0      0 :::53                   :::*                    LISTEN      11444/docker-proxy
udp        0      0 0.0.0.0:53              0.0.0.0:*                           11458/docker-proxy
udp        0      0 :::53                   :::*                                11464/docker-proxy

The nameserver is in the dashboard but no policy defined. But from the client, I can connect the DNS (telnet to port 53)

@choldi commented on GitHub (Sep 27, 2024): Hello, thanks @mgarces pihole: ``` tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 11438/docker-proxy tcp 0 0 :::53 :::* LISTEN 11444/docker-proxy udp 0 0 0.0.0.0:53 0.0.0.0:* 11458/docker-proxy udp 0 0 :::53 :::* 11464/docker-proxy ``` The nameserver is in the dashboard but no policy defined. But from the client, I can connect the DNS (telnet to port 53)
saavagebueno commented 2025-11-20 05:27:32 -05:00
Author
Owner
Copy Link

@choldi commented on GitHub (Sep 27, 2024):

Seem that it was a misconfiguration on my servers. Seems to work.

@choldi commented on GitHub (Sep 27, 2024): Seem that it was a misconfiguration on my servers. Seems to work.
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 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#1287
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?