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

Local DNS listener refuses connection after version 0.27.4 #877

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

Originally created by @kristoftorok on GitHub (May 12, 2024).

Describe the problem

Netbird linux client does not respond to DNS requests. (REFUSED)
So after upgrading to 0.27.5 the local DNS resolver stopped working.

I have a server running my own DNS server. On this server I have a network which has the subnet 192.168.94.0/24.
I have setup a static route to this network and it's working perfectly.
The DNS server is running on the 192.168.94.53 IP and it is used for local only domain resolution.

For example: postgres.domain.com -> 192.168.94.20

This DNS server is configured for the "devnet" group. My user is added to this group.

On my own computer I get a netbird VPN IP: 100.111.5.11, the local DNS server should respond on this IP but it does NOT! Which means that there is no DNS resolution. In fact, I see that the netbird client is listening on port 53, but it refuses the connection:
dig google.com @100.111.5.11

However if I make the DNS request directly to my DNS server:
dig postgres.domain.com @192.168.94.53 I get an answer.

Downgrading to 0.27.4 solved the problem. Everything works as excepted.

The platfrom is Linux, tested on Solus OS and Fedora, same error in both cases with 0.27.5

To Reproduce

Steps to reproduce the behavior:

  1. Upgrade to 0.27.5
  2. netbird up
  3. dig dig google.com @100.111.X.X -> REFUSED
  4. dig dig google.com @192.168.94.53 -> OK

Expected behavior

The DNS server should answer.

Are you using NetBird Cloud?

Yes NetBird Cloud

NetBird version

0.27.5

Originally created by @kristoftorok on GitHub (May 12, 2024). **Describe the problem** Netbird linux client does not respond to DNS requests. (REFUSED) So after upgrading to 0.27.5 the local DNS resolver stopped working. I have a server running my own DNS server. On this server I have a network which has the subnet `192.168.94.0/24`. I have setup a static route to this network and it's working perfectly. The DNS server is running on the 192.168.94.53 IP and it is used for local only domain resolution. For example: postgres.domain.com -> 192.168.94.20 This DNS server is configured for the "devnet" group. My user is added to this group. On my own computer I get a netbird VPN IP: 100.111.5.11, the local DNS server should respond on this IP but it does NOT! Which means that there is no DNS resolution. In fact, I see that the netbird client is listening on port 53, but it refuses the connection: `dig google.com @100.111.5.11` However if I make the DNS request directly to my DNS server: `dig postgres.domain.com @192.168.94.53` I get an answer. Downgrading to 0.27.4 solved the problem. Everything works as excepted. The platfrom is Linux, tested on Solus OS and Fedora, same error in both cases with 0.27.5 **To Reproduce** Steps to reproduce the behavior: 1. Upgrade to 0.27.5 2. `netbird up` 3. dig `dig google.com @100.111.X.X -> REFUSED` 4. dig `dig google.com @192.168.94.53 -> OK` **Expected behavior** The DNS server should answer. **Are you using NetBird Cloud?** Yes NetBird Cloud **NetBird version** `0.27.5`
saavagebueno added the clientdns labels 2025-11-20 05:19:07 -05:00
saavagebueno commented 2025-11-20 05:19:08 -05:00
Author
Owner
Copy Link

@lixmal commented on GitHub (May 13, 2024):

Can you provide a netbird status -dA when on 0.27.5, please? Logs would also be helpful.

You can generate a bundle containing logs and the status output with netbird debug for 1m -A (anonymized)

@lixmal commented on GitHub (May 13, 2024): Can you provide a `netbird status -dA` when on `0.27.5`, please? Logs would also be helpful. You can generate a bundle containing logs and the status output with `netbird debug for 1m -A` (anonymized)
saavagebueno commented 2025-11-20 05:19:08 -05:00
Author
Owner
Copy Link

@kristoftorok commented on GitHub (May 13, 2024):

netbird status -dA output:

OS: linux/amd64
Daemon version: 0.27.5
CLI version: 0.27.5
Management: Connected to https://api.netbird.io:443
Signal: Connected to https://signal.netbird.io:443
Relays: 
  [stun:stun.netbird.io:5555] is Unavailable, reason: dial: failed to listen: dial: dial udp: lookup stun.netbird.io on 127.0.0.53:53: server misbehaving
  [turns:turn.netbird.io:443?transport=tcp] is Unavailable, reason: dial: dial: dial tcp: lookup turn.netbird.io on 127.0.0.53:53: server misbehaving
Nameservers: 
  [192.168.94.53:53] for [.] is Available
FQDN: fedora-lap.netbird.cloud
NetBird IP: 100.111.150.97/16
Interface type: Kernel
Quantum resistance: false
Routes: -
Peers count: 1/1 Connected

netbird debug for 1m -A shows nothing, just a timer.

DNS:
image

@kristoftorok commented on GitHub (May 13, 2024): `netbird status -dA` output: ``` OS: linux/amd64 Daemon version: 0.27.5 CLI version: 0.27.5 Management: Connected to https://api.netbird.io:443 Signal: Connected to https://signal.netbird.io:443 Relays: [stun:stun.netbird.io:5555] is Unavailable, reason: dial: failed to listen: dial: dial udp: lookup stun.netbird.io on 127.0.0.53:53: server misbehaving [turns:turn.netbird.io:443?transport=tcp] is Unavailable, reason: dial: dial: dial tcp: lookup turn.netbird.io on 127.0.0.53:53: server misbehaving Nameservers: [192.168.94.53:53] for [.] is Available FQDN: fedora-lap.netbird.cloud NetBird IP: 100.111.150.97/16 Interface type: Kernel Quantum resistance: false Routes: - Peers count: 1/1 Connected ``` `netbird debug for 1m -A` shows nothing, just a timer. DNS: ![image](https://github.com/netbirdio/netbird/assets/55440418/21702776-f938-4626-a47c-eb9eb62bab12)
saavagebueno commented 2025-11-20 05:19:08 -05:00
Author
Owner
Copy Link

@lixmal commented on GitHub (May 13, 2024):

Thanks so far.

netbird debug for 1m -A shows nothing, just a timer.

It should print a file path at the end, does it not?
You'll need root permissions to copy it from there.

@lixmal commented on GitHub (May 13, 2024): Thanks so far. > netbird debug for 1m -A shows nothing, just a timer. It should print a file path at the end, does it not? You'll need root permissions to copy it from there.
saavagebueno commented 2025-11-20 05:19:08 -05:00
Author
Owner
Copy Link

@vojtovo commented on GitHub (May 13, 2024):

@lixmal Hello, I have exactly same problem on 0.27.5, downgrade to 0.27.4 resolved the issue.

This is what I have found in the log, I guess it is related to the issue:

2024-05-13T15:39:00+02:00 WARN [error: read udp 192.168.0.107:61401->10.0.35.1:53: i/o timeout, upstream: 10.0.35.1:53] client/internal/dns/upstream.go:102: got an error while connecting to upstream
2024-05-13T15:39:00+02:00 WARN [upstream: 10.0.35.1:53, error: read udp 192.168.0.107:49929->10.0.35.1:53: i/o timeout] client/internal/dns/upstream.go:102: got an error while connecting to upstream
2024-05-13T15:39:00+02:00 ERRO client/internal/dns/upstream.go:134: all queries to the upstream nameservers failed with timeout
2024-05-13T15:39:00+02:00 ERRO client/internal/dns/upstream.go:134: all queries to the upstream nameservers failed with timeout

Is it possible to send whole log via email?

@vojtovo commented on GitHub (May 13, 2024): @lixmal Hello, I have exactly same problem on 0.27.5, downgrade to 0.27.4 resolved the issue. This is what I have found in the log, I guess it is related to the issue: ``` 2024-05-13T15:39:00+02:00 WARN [error: read udp 192.168.0.107:61401->10.0.35.1:53: i/o timeout, upstream: 10.0.35.1:53] client/internal/dns/upstream.go:102: got an error while connecting to upstream 2024-05-13T15:39:00+02:00 WARN [upstream: 10.0.35.1:53, error: read udp 192.168.0.107:49929->10.0.35.1:53: i/o timeout] client/internal/dns/upstream.go:102: got an error while connecting to upstream 2024-05-13T15:39:00+02:00 ERRO client/internal/dns/upstream.go:134: all queries to the upstream nameservers failed with timeout 2024-05-13T15:39:00+02:00 ERRO client/internal/dns/upstream.go:134: all queries to the upstream nameservers failed with timeout ``` Is it possible to send whole log via email?
saavagebueno commented 2025-11-20 05:19:08 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (May 13, 2024):

Hello Folks, the PR #1975 will fix the issue. We will do a release soon after it is merged.

@mlsmaycon commented on GitHub (May 13, 2024): Hello Folks, the PR #1975 will fix the issue. We will do a release soon after it is merged.
saavagebueno commented 2025-11-20 05:19:09 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (May 13, 2024):

The new release is live. Please upgrade.

@mlsmaycon commented on GitHub (May 13, 2024): The new release is live. Please upgrade.
saavagebueno commented 2025-11-20 05:19:09 -05:00
Author
Owner
Copy Link

@kristoftorok commented on GitHub (May 13, 2024):

The new version works fine! Thanks!

@kristoftorok commented on GitHub (May 13, 2024): The new version works fine! Thanks!
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 client 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#877
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?