resolv.conf missing cluster DNS after upgrading to 0.52.1 #2140

Open
opened 2025-11-20 07:04:38 -05:00 by saavagebueno · 1 comment
Owner

Originally created by @1scrooge on GitHub (Jul 31, 2025).

Describe the problem

After update to 0.52.1 we have an issue with name resolution inside the Kubernetes cluster., The /etc/resolv.conf file looks like:

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

options ndots:5
search netbird.cloud 248f33ce-0af6-475a-9fb5-1a34343d5aa0.svc.cluster.local svc.cluster.local cluster.local
nameserver 100.123.26.124

There is no internal DNS nameserver in this configuration.
In version 0.51.2, everything worked fine. For comparison:

# Generated by NetBird
# If needed you can restore the original file by copying back /etc/resolv.conf.original.netbird

options attempts:1 timeout:4 ndots:5
search netbird.cloud cd7c0a24-7745-483f-835a-5cf41f6adcfe.svc.cluster.local svc.cluster.local cluster.local
nameserver 100.123.104.247
nameserver 10.245.0.10

Expected behavior

The internal Kubernetes DNS nameserver should still be present in the new version.

Are you using NetBird Cloud?

Yes, NetBird Cloud.

**NetBird version **

0.52.1

Is any other VPN software installed?

No

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 @1scrooge on GitHub (Jul 31, 2025). **Describe the problem** After update to 0.52.1 we have an issue with name resolution inside the Kubernetes cluster., The /etc/resolv.conf file looks like: ``` Generated by NetBird # The original file can be restored from /etc/resolv.conf.original.netbird options ndots:5 search netbird.cloud 248f33ce-0af6-475a-9fb5-1a34343d5aa0.svc.cluster.local svc.cluster.local cluster.local nameserver 100.123.26.124 ``` There is no internal DNS nameserver in this configuration. In version 0.51.2, everything worked fine. For comparison: ``` # Generated by NetBird # If needed you can restore the original file by copying back /etc/resolv.conf.original.netbird options attempts:1 timeout:4 ndots:5 search netbird.cloud cd7c0a24-7745-483f-835a-5cf41f6adcfe.svc.cluster.local svc.cluster.local cluster.local nameserver 100.123.104.247 nameserver 10.245.0.10 ``` **Expected behavior** The internal Kubernetes DNS nameserver should still be present in the new version. **Are you using NetBird Cloud?** Yes, NetBird Cloud. **NetBird version ** `0.52.1` **Is any other VPN software installed?** No **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 triage-needed label 2025-11-20 07:04:38 -05:00
Author
Owner

@Blackclaws commented on GitHub (Jul 31, 2025):

I think this is the same issue: https://github.com/netbirdio/netbird/issues/4250

@Blackclaws commented on GitHub (Jul 31, 2025): I think this is the same issue: https://github.com/netbirdio/netbird/issues/4250
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#2140