[GH-ISSUE #2157] DNS resolution fails when running a local resolver #4431

New Issue

saavagebueno · 2026-08-05T00:57:41-04:00

saavagebueno commented

2026-08-05 00:57:41 -04:00

Originally created by @MDMeridio001 on GitHub (Jun 19, 2024).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/2157

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:

Run "netbird up" on the peer
Run "dig google.com @127.0.0.1" on the peer
dig command results in ";; communications error to 127.0.0.1#53: timed out"
Run "netbird down" on the peer
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). Original GitHub issue: https://github.com/netbirdio/netbird/issues/2157 **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 bug client dns labels 2026-08-05 00:57:41 -04:00

saavagebueno commented

2026-08-05 00:57:41 -04:00

@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

2026-08-05 00:57:41 -04:00

@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

2026-08-05 00:57:41 -04:00

@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

2026-08-05 00:57:41 -04:00

@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

2026-08-05 00:57:41 -04:00

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

Having same issue here.

@yaneony commented on GitHub (Jun 20, 2024): Having same issue here.

saavagebueno commented

2026-08-05 00:57:41 -04:00

@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

2026-08-05 00:57:41 -04:00

@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

2026-08-05 00:57:41 -04:00

@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

2026-08-05 00:57:42 -04:00

@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

2026-08-05 00:57:42 -04:00

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

@nikolicjakov both of them.

@MDMeridio001 commented on GitHub (Jun 20, 2024): @nikolicjakov both of them.

saavagebueno commented

2026-08-05 00:57:42 -04:00

@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

2026-08-05 00:57:42 -04:00

@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

2026-08-05 00:57:42 -04:00

@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

2026-08-05 00:57:42 -04:00

@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

2026-08-05 00:57:42 -04:00

@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?

@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

2026-08-05 00:57:42 -04:00

@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?

@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

2026-08-05 00:57:42 -04:00

@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

2026-08-05 00:57:42 -04:00

@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

2026-08-05 00:57:42 -04:00

@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

2026-08-05 00:57:42 -04:00

@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

2026-08-05 00:57:42 -04:00

@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

2026-08-05 00:57:42 -04:00

@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)

saavagebueno commented

2026-08-05 00:57:42 -04:00

@TuXbOy06 commented on GitHub (Dec 22, 2025):

Hello everyone,

Any updates about this issue ? I am having the same problem here...

Thanks

@TuXbOy06 commented on GitHub (Dec 22, 2025): Hello everyone, Any updates about this issue ? I am having the same problem here... Thanks

saavagebueno commented

2026-08-05 00:57:42 -04:00

@openapphub commented on GitHub (Jan 15, 2026):

Any updates about this issue ? I am having the same problem here...

 [WARNING] DNS (0116e0d7-922b-4802-b5ba-7d38ef1cfae5)
    Message: All upstream servers failed (probe failed)
    Time: 3 minutes, 3 seconds ago
    Metadata: upstreams: 1.1.1.1:53, 1.0.0.1:53
  [WARNING] DNS (bc9564c6-6fb5-4753-9dea-de0299dd7fd4)
    Message: All upstream servers failed (probe failed)
    Time: 3 minutes, 3 seconds ago
    Metadata: upstreams: 8.8.8.8:53, 8.8.4.4:53
  [INFO] SYSTEM (681e18cc-833e-471b-92c7-8365fdaee554)
    Message: Network map updated
    Time: 3 minutes, 3 seconds ago
  [WARNING] DNS (1873be64-da6c-400d-98f2-5c21565b3028)
    Message: All upstream servers failed (probe failed)
    Time: 21 seconds ago
    Metadata: upstreams: 1.1.1.1:53, 1.0.0.1:53
  [WARNING] DNS (f2fa2c3d-f3d7-4f91-8e45-71ca1ba8d652)
    Message: All upstream servers failed (probe failed)
    Time: 21 seconds ago
    Metadata: upstreams: 8.8.8.8:53, 8.8.4.4:53
  [INFO] SYSTEM (37b22f26-aa15-4d05-a8f3-99ebf7a7d386)
    Message: Network map updated
    Time: 21 seconds ago
Nameservers: 
  [1.1.1.1:53, 1.0.0.1:53] for [.] is Available
  [8.8.8.8:53, 8.8.4.4:53] for [.] is Available
  [223.5.5.5:53, 223.6.6.6:53] for [.] is Available
  [127.0.0.1:53] for [.] is Available

root@ImmortalWrt:~# nslookup www.google.com 100.64.37.8
nslookup: write to '100.64.37.8': Required key not available
;; connection timed out; no servers could be reached

root@ImmortalWrt:~# nslookup www.google.com 127.0.0.1
Server:         127.0.0.1
Address:        127.0.0.1:53

Non-authoritative answer:
Name:   www.google.com
Address: 142.251.42.164

Non-authoritative answer:

@openapphub commented on GitHub (Jan 15, 2026): Any updates about this issue ? I am having the same problem here... ``` [WARNING] DNS (0116e0d7-922b-4802-b5ba-7d38ef1cfae5) Message: All upstream servers failed (probe failed) Time: 3 minutes, 3 seconds ago Metadata: upstreams: 1.1.1.1:53, 1.0.0.1:53 [WARNING] DNS (bc9564c6-6fb5-4753-9dea-de0299dd7fd4) Message: All upstream servers failed (probe failed) Time: 3 minutes, 3 seconds ago Metadata: upstreams: 8.8.8.8:53, 8.8.4.4:53 [INFO] SYSTEM (681e18cc-833e-471b-92c7-8365fdaee554) Message: Network map updated Time: 3 minutes, 3 seconds ago [WARNING] DNS (1873be64-da6c-400d-98f2-5c21565b3028) Message: All upstream servers failed (probe failed) Time: 21 seconds ago Metadata: upstreams: 1.1.1.1:53, 1.0.0.1:53 [WARNING] DNS (f2fa2c3d-f3d7-4f91-8e45-71ca1ba8d652) Message: All upstream servers failed (probe failed) Time: 21 seconds ago Metadata: upstreams: 8.8.8.8:53, 8.8.4.4:53 [INFO] SYSTEM (37b22f26-aa15-4d05-a8f3-99ebf7a7d386) Message: Network map updated Time: 21 seconds ago Nameservers: [1.1.1.1:53, 1.0.0.1:53] for [.] is Available [8.8.8.8:53, 8.8.4.4:53] for [.] is Available [223.5.5.5:53, 223.6.6.6:53] for [.] is Available [127.0.0.1:53] for [.] is Available ``` ``` root@ImmortalWrt:~# nslookup www.google.com 100.64.37.8 nslookup: write to '100.64.37.8': Required key not available ;; connection timed out; no servers could be reached root@ImmortalWrt:~# nslookup www.google.com 127.0.0.1 Server: 127.0.0.1 Address: 127.0.0.1:53 Non-authoritative answer: Name: www.google.com Address: 142.251.42.164 Non-authoritative answer: ```

saavagebueno commented

2026-08-05 00:57:43 -04:00

@sandroshu commented on GitHub (Mar 25, 2026):

I also get notifications about DNS issues.
The NS servers for specific domains provided in NetBird are available over Peers. I read in the forum that Netbird tries DNS first, then connects to network then retry DNS. Is it possible to change this order to connect to network first and then try DNS first if this is the case?

forum

First is a peer directly, then the other 2 are routed by another peer.

Events:
  [INFO] SYSTEM (56670c61-a332-4ee6-8816-36ddbb05a3d7)
    Message: Network map updated
    Time: 7 minutes, 55 seconds ago
  [WARNING] DNS (e6bc1ca3-f7d6-45f9-bc3c-fbefe511ef92)
    Message: All upstream servers failed (probe failed)
    Time: 7 minutes, 55 seconds ago
    Metadata: upstreams: 100.104.146.233:53
  [WARNING] DNS (30ef77d2-0cda-4544-9d86-fe64a085ee78)
    Message: All upstream servers failed (probe failed)
    Time: 7 minutes, 55 seconds ago
    Metadata: upstreams: 192.168.10.254:53
  [WARNING] DNS (d2f5e540-8ac0-4b7f-bffe-13ef676a776b)
    Message: All upstream servers failed (probe failed)
    Time: 7 minutes, 55 seconds ago
    Metadata: upstreams: 192.168.10.254:53

@sandroshu commented on GitHub (Mar 25, 2026): I also get notifications about DNS issues. The NS servers for specific domains provided in NetBird are available over Peers. I read in the forum that Netbird tries DNS first, then connects to network then retry DNS. Is it possible to change this order to connect to network first and then try DNS first if this is the case? [forum](https://forum.netbird.io/t/unable-to-reach-one-or-more-dns-servers/204/4) First is a peer directly, then the other 2 are routed by another peer. ``` Events: [INFO] SYSTEM (56670c61-a332-4ee6-8816-36ddbb05a3d7) Message: Network map updated Time: 7 minutes, 55 seconds ago [WARNING] DNS (e6bc1ca3-f7d6-45f9-bc3c-fbefe511ef92) Message: All upstream servers failed (probe failed) Time: 7 minutes, 55 seconds ago Metadata: upstreams: 100.104.146.233:53 [WARNING] DNS (30ef77d2-0cda-4544-9d86-fe64a085ee78) Message: All upstream servers failed (probe failed) Time: 7 minutes, 55 seconds ago Metadata: upstreams: 192.168.10.254:53 [WARNING] DNS (d2f5e540-8ac0-4b7f-bffe-13ef676a776b) Message: All upstream servers failed (probe failed) Time: 7 minutes, 55 seconds ago Metadata: upstreams: 192.168.10.254:53 ```

saavagebueno commented

2026-08-05 00:57:43 -04:00

@Crumar commented on GitHub (Apr 2, 2026):

I have started with a fresh install and face the same problem, but only in the docker container that is also running the management docker container (self hosted).

So I have public server running netbird-server and netbird-client in separate compose stacks.
The netbird-server is behind a separate traefik instance on the same host.

I also have a private server in my home network, running netbird-client as docker container.

local private server:

private-srv:/# netbird status -dA
Peers detail:
 netcup.netbird.selfhosted:
  NetBird IP: 100.114.93.45
  Public key: R/XdAJiLII7AHBqCR+rmcfXxD4IEhjr/GJajnR7VikQ=
  Status: Connected
  -- detail --
  Connection type: P2P
  ICE candidate (Local/Remote): srflx/host
  ICE candidate endpoints (Local/Remote): 172.24.0.1:33128/198.51.100.0:51820
  Relay server address: rels://netbird.anon-SEzhk.domain:443
  Last connection update: 34 seconds ago
  Last WireGuard handshake: 34 seconds ago
  Transfer status (received/sent) 124 B/212 B
  Quantum resistance: false
  Networks: -
  Latency: 12.798539ms

Events:
  [INFO] SYSTEM (f7713dda-4d07-4e68-b2bc-f81d121b9188)
    Message: Network map updated
    Time: 8 hours, 37 minutes ago
  [INFO] SYSTEM (546f9f6b-2239-41ba-8c04-fd5b94979e21)
    Message: Network map updated
    Time: 2 minutes, 50 seconds ago
  [INFO] SYSTEM (cff94515-056d-48e0-9210-b3a0818a3682)
    Message: Network map updated
    Time: 2 minutes, 13 seconds ago
  [INFO] SYSTEM (278a4d3e-cf15-4c1e-9b47-1e0914e1d73f)
    Message: Network map updated
    Time: 34 seconds ago
OS: linux/amd64
Daemon version: 0.67.1
CLI version: 0.67.1
Profile: default
Management: Connected to https://netbird.anon-SEzhk.domain:443
Signal: Connected to https://netbird.anon-SEzhk.domain:443
Relays: 
  [stun:netbird.anon-SEzhk.domain:3478] is Available
  [rels://netbird.anon-SEzhk.domain:443] is Available
Nameservers: 
FQDN: private-srv.netbird.selfhosted
NetBird IP: 100.114.82.206/16
Interface type: Kernel
Quantum resistance: false
Lazy connection: false
SSH Server: Disabled
Networks: -
Peers count: 1/1 Connected
private-srv:/# nslookup google.com
Server:         100.114.82.206
Address:        100.114.82.206:53

Non-authoritative answer:
Name:   google.com
Address: 142.250.186.78

Non-authoritative answer:
Name:   google.com
Address: 2a00:1450:4001:c0f::8a
Name:   google.com
Address: 2a00:1450:4001:c0f::65
Name:   google.com
Address: 2a00:1450:4001:c0f::64
Name:   google.com
Address: 2a00:1450:4001:c0f::66

Public server, client container

public-srv:/# netbird status -dA
Peers detail:
 drdocker.netbird.selfhosted:
  NetBird IP: 100.114.82.206
  Public key: nICaz3KMcZAnptZ92HcPOAvW4Lx+CNisKC5TqxmVFiY=
  Status: Connected
  -- detail --
  Connection type: P2P
  ICE candidate (Local/Remote): host/srflx
  ICE candidate endpoints (Local/Remote): 198.51.100.0:51820/198.51.100.1:51820
  Relay server address: rels://netbird.anon-z53bP.domain:443
  Last connection update: 27 seconds ago
  Last WireGuard handshake: 27 seconds ago
  Transfer status (received/sent) 212 B/124 B
  Quantum resistance: false
  Networks: -
  Latency: 13.070808ms

Events:
  [INFO] SYSTEM (e14e6eb9-f310-4c16-84af-67b6d6fab39a)
    Message: Network map updated
    Time: 27 seconds ago
OS: linux/amd64
Daemon version: 0.67.1
CLI version: 0.67.1
Profile: default
Management: Connected to https://netbird.anon-z53bP.domain:443
Signal: Connected to https://netbird.anon-z53bP.domain:443
Relays: 
  [stun:netbird.anon-z53bP.domain:3478] is Unavailable, reason: dial: failed to listen: dial udp: lookup netbird.anon-z53bP.domain on 100.114.93.45:53: server misbehaving
  [rels://netbird.anon-z53bP.domain:443] is Available
Nameservers: 
FQDN: public-srv.netbird.selfhosted
NetBird IP: 100.114.93.45/16
Interface type: Kernel
Quantum resistance: false
Lazy connection: false
SSH Server: Disabled
Networks: -
Peers count: 1/1 Connected
public-srv:/# nslookup google.com
Server:         100.114.93.45
Address:        100.114.93.45:53

** server can't find google.com: REFUSED

** server can't find google.com: REFUSED

public-srv:/# netbird down
Disconnected
public-srv:/# nslookup google.com
Server:         9.9.9.9
Address:        9.9.9.9:53

Non-authoritative answer:
Name:   google.com
Address: 2a00:1450:4001:c1f::71
Name:   google.com
Address: 2a00:1450:4001:c1f::65
Name:   google.com
Address: 2a00:1450:4001:c1f::8a
Name:   google.com
Address: 2a00:1450:4001:c1f::66

Non-authoritative answer:
Name:   google.com
Address: 142.251.143.110

Servers are not able to ping each other.
Both containers use the same setup, its just that one is running on the server that also hosts the netbird-server container

@Crumar commented on GitHub (Apr 2, 2026): I have started with a fresh install and face the same problem, but only in the docker container that is also running the management docker container (self hosted). So I have public server running netbird-server and netbird-client in separate compose stacks. The netbird-server is behind a separate traefik instance on the same host. I also have a private server in my home network, running netbird-client as docker container. # local private server: ``` private-srv:/# netbird status -dA Peers detail: netcup.netbird.selfhosted: NetBird IP: 100.114.93.45 Public key: R/XdAJiLII7AHBqCR+rmcfXxD4IEhjr/GJajnR7VikQ= Status: Connected -- detail -- Connection type: P2P ICE candidate (Local/Remote): srflx/host ICE candidate endpoints (Local/Remote): 172.24.0.1:33128/198.51.100.0:51820 Relay server address: rels://netbird.anon-SEzhk.domain:443 Last connection update: 34 seconds ago Last WireGuard handshake: 34 seconds ago Transfer status (received/sent) 124 B/212 B Quantum resistance: false Networks: - Latency: 12.798539ms Events: [INFO] SYSTEM (f7713dda-4d07-4e68-b2bc-f81d121b9188) Message: Network map updated Time: 8 hours, 37 minutes ago [INFO] SYSTEM (546f9f6b-2239-41ba-8c04-fd5b94979e21) Message: Network map updated Time: 2 minutes, 50 seconds ago [INFO] SYSTEM (cff94515-056d-48e0-9210-b3a0818a3682) Message: Network map updated Time: 2 minutes, 13 seconds ago [INFO] SYSTEM (278a4d3e-cf15-4c1e-9b47-1e0914e1d73f) Message: Network map updated Time: 34 seconds ago OS: linux/amd64 Daemon version: 0.67.1 CLI version: 0.67.1 Profile: default Management: Connected to https://netbird.anon-SEzhk.domain:443 Signal: Connected to https://netbird.anon-SEzhk.domain:443 Relays: [stun:netbird.anon-SEzhk.domain:3478] is Available [rels://netbird.anon-SEzhk.domain:443] is Available Nameservers: FQDN: private-srv.netbird.selfhosted NetBird IP: 100.114.82.206/16 Interface type: Kernel Quantum resistance: false Lazy connection: false SSH Server: Disabled Networks: - Peers count: 1/1 Connected private-srv:/# nslookup google.com Server: 100.114.82.206 Address: 100.114.82.206:53 Non-authoritative answer: Name: google.com Address: 142.250.186.78 Non-authoritative answer: Name: google.com Address: 2a00:1450:4001:c0f::8a Name: google.com Address: 2a00:1450:4001:c0f::65 Name: google.com Address: 2a00:1450:4001:c0f::64 Name: google.com Address: 2a00:1450:4001:c0f::66 ``` # Public server, client container ``` public-srv:/# netbird status -dA Peers detail: drdocker.netbird.selfhosted: NetBird IP: 100.114.82.206 Public key: nICaz3KMcZAnptZ92HcPOAvW4Lx+CNisKC5TqxmVFiY= Status: Connected -- detail -- Connection type: P2P ICE candidate (Local/Remote): host/srflx ICE candidate endpoints (Local/Remote): 198.51.100.0:51820/198.51.100.1:51820 Relay server address: rels://netbird.anon-z53bP.domain:443 Last connection update: 27 seconds ago Last WireGuard handshake: 27 seconds ago Transfer status (received/sent) 212 B/124 B Quantum resistance: false Networks: - Latency: 13.070808ms Events: [INFO] SYSTEM (e14e6eb9-f310-4c16-84af-67b6d6fab39a) Message: Network map updated Time: 27 seconds ago OS: linux/amd64 Daemon version: 0.67.1 CLI version: 0.67.1 Profile: default Management: Connected to https://netbird.anon-z53bP.domain:443 Signal: Connected to https://netbird.anon-z53bP.domain:443 Relays: [stun:netbird.anon-z53bP.domain:3478] is Unavailable, reason: dial: failed to listen: dial udp: lookup netbird.anon-z53bP.domain on 100.114.93.45:53: server misbehaving [rels://netbird.anon-z53bP.domain:443] is Available Nameservers: FQDN: public-srv.netbird.selfhosted NetBird IP: 100.114.93.45/16 Interface type: Kernel Quantum resistance: false Lazy connection: false SSH Server: Disabled Networks: - Peers count: 1/1 Connected public-srv:/# nslookup google.com Server: 100.114.93.45 Address: 100.114.93.45:53 ** server can't find google.com: REFUSED ** server can't find google.com: REFUSED public-srv:/# netbird down Disconnected public-srv:/# nslookup google.com Server: 9.9.9.9 Address: 9.9.9.9:53 Non-authoritative answer: Name: google.com Address: 2a00:1450:4001:c1f::71 Name: google.com Address: 2a00:1450:4001:c1f::65 Name: google.com Address: 2a00:1450:4001:c1f::8a Name: google.com Address: 2a00:1450:4001:c1f::66 Non-authoritative answer: Name: google.com Address: 142.251.143.110 ``` Servers are not able to ping each other. Both containers use the same setup, its just that one is running on the server that also hosts the netbird-server container

saavagebueno referenced this issue

2026-08-05 01:19:05 -04:00

[GH-ISSUE #4431] Windows: encrypt the sensitive config.json data #8662

saavagebueno referenced this issue

2026-08-05 01:20:53 -04:00

[GH-ISSUE #4431] Windows: encrypt the sensitive config.json data #9117

saavagebueno referenced this issue

2026-08-05 01:22:03 -04:00

[GH-ISSUE #4431] Windows: encrypt the sensitive config.json data #9417

Sign in to join this conversation.

Branches Tags

main

fix/custom-domain-validation

check-user-status

hardening/custom-domain-followups

feat-post_quantum_ml_kem

anonymize-level

embedded-vnc

mdm_integration

debug-ui-memprofile-lazy-windows

refactor/ui-lazy-windows

add-atomic-cache-ops

debug-ui-memprofile

feat/agent-network-per-account-serving

fix/wails-go-vendor

relay_transport_down_no_offer_storm

revert/component-types

wins_nrpt_dns_delegation

dependabot/github_actions/actions-a940c7c866

fix/quickstart-subnet-and-domain-alias

notification-localization

ssh-settings-elevation

refactor/peer-event-bus

fix/relay-proxy-redirect-when-ice-active

claude/agent-network-test-cases-p743vw

android/gui-integration

ice-stun-wg-demux

dependabot/npm_and_yarn/proxy/web/npm_and_yarn-b39864987c

agent-network-setup-poc

dependabot/go_modules/aws-sdk-8f849ebaed

dependabot/go_modules/otel-e34c790afd

dependabot/go_modules/testcontainers-de325c0dd6

dependabot/go_modules/wireguard-dbd6b95108

dependabot/go_modules/pion-5f703e1eca

dependabot/go_modules/gorm-2271c8195b

fix-login-needed-check

dependabot/go_modules/google.golang.org/grpc-1.82.1

revert/component-types-hookup

feature/ios-ssh

docs/agent-network-docs-update

dependabot/go_modules/github.com/aws/aws-sdk-go-v2/service/s3-1.106.3

dependabot/go_modules/github.com/pion/stun/v3-3.1.5

fix-ssh-authorized-users-multi-rule

peer-acl-multi-source

reverse-proxy-crowdsec-appsec

reverse-proxy-allow-match-or

client-local-metrics

lazy-conn-per-peer

lazy-conn-rosenpass

dependabot/go_modules/github.com/gopacket/gopacket-1.7.0

dependabot/go_modules/goauthentik.io/api/v3-3.2026050.6

dependabot/go_modules/github.com/pires/go-proxyproto-0.15.0

dependabot/go_modules/github.com/jackc/pgx/v5-5.10.0

dependabot/go_modules/github.com/oapi-codegen/runtime-1.6.0

dependabot/go_modules/github.com/eko/gocache/lib/v4-4.2.4

dependabot/go_modules/github.com/pkg/sftp-1.13.11

dependabot/go_modules/github.com/coreos/go-oidc/v3-3.20.0

ssh-windows-privilege-check

fix/explicit-cors-handling

fix/remove-math-rand

test/gui-memory-leak-fix

fix/ui-status-dispatch

install-script-ui-dependencies

fix/grpc-get-network-map

fix/subscribe-status-coalesce

fix/tray-menu-item-leak

fix/windows-tray-race

feature/changeset

worktree-dns-route-qtype-fallthrough

mlsmaycon-patch-2

feat/agent-network-ollama

proxy-tunnel-cache-ttl-env

coderabbitai/utg/1e5b0a5

grpc-acl

test/battery-drain

components-impl-drop-indexes-use-xids-no-resource-policy-map

fix/nmap-relevant-groups

e2e-guardrail-blocks-unselected-model

fix/lazyconn-cold-start-allowed-ips

vertex-guardrails-model-access-e2e

refactor/relay-foreign-cache

ci/trigger-release-tests

feature/kimi-3-agent-networks-dns-warmup

feature/dns-lazy-conn-warmup

daemon-ipc-acl

feature/ui-translation-key-parity-check

refactor/relay-foreign-cache-tests

fix/lazyconn-idle-keep-wg-peer

dmitri-propagate-auth-grant-types-on-combined

0.74.7-branch

diagnose-empty-vs-corrupt-state

windows-sleep-detector

fix/cli-up-wait-for-daemon

rp_key_persistency

feature/native-grpc

0.74.6-branch

0.74.6-branch-sync

0.74.5-branch-sync

0.74.4-branch

fix/remove-stale-peers-removal

fix/remove-stale-proxy-logic

fix/nsis-preserve-autostart-on-upgrade

dependabot/go_modules/goauthentik.io/api/v3-3.2026050.3

dependabot/go_modules/github.com/pkg/sftp-1.13.10

components-impl-drop-indexes

fix-reset-aggregation-window-flake

dependabot/go_modules/github.com/pion/dtls/v3-3.1.5

0.74.x

fix/relay-states-lock

update-process-pkg

update-gopsutil-v4

fix/relay_states_lock

increase-sysinfo-timeout

dependabot/go_modules/github.com/Azure/go-ntlmssp-0.1.1

dependabot/go_modules/github.com/eko/gocache/store/redis/v4-4.2.6

dependabot/go_modules/github.com/eko/gocache/lib/v4-4.2.3

fix/fail-to-create-upnp-port-mapping-on-opnsense-firewall

0.74.3-branch

fix/routeselector-atomic-exit-node

netmap_progressive_alignment

nmap/components-impl

dependabot/go_modules/github.com/jackc/pgx/v5-5.9.2

dependabot/go_modules/github.com/oapi-codegen/runtime-1.4.2

dependabot/go_modules/github.com/gopacket/gopacket-1.6.1

dependabot/go_modules/github.com/coreos/go-oidc/v3-3.19.0

dependabot/go_modules/github.com/pires/go-proxyproto-0.12.0

fix/signal-watchdog-sync-stop

docs/agent-network

test/affected-logic

fix/revert-ice-filter

refactor/simplify-affected-peers

pascal-filter-policies-by-direction

claude/lock-contention-peer-connect-g8t6au

dmitri-filter-policies-by-direction

refactor/migrate-profiles-to-go

profile-bindings-ios

fix/skip-restart-unchanged-route

fix/mgmt-cache-async-resolve

refactor/wails-update-105

client_lifetime_serialization_refactor

fix/browser-ssh-2

fix/ipv6-and-netstack-accept-loop

fix/browser-ssh

profile-id-name-test

refactor/mgmt-bootstrap

feat/getting-started-unified-wizard

socket-grpc-permissions

fix/mysql-index-migration

windows-dns-firewall

tests/enable-race-on-tests

ui-refactor-gtk3

feature/affected-peers-grpc

profile-id

lazyconn-first-packet-fix-v2

claude/focused-gates-VMTgb

ui-tray-linux-leftclick

fix/ctx-enrichment

daemon-owner

feature/android-client-ssh

worktree-accept-ra-forwarding

nmap/combined-deploy

task/align_protobuff_toolset

feature/session-extend

add-json-yaml-flags

refactor/ephemeral-cleanup

claude/webtransport-relay-wasm-mUjY9

claude/vnc-udp-feasibility-6KB1U

fix/wgport-config

e2e-windows-dns-combined

fix/login-cmd-root-flags

feat/reseller-openapi-spec

github-issue-resolver

add-steamos-support

fix-darwin-uninstaller

flutter-test

ci/freebsd-pkg-bootstrap

cached-serial-check-on-sync

fix-mgmt-cache-bypass-overlay

revert-easyjson-5938

revert-ice-5820

revert-firewalld-5928

refactor/permissions-manager

revert-dns-5935-systemd-resolved

revert-dns-5935-5945

revert-dns-5945-mgmt-cache

feature/log-most-busy-peers

prototype/ui-wails

coderabbitai/utg/8ae8f20

feature/use-peer-fqdn-on-https

release/0.68.3

add-slack-channel

claude/rdp-token-passthrough-eNcqW

transparent-proxy

fix/macos-stale-route-eexist

crowdsec-selfhosted

fix/remove-otel-units

entire/checkpoints/v1

fix/getting-started

feat/static-connectors-combined-server

feature/use-local-keys-embedded

feature/fleetdm

set-env-only-if-not-fork

feature/expose-has-channel

fix/connection-status-race

fix/filter-cgnat-cni-ice-candidates

feature/check-cert-locker-before-acme

test/proxy-fixes

test/proxy-mtu

prototype/ui-tauri

test/proxy-speed

fix-reused-ports

feat/migrate-to-embedded-idp

feature/add-serial-to-proxy-merged

deploy/proxy-serial

test/connection

feature/disable-legacy-port

feature/flag-to-disable-legacy-port

test/perftest

fix/http-redirect

poc-token-command

dn-reverse-proxy

prototype/reverse-proxy-rename

prototype/reverse-proxy-logs-pagination

feature/client-metrics

prototype/reverse-proxy-clusters

debug-dns-route

fix/win-dns-batch

add-extra-route-logs

job-stream-notify-disconnection-eof

deploy/secrets-manager

trigger-proxy-update

bug/update-ios-client-code-build-tags

sync-client-netmap-serial

log/conn-disconn

nmap/compaction-deploy

ci-win-test

feature/disk-encryption-check

wasm-debug

swap-dns-prio

fix/dex-config

feature/migrate-auto-groups-to-table

nmap/compaction

dex-nocgo-stub

feature/exclude-terraform-from-rate-limiting

test-freebsd

retries-refactor

coderabbitai/docstrings/b7e98ac

feat/integrate-zitadel

bug/ios-hanging-reconection

zitadel-idp

feat/network-map-serial

refactor/get-account-no-users

feat/auto-upgrade

feature/report-high-pat-id

feature/temporary-access-for-resource

fix/nmap-fwrules

dont-restart-dns

prototype/ui

update-gomobile

go-dns-for-ice

wasm-ldflags

test-ldflags

wasmbuild-test

feature/networks-s2s

vk/compare-nmaps

dbg/bothmaps

reorder-dns-shutdown

fix/relay-reconnection-race

fix/nmap-exitnodes

vk/debug/nmap-both

move-licensed-code

feat/better-daemon-connection-lost-message

feat/auto-update-2

test/timings

refactor/getaccount-raw

tests/nmap-getaccount

refactor/nmap

refactor/nmap-limit-buffer

feature/detect-mac-wakeup

feature/extract-modules

quick-setings

feat/sync-limiter

feature/store-cache-impl

fix-install-version

feature/store-metrics

feature/metrics-on-store

feature/use-gorm-cache

loadtest-signal

unsymmetrical-squash

refactor/reducate-signaling

test/update-reduce

feature/store-cache

feature/remote-debug

cli-ws-proxy-backend-addr

feat/mgmt-map-serial

snyk-fix-d9d0081a4c7f9137bdb59d0d50a141a2

snyk-fix-7415cea5a11acd66753540ca2c598c63

job-yml-update

feature/android-allow-selecting-routes

fix/up-sequence

fix/dns-hash-update

snyk-fix-967adae9863f17f108ce8948d9117b8d

log/getaccount-by-peer

signal-suppressor

dns-exit-node

feature/auto-updates

feature/cache-srv-key

merged-fixes

fix/missed-offers-and-debug

debug-and-fixes

poc-wasm-clean-backend-s2s

test/remote-debug

debug-api

fix/remove-gpo-if-empty

fix/test-freebsd

fix/mysql-setup

fix/remove-logout-btn

handle-existing-domain-user

chore/unify-domain-validation

snyk-fix-c5fafc8a50ce1f29046e25a1fc346185

feat/profile-edit-btn

snyk-fix-a54966211e18d4cf67e5a2757cc006d1

log-short-id

feat/logout-ephemeral

log-checks

batch-wg-ops

nb-interface-default

feat/aws-integration

add/race-test

feature/relay-feature-versioning

fix/systemd-service-logs

poc/preprocessed-map

add-account-onboarding

bind-ipv6

fix/merge-main

logs/peerlogs-addpeer

feature/net-297-network-migration

feature/support-skip-auto-apply-exit-node-routes

set-cmd

set-command-with-cursor

feature/limit-update-channel

stop-using-locking-share

feature/poc-lazy-detection

feature/net-248-removal-of-sync-mutex-locks

test/multiple-peer-logging

preresolve

add-ns-punnycode-support

apply-routes-early

windows-search-domains

fix/connecting-route-filter

feature/management/rest-client/impersonate

debug-local-records

resource-fields-snake-case

test/grpc-rate-limit

traffic-correlation-policy

feature/rest-client-options

feat/events-metrics

feature/buf-cli

test/add-ratelimiter

test/remove-write-lock-on-add-peer

fix/add-peer-semaphore

feature/users-roles-endpoint

mlsmaycon-patch-1

debug-user-role

chore/primary-key-on-networks

feature/update-account-peers-buffer-startup

remove-ubuntu2004-runners

refactor/permissions-no-pat-allowed

ref/logrus-factory

use-conntrack-zone

deploy/permissions-account

feature/lazy-connection-idle

ref/improve-test-cov

restore-pr-3440

test/increase-grpc-timeouts

feat/buffer-account-peers-update

test/networkmapgeneration-changes

feature/base-manager

feature/flow-receiver

chore/benchmark-with-large-runner

refactor/handshake-initiator

client/ui-update-systray-icons

userspace-router

wgwatcher-test

output-if-key-already-exists

fix/relay-reconnection

feature/port-forwarding-client-codecleaning

detached2

test/callbacks-nil-iceconninfo

refactor/optimize-peer-expiration

enable-udp-port-for-docker-template

fix/relay-update

feature/apply-posture-netmap

fix/group-update-existing-resource

conntrack-stats

upgrade-okta-sdk

multi-price

test/conn-stat

set-min-parallel-tests-for-management

dns-interceptor

debug-dns

router-dns

add-static-system-info

debug-0.29.4

debug-0.33.0

account-refactoring

relay/2800_quic

route-get-account-refactoring

test/seed-random-routes

feature/get-account-refactoring

test/reconnect-race-condition

refactor/get-account-usage

feature/add-session-id-to-update-channel

improve-ipv4conn

fix/async-pion-event-handling

debug

add-offload

feature/validate-group-association-debug

fix/limit-conn-for-sqlite

test/engine-iface

test/transaction-for-jwt-sync

fix/engine-stop-in-foreground

feature/add-mysql-support

test-migration

refactor/header-size-values

relay/eliminate-gob

test/signal-dispatcher-with-relay

relay/debug

validate-icon

feature/ipv6-support

use-pre-expanded-peers-map

feature/use-signal-dispatcher

validate/peer-status

add-read-write-times

fix/sync-peer-race

feature/relay-status

netmap

evaluate/network-map-hash

fix/lower-dns-resolve-interval-on-fail

feature/relay

fix/go-mod-version

upgrade-nftables

synology-userspace-mode

fix/use-ip-for-default-routes-on-darwin

fix/proxy_close

enable-release-workflow-on-pr

deploy/peer-performance

feature/permanent-turn

feature/permanent-turn-proxy

deploy/posture-check-sqlite

feature/optimize_sqlite_save

debug-ios-behavior

fix/delete-route-only-after-adding

tshoot/windows-logger

remove-new-routing

refactor/eliminate-repo-dependency

add-arm-to-ci

refactor-demo-account-object

test/abc2

test/abc

send-ssh-rosenpass-config-meta

refactor-demo

ensure-schedule-never-runs-non-positive

feature/peer-validator-groupmgm

feature/peer-validator-fix

fix/include-active-dashboard-users

fix/handle-canceling-schedule

fix/geo-download

debug-google-workspace

yury/resolve-ip-to-location

feature/extend-sysinfo

sqlite-async-peer-status

yury/add-postgresql-store

fix/route

test-build

posture-checks-poc

debug-keycloak-idp

poc/netstack

for-pascal-tmp

peer-logout-management

manual-peer-logout

detached

chore/refactor-management

test/dns-bind

fix/enforce-acl-for-containers

yury/use-sync-map-in-updatechannel

fix/events-key-handling

filter-cache-on-load-account

fix/user-expiration

handle-user-context-cancellation

nb-client-k8s-statefulset

fake-addr

fix/iptables_in_docker

ebpf-debug

update-getting-started-flow-use-postgres

fix/peer_list_notification

feature/device-authentication-with-client-secret

feature/keep_alive

feat-groups-from-jwt

separate_proxy_from_wgconfig

fix/wg_conn

wg_conn_fix

wg_bind_parallel_processing

fix-rollback-get-acls

proxy_cfg_cleanup

performance-improvement-rego

update-lock-log-level

feat-client-side-acl

refactor/move_grpcserver_logic_to_account_manager

feature/event-storage

feature/update-idp-redeeming-invite

feature/api-peer-info

return-groupminimum-setupkey

feature/interface-bind

documentation_enhancement

fix-peer-registration

ssh

users_cache

pass-client-caller

client_caller_type

revert-283-feat-fix-windows-installer

periodic-peer-updates

ebpf

braginini/wasm

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: DYNR/netbird#4431