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

Can't resolve names for other peers from host using Docker container #2469

New Issue
Open
opened 2025-11-20 07:10:11 -05:00 by saavagebueno · 0 comments
saavagebueno commented 2025-11-20 07:10:11 -05:00
Owner
Copy Link

Originally created by @spiral6 on GitHub (Nov 18, 2025).

Describe the problem

I've got the following setup:

  • Client 1: Ubuntu 24.04

    • Container 1: Docker image netbirdio/netbird:latest

          cap_add:
          - NET_ADMIN
          - SYS_ADMIN
          - SYS_RESOURCE
        network_mode: host

    • Container 2: Docker image gethomepage/homepage:latest

  • Client 2: Ubuntu 24.04

    • Container: Docker image netbirdio/netbird:latest
      • Same host networking setup as above

I'm trying to set up the ability to resolve Client 2's hostname (i.e. client2.netbird.selfhosted ) from Client 1.

Here's what works and doesn't work:

Client 1: nslookup client2.netbird.selfhosted --> fails
Container 1: nslookup client2.netbird.selfhosted --> success
Container 2: nslookup client2.netbird.selfhosted --> fails

How do I get DNS to propagate from Container 1 to Client 1 and Container 2?

Note: Pinging Client 2's IP works for every case. Not nslookup and DNS though.

To Reproduce

Steps to reproduce the behavior:
See above.

Expected behavior

Client 1 and Container 2 should resolve DNS.

Are you using NetBird Cloud?

No.

NetBird version

netbird version

Is any other VPN software installed?
No.

Debug output

To help us resolve the problem, please attach the following anonymized status output

netbird status -dA

Create and upload a debug bundle, and share the returned file key:

netbird debug for 1m -AS -U

Uploaded files are automatically deleted after 30 days.

Alternatively, create the file only and attach it here manually:

netbird debug for 1m -AS

Screenshots

If applicable, add screenshots to help explain your problem.

Additional context

Add any other context about the problem here.

Have you tried these troubleshooting steps?

  • Reviewed client troubleshooting (if applicable)
  • Checked for newer NetBird versions
  • Searched for similar issues on GitHub (including closed ones)
  • Restarted the NetBird client
  • Disabled other VPN software
  • Checked firewall settings
Originally created by @spiral6 on GitHub (Nov 18, 2025). **Describe the problem** I've got the following setup: - Client 1: Ubuntu 24.04 - Container 1: Docker image `netbirdio/netbird:latest` cap_add: - NET_ADMIN - SYS_ADMIN - SYS_RESOURCE network_mode: host - Container 2: Docker image `gethomepage/homepage:latest` - Client 2: Ubuntu 24.04 - Container: Docker image `netbirdio/netbird:latest` - Same host networking setup as above I'm trying to set up the ability to resolve Client 2's hostname (i.e. `client2.netbird.selfhosted` ) from Client 1. Here's what works and doesn't work: Client 1: nslookup client2.netbird.selfhosted --> fails Container 1: nslookup client2.netbird.selfhosted --> success Container 2: nslookup client2.netbird.selfhosted --> fails How do I get DNS to propagate from `Container 1` to `Client 1` and `Container 2`? Note: Pinging Client 2's IP works for every case. Not `nslookup` and DNS though. **To Reproduce** Steps to reproduce the behavior: See above. **Expected behavior** Client 1 and Container 2 should resolve DNS. **Are you using NetBird Cloud?** No. **NetBird version** `netbird version` **Is any other VPN software installed?** No. **Debug output** To help us resolve the problem, please attach the following anonymized status output netbird status -dA Create and upload a debug bundle, and share the returned file key: netbird debug for 1m -AS -U *Uploaded files are automatically deleted after 30 days.* Alternatively, create the file only and attach it here manually: netbird debug for 1m -AS **Screenshots** If applicable, add screenshots to help explain your problem. **Additional context** Add any other context about the problem here. **Have you tried these troubleshooting steps?** - [ ] Reviewed [client troubleshooting](https://docs.netbird.io/how-to/troubleshooting-client) (if applicable) - [ ] Checked for newer NetBird versions - [ ] Searched for similar issues on GitHub (including closed ones) - [ ] Restarted the NetBird client - [ ] Disabled other VPN software - [ ] Checked firewall settings
saavagebueno added the triage-needed label 2025-11-20 07:10:11 -05:00
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 triage-needed
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#2469
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?