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

/etc/resolv.conf overridden with "Invalid IP" for nameserver on hosts with DNS handling disabled #2120

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

Originally created by @LouisVallat on GitHub (Jul 29, 2025).

Describe the problem

I host some DNS servers, some of which have netbird installed with DNS handling disabled (as it conflicted with the port 53 being already used by my own DNS software).
I recently updated to 0.52.0 and now my /etc/resolv.conf file is overridden with this:

# Generated by NetBird
# The original file can be restored from /etc/resolv.conf.original.netbird

nameserver invalid IP

Of course, invalid IP is, well, not an actual IP, so any DNS query done on these servers fail, and overwriting the file leads to netbird re-overwriting over my modifications.

To Reproduce

Steps to reproduce the behavior:

  1. Install netbird on a host (here on Debian 12)
  2. Disable DNS handling for this host
  3. Check /etc/resolv.conf

Expected behavior

I expect netbird to:

  1. not touch my DNS config when I told it to
  2. NOT set "invalid IP" as a new name-server.

Are you using NetBird Cloud?

Self-hosted using Docker Compose.

NetBird version

0.52.0

Is any other VPN software installed?

No.

Debug output

N/A

Screenshots

N/A

Additional context

N/A

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 @LouisVallat on GitHub (Jul 29, 2025). **Describe the problem** I host some DNS servers, some of which have `netbird` installed with DNS handling disabled (as it conflicted with the port 53 being already used by my own DNS software). I recently updated to 0.52.0 and now my /etc/resolv.conf file is overridden with this: ```conf # Generated by NetBird # The original file can be restored from /etc/resolv.conf.original.netbird nameserver invalid IP ``` Of course, `invalid IP` is, well, not an actual IP, so any DNS query done on these servers fail, and overwriting the file leads to `netbird` re-overwriting over my modifications. **To Reproduce** Steps to reproduce the behavior: 1. Install `netbird` on a host (here on Debian 12) 2. Disable DNS handling for this host 3. Check `/etc/resolv.conf` **Expected behavior** I expect `netbird` to: 1. not touch my DNS config when I told it to 2. **NOT** set "invalid IP" as a new name-server. **Are you using NetBird Cloud?** Self-hosted using Docker Compose. **NetBird version** `0.52.0` **Is any other VPN software installed?** No. **Debug output** N/A **Screenshots** N/A **Additional context** N/A **Have you tried these troubleshooting steps?** - [x] Reviewed [client troubleshooting](https://docs.netbird.io/how-to/troubleshooting-client) (if applicable) - [x] Checked for newer NetBird versions - [x] Searched for similar issues on GitHub (including closed ones) - [x] Restarted the NetBird client - [x] Disabled other VPN software - [x] Checked firewall settings
saavagebueno added the bugclient labels 2025-11-20 07:04:10 -05:00
saavagebueno commented 2025-11-20 07:04:12 -05:00
Author
Owner
Copy Link

@MrBE4R commented on GitHub (Jul 29, 2025):

Hi,

I'm encountering the same issue.

This is most likely due to #3967 .

The problem occur if not dns servers are configured for the group or if the clients are in a group where dns management is disabled.

If the client have systemd-resolved installed everything work (I've not yet tested with or openresolv).

Cheer,
Jeff

@MrBE4R commented on GitHub (Jul 29, 2025): Hi, I'm encountering the same issue. This is most likely due to #3967 . The problem occur if not dns servers are configured for the group or if the clients are in a group where dns management is disabled. If the client have `systemd-resolved` installed everything work (I've not yet tested with or `openresolv`). Cheer, Jeff
saavagebueno commented 2025-11-20 07:04:12 -05:00
Author
Owner
Copy Link

@fiadigifrank commented on GitHub (Jul 29, 2025):

+1 this update, broke my 20 client connection~~~oh god~

@fiadigifrank commented on GitHub (Jul 29, 2025): +1 this update, broke my 20 client connection~~~oh god~
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 bug 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#2120
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?