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

Debian: resolveconf vs. openresolv (peer DNS doesn't work) #654

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

Originally created by @bashgeek on GitHub (Feb 25, 2024).

I was wondering why the DNS resolution of my peers weren't working on our Debian servers, because everything seemed to have been set up correctly.

After inspecting the client log this appears:
apply config: applying resolvconf configuration for wt0 interface, error: exit status 99

Which isn't very verbose about what the issue is. After inspecting the code-base I found that NetBird relies on having openresolv installed, rather than resolveconf. Especially the resolveconf version that Debian uses seems to cause quite some issues, but you already know that judging by the comment in the code:
// openresolv only, debian resolvconf doesn't support "-f"

However, that wasn't clear to me, since it's not mentioned in the docs or anywhere else, so I'm guessing quite some people having this issue on Debian.

After installing openresolv (and hence removing resolvconf) everything magically started to work.

I'd suggest the following:

  • For the Debian packages, set the openresolv package to required dependency
  • Mention it in the docs
  • Enhance the error output in this case and give a hint about the openresolv dependency here

Hope this helps!

Thanks for your work!

Cheers,
Daniel

Originally created by @bashgeek on GitHub (Feb 25, 2024). I was wondering why the DNS resolution of my peers weren't working on our Debian servers, because everything seemed to have been set up correctly. After inspecting the client log this appears: `apply config: applying resolvconf configuration for wt0 interface, error: exit status 99` Which isn't very verbose about what the issue is. After inspecting the code-base I found that NetBird relies on having openresolv installed, rather than resolveconf. Especially the resolveconf version that Debian uses seems to cause quite some issues, but you already know that judging by the comment in the code: `// openresolv only, debian resolvconf doesn't support "-f"` However, that wasn't clear to me, since it's not mentioned in the docs or anywhere else, so I'm guessing quite some people having this issue on Debian. After installing openresolv (and hence removing resolvconf) everything magically started to work. I'd suggest the following: - For the Debian packages, set the openresolv package to required dependency - Mention it in the docs - Enhance the error output in this case and give a hint about the openresolv dependency here Hope this helps! Thanks for your work! Cheers, Daniel
saavagebueno added the triage-needed label 2025-11-20 05:15:25 -05:00
saavagebueno commented 2025-11-20 05:15:25 -05:00
Author
Owner
Copy Link

@adasauce commented on GitHub (Mar 4, 2024):

thanks for reporting this @bashgeek , I was pulling my hair out a bit trying to figure out why DNS wasn't working properly.

I've baked openresolv into my debian images now 👍🏼

@adasauce commented on GitHub (Mar 4, 2024): thanks for reporting this @bashgeek , I was pulling my hair out a bit trying to figure out why DNS wasn't working properly. I've baked openresolv into my debian images now 👍🏼
saavagebueno commented 2025-11-20 05:15:26 -05:00
Author
Owner
Copy Link

@viiiwonder commented on GitHub (May 6, 2024):

Came to say thanks for this report/information. Was able to resolve my DNS issue on Debian because of this.

@viiiwonder commented on GitHub (May 6, 2024): Came to say thanks for this report/information. Was able to resolve my DNS issue on Debian because of this.
saavagebueno commented 2025-11-20 05:15:26 -05:00
Author
Owner
Copy Link

@lixmal commented on GitHub (Feb 21, 2025):

debian resolvconf is now supported

@lixmal commented on GitHub (Feb 21, 2025): debian resolvconf is now supported
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#654
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?