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

DNS resolution fails when running a local resolver #995

New Issue
Open
opened 2025-11-20 05:21:18 -05:00 by saavagebueno · 22 comments
saavagebueno commented 2025-11-20 05:21:18 -05:00
Owner
Copy Link

Originally created by @MDMeridio001 on GitHub (Jun 19, 2024).

Describe the problem

I run a local DNS resolver (unbound) on a netbird peer running Ubuntu Server 22.04.4 LTS. DNS management is disabled for the peer in question via the netbird dashboard. Everything worked fine in version 0.27.10, but after updating to 0.28.0 the peer is not able to reach the unbound server running on localhost and every DNS query results in a timeout.

To Reproduce

Steps to reproduce the behavior:

  1. Run "netbird up" on the peer
  2. Run "dig google.com @127.0.0.1" on the peer
  3. dig command results in ";; communications error to 127.0.0.1#53: timed out"
  4. Run "netbird down" on the peer
  5. DNS resolution is back to normal

Expected behavior

I expect the DNS resolution to not be impacted whether or not the peer is connected to netbird, especially because DNS management is disabled in the dashboard for the said peer.

Are you using NetBird Cloud?

No, I'm self-hosting it.

NetBird version

0.28.0

Originally created by @MDMeridio001 on GitHub (Jun 19, 2024). **Describe the problem** I run a local DNS resolver (unbound) on a netbird peer running Ubuntu Server 22.04.4 LTS. DNS management is disabled for the peer in question via the netbird dashboard. Everything worked fine in version 0.27.10, but after updating to 0.28.0 the peer is not able to reach the unbound server running on localhost and every DNS query results in a timeout. **To Reproduce** Steps to reproduce the behavior: 1. Run "netbird up" on the peer 2. Run "dig google.com @127.0.0.1" on the peer 3. dig command results in ";; communications error to 127.0.0.1#53: timed out" 4. Run "netbird down" on the peer 5. DNS resolution is back to normal **Expected behavior** I expect the DNS resolution to not be impacted whether or not the peer is connected to netbird, especially because DNS management is disabled in the dashboard for the said peer. **Are you using NetBird Cloud?** No, I'm self-hosting it. **NetBird version** 0.28.0
saavagebueno added the bugclientdns labels 2025-11-20 05:21:18 -05:00
saavagebueno commented 2025-11-20 05:21:18 -05:00
Author
Owner
Copy Link

@mrota83 commented on GitHub (Jun 19, 2024):

same thing here worked fine before 0.28.0

@mrota83 commented on GitHub (Jun 19, 2024): same thing here worked fine before 0.28.0
saavagebueno commented 2025-11-20 05:21:18 -05:00
Author
Owner
Copy Link

@nikolicjakov commented on GitHub (Jun 20, 2024):

I am having same problem running new 0.28.0 version. And i am also self hosting.

WARN [error: read udp 192.168.25.40:56297->192.168.40.168:53: i/o timeout, upstream: 192.168.40.168:53] client/internal/dns/upstream.go:101: got an error while connecting to upstream

DNS_PROBE_FINISHED_NXDOMAIN

I have 2 DNS servers running in private network and i have created network route to this subnet so that anyone who is connected to vpn can access these DNS servers (one of them 192.168.40.168). But for some reason after 0.28.0 update i am only experiencing issues with internal domain resolutions and i am seeing file getting created every 10 seconds.

And if i am trying to open internal domain client connection breaks since i can see my peer disappearing from dashboard and following files/logs are written...

unclean_shutdown_dns.txt with some strange id inside..

2024-06-20T08:18:33+02:00 WARN client/internal/dns/upstream.go:184: probing upstream nameserver 192.168.40.168:53: read udp 192.168.25.40:59355->192.168.40.168:53: i/o timeout
2024-06-20T08:18:33+02:00 WARN client/internal/dns/upstream.go:184: probing upstream nameserver 192.168.40.68:53: read udp 192.168.25.40:59354->192.168.40.68:53: i/o timeout
2024-06-20T08:18:33+02:00 WARN client/internal/dns/upstream.go:262: Upstream resolving is Disabled for 30s

Something is definitely wrong with communication after 0.28.0 update please take look at this issue... 😢

@nikolicjakov commented on GitHub (Jun 20, 2024): I am having same problem running new 0.28.0 version. And i am also self hosting. `WARN [error: read udp 192.168.25.40:56297->192.168.40.168:53: i/o timeout, upstream: 192.168.40.168:53] client/internal/dns/upstream.go:101: got an error while connecting to upstream` DNS_PROBE_FINISHED_NXDOMAIN I have 2 DNS servers running in private network and i have created network route to this subnet so that anyone who is connected to vpn can access these DNS servers (one of them 192.168.40.168). But for some reason after 0.28.0 update i am only experiencing issues with internal domain resolutions and i am seeing file getting created every 10 seconds. And if i am trying to open internal domain client connection breaks since i can see my peer disappearing from dashboard and following files/logs are written... `unclean_shutdown_dns.txt` with some strange id inside.. ``` 2024-06-20T08:18:33+02:00 WARN client/internal/dns/upstream.go:184: probing upstream nameserver 192.168.40.168:53: read udp 192.168.25.40:59355->192.168.40.168:53: i/o timeout 2024-06-20T08:18:33+02:00 WARN client/internal/dns/upstream.go:184: probing upstream nameserver 192.168.40.68:53: read udp 192.168.25.40:59354->192.168.40.68:53: i/o timeout 2024-06-20T08:18:33+02:00 WARN client/internal/dns/upstream.go:262: Upstream resolving is Disabled for 30s ``` Something is definitely wrong with communication after 0.28.0 update please take look at this issue... 😢
saavagebueno commented 2025-11-20 05:21:18 -05:00
Author
Owner
Copy Link

@lixmal commented on GitHub (Jun 20, 2024):

Can you provide a netbird status -dA please? Even better a complete debug bundle netbird debug for 1m -A

@lixmal commented on GitHub (Jun 20, 2024): Can you provide a `netbird status -dA` please? Even better a complete debug bundle `netbird debug for 1m -A`
saavagebueno commented 2025-11-20 05:21:18 -05:00
Author
Owner
Copy Link

@nikolicjakov commented on GitHub (Jun 20, 2024):

netbird.debug.3041785520.zip

@lixmal Here you go...

@nikolicjakov commented on GitHub (Jun 20, 2024): [netbird.debug.3041785520.zip](https://github.com/user-attachments/files/15910150/netbird.debug.3041785520.zip) @lixmal Here you go...
saavagebueno commented 2025-11-20 05:21:19 -05:00
Author
Owner
Copy Link

@yaneony commented on GitHub (Jun 20, 2024):

Having same issue here.

@yaneony commented on GitHub (Jun 20, 2024): Having same issue here.
saavagebueno commented 2025-11-20 05:21:19 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Jun 20, 2024):

@yaneony @mrota83 @MDMeridio001 are you running on windows? can you share the output requested here: https://github.com/netbirdio/netbird/issues/2157#issuecomment-2179963612 ?

@mlsmaycon commented on GitHub (Jun 20, 2024): @yaneony @mrota83 @MDMeridio001 are you running on windows? can you share the output requested here: https://github.com/netbirdio/netbird/issues/2157#issuecomment-2179963612 ?
saavagebueno commented 2025-11-20 05:21:19 -05:00
Author
Owner
Copy Link

@nikolicjakov commented on GitHub (Jun 20, 2024):

Thank you guys for new release everything looks to be working fine in v0.28.1

@nikolicjakov commented on GitHub (Jun 20, 2024): Thank you guys for new release everything looks to be working fine in v0.28.1
saavagebueno commented 2025-11-20 05:21:19 -05:00
Author
Owner
Copy Link

@MDMeridio001 commented on GitHub (Jun 20, 2024):

@mlsmaycon No, the client is an Ubuntu Server machine. I have updated to 0.28.1 but I'm still facing the same issue.
Here is the output of netbird debug for 1m -A: netbird.debug.80462564.zip

@MDMeridio001 commented on GitHub (Jun 20, 2024): @mlsmaycon No, the client is an Ubuntu Server machine. I have updated to 0.28.1 but I'm still facing the same issue. Here is the output of `netbird debug for 1m -A`: [netbird.debug.80462564.zip](https://github.com/user-attachments/files/15914108/netbird.debug.80462564.zip)
saavagebueno commented 2025-11-20 05:21:19 -05:00
Author
Owner
Copy Link

@nikolicjakov commented on GitHub (Jun 20, 2024):

What did you update client or server components to new v0.28.1 version?

@nikolicjakov commented on GitHub (Jun 20, 2024): What did you update client or server components to new v0.28.1 version?
saavagebueno commented 2025-11-20 05:21:19 -05:00
Author
Owner
Copy Link

@MDMeridio001 commented on GitHub (Jun 20, 2024):

@nikolicjakov both of them.

@MDMeridio001 commented on GitHub (Jun 20, 2024): @nikolicjakov both of them.
saavagebueno commented 2025-11-20 05:21:19 -05:00
Author
Owner
Copy Link

@MDMeridio001 commented on GitHub (Jun 21, 2024):

Just an update, I have also tried updating both the server components and the client to version 0.28.2 and the issue persists.

@MDMeridio001 commented on GitHub (Jun 21, 2024): Just an update, I have also tried updating both the server components and the client to version 0.28.2 and the issue persists.
saavagebueno commented 2025-11-20 05:21:20 -05:00
Author
Owner
Copy Link

@Ryan00793 commented on GitHub (Jul 3, 2024):

This is not fixed in 0.28.3 hosts that previously had the issue however, on a fresh install of ubuntu 22.04 it appears to be working. Luckily for me this is being used in a VM that is only used for netbird so wasn't worried about other things.

@Ryan00793 commented on GitHub (Jul 3, 2024): This is not fixed in 0.28.3 hosts that previously had the issue however, on a fresh install of ubuntu 22.04 it appears to be working. Luckily for me this is being used in a VM that is only used for netbird so wasn't worried about other things.
saavagebueno commented 2025-11-20 05:21:20 -05:00
Author
Owner
Copy Link

@ykorzikowski commented on GitHub (Jul 3, 2024):

Maybe related to this https://github.com/netbirdio/netbird/issues/2219

I start noticing a really shaky server environment after I updated my server-netbird-clients (dns issues, packet loss).

Did not do any further debugging and downgraded all clients to 0.27.10 instead, looks stable again.

Edit:

Some minds: I notice i can dig&nslookup my custom dns server and the local netbird dns. But a curl results in a can not resolve error. This issue was not persistant (see my macbook dns firewall issue). Maybe its a iptables related issue? Some packages got filtered by a wrongly configured rule?

@ykorzikowski commented on GitHub (Jul 3, 2024): Maybe related to this https://github.com/netbirdio/netbird/issues/2219 I start noticing a really shaky server environment after I updated my server-netbird-clients (dns issues, packet loss). Did not do any further debugging and downgraded all clients to 0.27.10 instead, looks stable again. Edit: Some minds: I notice i can dig&nslookup my custom dns server and the local netbird dns. But a curl results in a can not resolve error. This issue was not persistant (see my macbook dns firewall issue). Maybe its a iptables related issue? Some packages got filtered by a wrongly configured rule?
saavagebueno commented 2025-11-20 05:21:20 -05:00
Author
Owner
Copy Link

@Riza-Aslan commented on GitHub (Jan 27, 2025):

I am having same problem running new 0.28.0 version. And i am also self hosting.

WARN [error: read udp 192.168.25.40:56297->192.168.40.168:53: i/o timeout, upstream: 192.168.40.168:53] client/internal/dns/upstream.go:101: got an error while connecting to upstream

DNS_PROBE_FINISHED_NXDOMAIN

I have 2 DNS servers running in private network and i have created network route to this subnet so that anyone who is connected to vpn can access these DNS servers (one of them 192.168.40.168). But for some reason after 0.28.0 update i am only experiencing issues with internal domain resolutions and i am seeing file getting created every 10 seconds.

And if i am trying to open internal domain client connection breaks since i can see my peer disappearing from dashboard and following files/logs are written...

unclean_shutdown_dns.txt with some strange id inside..

2024-06-20T08:18:33+02:00 WARN client/internal/dns/upstream.go:184: probing upstream nameserver 192.168.40.168:53: read udp 192.168.25.40:59355->192.168.40.168:53: i/o timeout
2024-06-20T08:18:33+02:00 WARN client/internal/dns/upstream.go:184: probing upstream nameserver 192.168.40.68:53: read udp 192.168.25.40:59354->192.168.40.68:53: i/o timeout
2024-06-20T08:18:33+02:00 WARN client/internal/dns/upstream.go:262: Upstream resolving is Disabled for 30s

Something is definitely wrong with communication after 0.28.0 update please take look at this issue... 😢

I have exactly the same issue here. The strange thing is, that even in our internal network the clients are not able to resolve our internal domain anymore. My only solution is to reinstall the client and hope that it does not happen again...but it happens again.

Does anyone know how to fix the dns resolver when it has crashed?

Im using v.028.9 on Windows 11 (selfhosted)

@Riza-Aslan commented on GitHub (Jan 27, 2025): > I am having same problem running new 0.28.0 version. And i am also self hosting. > > `WARN [error: read udp 192.168.25.40:56297->192.168.40.168:53: i/o timeout, upstream: 192.168.40.168:53] client/internal/dns/upstream.go:101: got an error while connecting to upstream` > > DNS_PROBE_FINISHED_NXDOMAIN > > I have 2 DNS servers running in private network and i have created network route to this subnet so that anyone who is connected to vpn can access these DNS servers (one of them 192.168.40.168). But for some reason after 0.28.0 update i am only experiencing issues with internal domain resolutions and i am seeing file getting created every 10 seconds. > > And if i am trying to open internal domain client connection breaks since i can see my peer disappearing from dashboard and following files/logs are written... > > `unclean_shutdown_dns.txt` with some strange id inside.. > > ``` > 2024-06-20T08:18:33+02:00 WARN client/internal/dns/upstream.go:184: probing upstream nameserver 192.168.40.168:53: read udp 192.168.25.40:59355->192.168.40.168:53: i/o timeout > 2024-06-20T08:18:33+02:00 WARN client/internal/dns/upstream.go:184: probing upstream nameserver 192.168.40.68:53: read udp 192.168.25.40:59354->192.168.40.68:53: i/o timeout > 2024-06-20T08:18:33+02:00 WARN client/internal/dns/upstream.go:262: Upstream resolving is Disabled for 30s > ``` > > Something is definitely wrong with communication after 0.28.0 update please take look at this issue... 😢 I have exactly the same issue here. The strange thing is, that even in our internal network the clients are not able to resolve our internal domain anymore. My only solution is to reinstall the client and hope that it does not happen again...but it happens again. Does anyone know how to fix the dns resolver when it has crashed? Im using v.028.9 on Windows 11 (selfhosted)
saavagebueno commented 2025-11-20 05:21:20 -05:00
Author
Owner
Copy Link

@ptpu commented on GitHub (Mar 18, 2025):

Same issue here. I'm running 0.38.2 on all connected devices/server. At irregular intervals the DNS resolutions probe fails and the DNS server is marked as offline (timeout).

I have the local dns configured in the NetBird UI. Also I have configured an access policy allowing clients to connect to the server which is running dns on port UDP 53. When deactivating this rule and immediately activating it again, the dns server is marked as available on all the clients. Could this be a ACL bug?

Image

@ptpu commented on GitHub (Mar 18, 2025): Same issue here. I'm running 0.38.2 on all connected devices/server. At irregular intervals the DNS resolutions probe fails and the DNS server is marked as offline (timeout). I have the local dns configured in the NetBird UI. Also I have configured an access policy allowing clients to connect to the server which is running dns on port UDP 53. When deactivating this rule and immediately activating it again, the dns server is marked as available on all the clients. Could this be a ACL bug? ![Image](https://github.com/user-attachments/assets/369416d1-0e5e-4987-a73a-61d8b87fa6ea)
saavagebueno commented 2025-11-20 05:21:20 -05:00
Author
Owner
Copy Link

@scroguard commented on GitHub (Mar 20, 2025):

i too have this issue, for me it started in 0.38.2. however it's happening on more than just my dns access policies. i have had to toggle all my various policies off and then back on again to restore connectivity. at this point i have not been able to pinpoint anything that could be the root cause of the issue, thus i too wonder if it's an ACL bug.

Same issue here. I'm running 0.38.2 on all connected devices/server. At irregular intervals the DNS resolutions probe fails and the DNS server is marked as offline (timeout).

I have the local dns configured in the NetBird UI. Also I have configured an access policy allowing clients to connect to the server which is running dns on port UDP 53. When deactivating this rule and immediately activating it again, the dns server is marked as available on all the clients. Could this be a ACL bug?

Image

@scroguard commented on GitHub (Mar 20, 2025): i too have this issue, for me it started in 0.38.2. however it's happening on more than just my dns access policies. i have had to toggle all my various policies off and then back on again to restore connectivity. at this point i have not been able to pinpoint anything that could be the root cause of the issue, thus i too wonder if it's an ACL bug. > Same issue here. I'm running 0.38.2 on all connected devices/server. At irregular intervals the DNS resolutions probe fails and the DNS server is marked as offline (timeout). > > I have the local dns configured in the NetBird UI. Also I have configured an access policy allowing clients to connect to the server which is running dns on port UDP 53. When deactivating this rule and immediately activating it again, the dns server is marked as available on all the clients. Could this be a ACL bug? > > ![Image](https://github.com/user-attachments/assets/369416d1-0e5e-4987-a73a-61d8b87fa6ea)
saavagebueno commented 2025-11-20 05:21:20 -05:00
Author
Owner
Copy Link

@William-BCLabs commented on GitHub (Apr 7, 2025):

Having this issue with random peers on 39.2 as well. Have not worked on pinpointing the root cause just that it seems to mostly affect m1+ macbooks (but not all)

@William-BCLabs commented on GitHub (Apr 7, 2025): Having this issue with random peers on 39.2 as well. Have not worked on pinpointing the root cause just that it seems to mostly affect m1+ macbooks (but not all)
saavagebueno commented 2025-11-20 05:21:21 -05:00
Author
Owner
Copy Link

@nazarewk commented on GitHub (Apr 7, 2025):

@William-BCLabs since a lot of time has passed since the previous reports, could you enable trace logs and share a debug bundle after you observe the issue? You can send the logs to support at netbird.io or to kdn on the Slack.

see https://docs.netbird.io/how-to/troubleshooting-client#enabling-debug-logs-on-agent

@nazarewk commented on GitHub (Apr 7, 2025): @William-BCLabs since a lot of time has passed since the previous reports, could you enable trace logs and share a debug bundle after you observe the issue? You can send the logs to support at netbird.io or to `kdn` on the Slack. see https://docs.netbird.io/how-to/troubleshooting-client#enabling-debug-logs-on-agent
saavagebueno commented 2025-11-20 05:21:21 -05:00
Author
Owner
Copy Link

@lepazca commented on GitHub (Jul 30, 2025):

While doing some tests, I ran into DNS resolution issues for resources associated with a network, similar to what's described in this issue.

After enabling debug mode, I noticed that DNS queries were timing out when trying to reach the IP of the routing peer. It turned out that the firewall was enabled and blocking the traffic.

Once I added rules to allow traffic on ports 53 and 5353, DNS resolution started working as expected.

Hope this helps others running into the same problem.

@lepazca commented on GitHub (Jul 30, 2025): While doing some tests, I ran into DNS resolution issues for resources associated with a network, similar to what's described in this issue. After enabling debug mode, I noticed that DNS queries were timing out when trying to reach the IP of the routing peer. It turned out that the firewall was enabled and blocking the traffic. Once I added rules to allow traffic on ports 53 and 5353, DNS resolution started working as expected. Hope this helps others running into the same problem.
saavagebueno commented 2025-11-20 05:21:21 -05:00
Author
Owner
Copy Link

@cmonty14 commented on GitHub (Oct 3, 2025):

Hi,
I'm facing the same issue after upgrading to netbird 0.59.2.
I'm running a mailserver on Debian 12 with unbound DNS resolver.

tcp        0      0 127.0.0.1:53            0.0.0.0:*               LISTEN      19996/unbound       
tcp        0      0 127.0.0.1:5953          0.0.0.0:*               LISTEN      1/init              
tcp6       0      0 ::1:5953                :::*                    LISTEN      1/init              
tcp6       0      0 ::1:53                  :::*                    LISTEN      19996/unbound       
udp        0      0 127.0.0.1:53            0.0.0.0:*                           19996/unbound       
udp6       0      0 ::1:53                  :::*                                19996/unbound

Creating debug bundle fails with this error:
Error: failed to restore log level: connect client not initialized

When netbird is up, I get this /etc/resolv.conf:

# Generated by resolvconf
search netbird.cloud
nameserver ::1
nameserver 127.0.0.1
options trust-ad
options trust-ad

Please advise how to fix this issue.

@cmonty14 commented on GitHub (Oct 3, 2025): Hi, I'm facing the same issue after upgrading to _netbird 0.59.2_. I'm running a mailserver on Debian 12 with [unbound DNS resolver](https://github.com/NLnetLabs/unbound). ``` tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 19996/unbound tcp 0 0 127.0.0.1:5953 0.0.0.0:* LISTEN 1/init tcp6 0 0 ::1:5953 :::* LISTEN 1/init tcp6 0 0 ::1:53 :::* LISTEN 19996/unbound udp 0 0 127.0.0.1:53 0.0.0.0:* 19996/unbound udp6 0 0 ::1:53 :::* 19996/unbound ``` Creating debug bundle fails with this error: `Error: failed to restore log level: connect client not initialized` When netbird is up, I get this _/etc/resolv.conf_: ``` # Generated by resolvconf search netbird.cloud nameserver ::1 nameserver 127.0.0.1 options trust-ad options trust-ad ``` Please advise how to fix this issue.
saavagebueno commented 2025-11-20 05:21:21 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Oct 3, 2025):

Hello Thomas,

Can you please ensure netbird up was executed?

If it still doesn't work, please share the log files below:

C:\ProgramData\NetBird\client.log

C:\ProgramData\NetBird\netbird.err

Best,
Maycon
CTO & Co-Founder

On Fri, Oct 3, 2025, 4:56 PM Thomas @.***> wrote:

cmonty14 left a comment (netbirdio/netbird#2157)
https://github.com/netbirdio/netbird/issues/2157#issuecomment-3366049237

Hi,
I'm facing the same issue after upgrading to netbird 0.59.2.
I'm running a mailserver on Debian 12 with unbound DNS resolver
https://github.com/NLnetLabs/unbound.

Creating debug bundle fails with this error:
Error: failed to restore log level: connect client not initialized

Please advise how to fix this issue.

—
Reply to this email directly, view it on GitHub
https://github.com/netbirdio/netbird/issues/2157#issuecomment-3366049237,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB3DRIEW3QWX76IJDY3AEYT3V2FCDAVCNFSM6AAAAABV5PEDUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGNRWGA2DSMRTG4
.
You are receiving this because you were mentioned.Message ID:
@.***>

@mlsmaycon commented on GitHub (Oct 3, 2025): Hello Thomas, Can you please ensure netbird up was executed? If it still doesn't work, please share the log files below: C:\ProgramData\NetBird\client.log C:\ProgramData\NetBird\netbird.err Best, Maycon CTO & Co-Founder On Fri, Oct 3, 2025, 4:56 PM Thomas ***@***.***> wrote: > *cmonty14* left a comment (netbirdio/netbird#2157) > <https://github.com/netbirdio/netbird/issues/2157#issuecomment-3366049237> > > Hi, > I'm facing the same issue after upgrading to *netbird 0.59.2*. > I'm running a mailserver on Debian 12 with unbound DNS resolver > <https://github.com/NLnetLabs/unbound>. > > Creating debug bundle fails with this error: > Error: failed to restore log level: connect client not initialized > > Please advise how to fix this issue. > > — > Reply to this email directly, view it on GitHub > <https://github.com/netbirdio/netbird/issues/2157#issuecomment-3366049237>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AB3DRIEW3QWX76IJDY3AEYT3V2FCDAVCNFSM6AAAAABV5PEDUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGNRWGA2DSMRTG4> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >
saavagebueno commented 2025-11-20 05:21:21 -05:00
Author
Owner
Copy Link

@cmonty14 commented on GitHub (Oct 7, 2025):

Hello Thomas,

Can you please ensure netbird up was executed?

If it still doesn't work, please share the log files below:

C:\ProgramData\NetBird\client.log

C:\ProgramData\NetBird\netbird.err

Best,
Maycon
CTO & Co-Founder
…

I reproduced the issue on 2025-10-07T07:42, created debug bundle and attached it here.
Imo the relevant error is:

2025-10-07T07:42:14+02:00 ERRO [request_id: 48a8b80f] client/internal/dns/upstream.go:214: all queries to the Upstream [[::1]:
53 127.0.0.1:53] failed for question domain=94.107.30.81.in-addr.arpa.
2025-10-07T07:42:14+02:00 WARN [request_id: ac91bb5a] client/internal/dns/upstream.go:200: upstream 127.0.0.1:53 timed out for
 question domain=94.107.30.81.in-addr.arpa. after 2.5s (timeout=2.5s) - error: with udp: read udp 127.0.0.1:47998->127.0.0.1:53: i/o timeout

While netbird debug was running (for 30s) I executed nslookup that returned this error:

# nslookup oracle.com
;; communications error to ::1#53: timed out
;; communications error to ::1#53: timed out
;; communications error to ::1#53: timed out
;; communications error to 127.0.0.1#53: timed out
;; no servers could be reached

Note: Peer is running on Ubuntu (not Windows).

netbird.debug.1881625687.zip

@cmonty14 commented on GitHub (Oct 7, 2025): > Hello Thomas, > > Can you please ensure netbird up was executed? > > If it still doesn't work, please share the log files below: > > C:\ProgramData\NetBird\client.log > > C:\ProgramData\NetBird\netbird.err > > > Best, > Maycon > CTO & Co-Founder > […](#) I reproduced the issue on _2025-10-07T07:42_, created debug bundle and attached it here. Imo the relevant error is: ``` 2025-10-07T07:42:14+02:00 ERRO [request_id: 48a8b80f] client/internal/dns/upstream.go:214: all queries to the Upstream [[::1]: 53 127.0.0.1:53] failed for question domain=94.107.30.81.in-addr.arpa. 2025-10-07T07:42:14+02:00 WARN [request_id: ac91bb5a] client/internal/dns/upstream.go:200: upstream 127.0.0.1:53 timed out for question domain=94.107.30.81.in-addr.arpa. after 2.5s (timeout=2.5s) - error: with udp: read udp 127.0.0.1:47998->127.0.0.1:53: i/o timeout ``` While netbird debug was running (for 30s) I executed `nslookup` that returned this error: ``` # nslookup oracle.com ;; communications error to ::1#53: timed out ;; communications error to ::1#53: timed out ;; communications error to ::1#53: timed out ;; communications error to 127.0.0.1#53: timed out ;; no servers could be reached ``` Note: Peer is running on Ubuntu (not Windows). [netbird.debug.1881625687.zip](https://github.com/user-attachments/files/22735614/netbird.debug.1881625687.zip)
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 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#995
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?