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

Onconnect recurring DNS unreachable notification #2306

New Issue
Open
opened 2025-11-20 07:07:29 -05:00 by saavagebueno · 3 comments
saavagebueno commented 2025-11-20 07:07:29 -05:00
Owner
Copy Link

Originally created by @tomashora on GitHub (Sep 24, 2025).

Describe the problem

After each connection, the DNS notification pops up multiple times. Sometimes it pops up only 2-3 times sometimes it almost newe stops so it's better do disable notification which has to be done while disconnected because the notification repeatedly covers the settings menu.

The private DNS server is reachable as a peer and distributed in group All so it may take some time for the DNS to be reachable.

To Reproduce

Steps to reproduce the behavior:

  1. Connect with enabled notifications
  2. DNS unrechable is displayed

Expected behavior

The DNS notification could be displayed after longer period.

Are you using NetBird Cloud?

Self-hosted

NetBird version

0.58.1

Is any other VPN software installed?

No

Debug output

1ddeb81b5637b00d27b906270508c117cf46cb4d0b768e79b281a23a281098c8/cbb6dae5-e28f-4388-8fdc-e4efb838cbde

Screenshots

Image

Additional context

Have you tried these troubleshooting steps?

  • Reviewed client troubleshooting (if applicable)
  • Checked for newer NetBird versions
  • Searched for similar issues on GitHub (including closed ones)
  • Restarted the NetBird client
  • Disabled other VPN software
  • Checked firewall settings
Originally created by @tomashora on GitHub (Sep 24, 2025). **Describe the problem** After each connection, the DNS notification pops up multiple times. Sometimes it pops up only 2-3 times sometimes it almost newe stops so it's better do disable notification which has to be done while disconnected because the notification repeatedly covers the settings menu. The private DNS server is reachable as a peer and distributed in group All so it may take some time for the DNS to be reachable. **To Reproduce** Steps to reproduce the behavior: 1. Connect with enabled notifications 2. DNS unrechable is displayed **Expected behavior** The DNS notification could be displayed after longer period. **Are you using NetBird Cloud?** Self-hosted **NetBird version** 0.58.1 **Is any other VPN software installed?** No **Debug output** 1ddeb81b5637b00d27b906270508c117cf46cb4d0b768e79b281a23a281098c8/cbb6dae5-e28f-4388-8fdc-e4efb838cbde **Screenshots** <img width="415" height="295" alt="Image" src="https://github.com/user-attachments/assets/da86b021-f7df-497a-adf3-15bd9bcc4568" /> **Additional context** **Have you tried these troubleshooting steps?** - [x] Reviewed [client troubleshooting](https://docs.netbird.io/how-to/troubleshooting-client) (if applicable) - [x] Checked for newer NetBird versions - [x] Searched for similar issues on GitHub (including closed ones) - [x] Restarted the NetBird client - [x] Disabled other VPN software - [x] Checked firewall settings
saavagebueno added the triage-needed label 2025-11-20 07:07:29 -05:00
saavagebueno commented 2025-11-20 07:07:31 -05:00
Author
Owner
Copy Link

@tkloda commented on GitHub (Sep 24, 2025):

I can confirm this warning appears consistently across Linux, macOS, and Windows clients. It's generated upon every successful connection to the VPN.

The primary issue is the user confusion this causes. Although the warning is displayed, DNS resolution works perfectly, suggesting the warning is a false positive.

Could this be a race condition? It seems the warning may be triggered prematurely, before the DNS subsystem has fully initialized.

@tkloda commented on GitHub (Sep 24, 2025): I can confirm this warning appears consistently across Linux, macOS, and Windows clients. It's generated upon every successful connection to the VPN. The primary issue is the user confusion this causes. Although the warning is displayed, DNS resolution works perfectly, suggesting the warning is a false positive. Could this be a race condition? It seems the warning may be triggered prematurely, before the DNS subsystem has fully initialized.
saavagebueno commented 2025-11-20 07:07:31 -05:00
Author
Owner
Copy Link

@Lirok228 commented on GitHub (Sep 26, 2025):

I can confirm I’m experiencing the same issue. The DNS servers do become reachable after a short period of time, but the client still shows the “DNS unreachable” warning.
Is there a way to either increase the TTL/grace period before triggering this warning, or are there any other recommended workarounds to mitigate the problem?

2025-09-26T22:50:59+03:00 WARN [request_id: d26cfaff] client/internal/dns/upstream.go:200: upstream 192.168.102.105:53 timed out for question domain=lb._dns-sd._udp.mydomaintest.ru. after 2s (timeout=2s) (routes through NetBird peer peer-t-vpn03.netbird.selfhosted:100.64.56.216 NO_RECENT_HANDSHAKE no_handshake via_relay) - error: with udp: read udp 192.168.0.25:60741->192.168.102.105:53: i/o timeout
2025-09-26T22:50:59+03:00 WARN [request_id: 33482a54] client/internal/dns/upstream.go:200: upstream 192.168.102.105:53 timed out for question domain=lb._dns-sd._udp.mydomaintestrus.ru. after 2s (timeout=2s) (routes through NetBird peer peer-t-vpn03.netbird.selfhosted:100.64.56.216 NO_RECENT_HANDSHAKE no_handshake via_relay) - error: with udp: read udp 192.168.0.25:61674->192.168.102.105:53: i/o timeout
2025-09-26T22:50:59+03:00 WARN [request_id: 6de4cd11] client/internal/dns/upstream.go:200: upstream 192.168.102.105:53 timed out for question domain=lb._dns-sd._udp.mydomaintestrus.hrdoc.ru. after 2s (timeout=2s) (routes through NetBird peer peer-t-vpn03.netbird.selfhosted:100.64.56.216 NO_RECENT_HANDSHAKE no_handshake via_relay) - error: with udp: read udp 192.168.0.25:55347->192.168.102.105:53: i/o timeout
2025-09-26T22:50:59+03:00 WARN [request_id: 401f2cd9] client/internal/dns/upstream.go:200: upstream 192.168.102.105:53 timed out for question domain=lb._dns-sd._udp.mydomaintest.ru. after 2s (timeout=2s) (routes through NetBird peer peer-t-vpn03.netbird.selfhosted:100.64.56.216 NO_RECENT_HANDSHAKE no_handshake via_relay) - error: with udp: read udp 192.168.0.25:62773->192.168.102.105:53: i/o timeout
2025-09-26T22:50:59+03:00 WARN [request_id: e2971d9b] client/internal/dns/upstream.go:200: upstream 192.168.102.105:53 timed out for question domain=lb._dns-sd._udp.mydomaintestrus.ru. after 2s (timeout=2s) (routes through NetBird peer peer-t-vpn03.netbird.selfhosted:100.64.56.216 NO_RECENT_HANDSHAKE no_handshake via_relay) - error: with udp: read udp 192.168.0.25:54385->192.168.102.105:53: i/o timeout
2025-09-26T22:50:59+03:00 WARN [request_id: e693d6d2] client/internal/dns/upstream.go:200: upstream 192.168.102.105:53 timed out for question domain=lb._dns-sd._udp.mydomaintestrus.hrdoc.ru. after 2s (timeout=2s) (routes through NetBird peer peer-t-vpn03.netbird.selfhosted:100.64.56.216 NO_RECENT_HANDSHAKE no_handshake via_relay) - error: with udp: read udp 192.168.0.25:55441->192.168.102.105:53: i/o timeout
2025-09-26T22:50:59+03:00 WARN [request_id: f91897af] client/internal/dns/upstream.go:200: upstream 192.168.102.105:53 timed out for question domain=lb._dns-sd._udp.mydomaintestrus.ru. after 2s (timeout=2s) (routes through NetBird peer peer-t-vpn03.netbird.selfhosted:100.64.56.216 NO_RECENT_HANDSHAKE no_handshake via_relay) - error: with udp: read udp 100.64.143.59:54984->192.168.102.105:53: i/o timeout
2025-09-26T22:50:59+03:00 WARN [request_id: b6b4cdca] client/internal/dns/upstream.go:200: upstream 192.168.102.105:53 timed out for question domain=lb._dns-sd._udp.mydomaintestrus.hrdoc.ru. after 2s (timeout=2s) (routes through NetBird peer peer-t-vpn03.netbird.selfhosted:100.64.56.216 NO_RECENT_HANDSHAKE no_handshake via_relay) - error: with udp: read udp 100.64.143.59:52787->192.168.102.105:53: i/o timeout
2025-09-26T22:50:59+03:00 WARN [request_id: a1c55e29] client/internal/dns/upstream.go:200: upstream 192.168.102.105:53 timed out for question domain=lb._dns-sd._udp.mydomaintest.ru. after 2s (timeout=2s) (routes through NetBird peer peer-t-vpn03.netbird.selfhosted:100.64.56.216 NO_RECENT_HANDSHAKE no_handshake via_relay) - error: with udp: read udp 100.64.143.59:53591->192.168.102.105:53: i/o timeout
2025-09-26T22:51:00+03:00 WARN [request_id: 887da04b] client/internal/dns/upstream.go:200: upstream 192.168.102.105:53 timed out for question domain=lb._dns-sd._udp.mydomaintest.ru. after 2s (timeout=2s) (routes through NetBird peer peer-t-vpn03.netbird.selfhosted:100.64.56.216 NO_RECENT_HANDSHAKE no_handshake via_relay) - error: with udp: read udp 100.64.143.59:52940->192.168.102.105:53: i/o timeout
2025-09-26T22:51:00+03:00 WARN [request_id: 187f1c12] client/internal/dns/upstream.go:200: upstream 192.168.102.105:53 timed out for question domain=lb._dns-sd._udp.mydomaintestrus.ru. after 2s (timeout=2s) (routes through NetBird peer peer-t-vpn03.netbird.selfhosted:100.64.56.216 NO_RECENT_HANDSHAKE no_handshake via_relay) - error: with udp: read udp 100.64.143.59:61287->192.168.102.105:53: i/o timeout
2025-09-26T22:51:00+03:00 WARN [request_id: 4569e1e7] client/internal/dns/upstream.go:200: upstream 192.168.102.105:53 timed out for question domain=lb._dns-sd._udp.mydomaintestrus.hrdoc.ru. after 2s (timeout=2s) (routes through NetBird peer peer-t-vpn03.netbird.selfhosted:100.64.56.216 NO_RECENT_HANDSHAKE no_handshake via_relay) - error: with udp: read udp 100.64.143.59:65473->192.168.102.105:53: i/o timeout
2025-09-26T22:51:00+03:00 INFO client/internal/dns/upstream.go:322: upstreams 192.168.102.105:53, 192.168.100.21:53, 192.168.100.146:53 are responsive again. Adding them back to system
2025-09-26T22:51:00+03:00 INFO client/internal/dns/upstream.go:322: upstreams 192.168.102.105:53, 192.168.100.21:53, 192.168.100.146:53 are responsive again. Adding them back to system
2025-09-26T22:51:00+03:00 INFO client/internal/dns/host_darwin.go:278: added 1 match domains to the state. Domain list: 64.100.in-addr.arpa
2025-09-26T22:51:00+03:00 WARN [request_id: c41e253d] client/internal/dns/upstream.go:200: upstream 192.168.102.105:53 timed out for question domain=lb._dns-sd._udp.mydomaintestrus.ru. after 2.001s (timeout=2s) (routes through NetBird peer peer-t-vpn03.netbird.selfhosted:100.64.56.216 NO_RECENT_HANDSHAKE no_handshake via_relay) - error: with udp: read udp 100.64.143.59:52421->192.168.102.105:53: i/o timeout
2025-09-26T22:51:00+03:00 WARN [request_id: f62085bd] client/internal/dns/upstream.go:200: upstream 192.168.102.105:53 timed out for question domain=lb._dns-sd._udp.mydomaintest.ru. after 2.001s (timeout=2s) (routes through NetBird peer peer-t-vpn03.netbird.selfhosted:100.64.56.216 NO_RECENT_HANDSHAKE no_handshake via_relay) - error: with udp: read udp 100.64.143.59:55006->192.168.102.105:53: i/o timeout
2025-09-26T22:51:00+03:00 WARN [request_id: 09ec9fd9] client/internal/dns/upstream.go:200: upstream 192.168.102.105:53 timed out for question domain=lb._dns-sd._udp.mydomaintestrus.hrdoc.ru. after 2.001s (timeout=2s) (routes through NetBird peer peer-t-vpn03.netbird.selfhosted:100.64.56.216 NO_RECENT_HANDSHAKE no_handshake via_relay) - error: with udp: read udp 100.64.143.59:52469->192.168.102.105:53: i/o timeout
2025-09-26T22:51:00+03:00 INFO client/internal/dns/host_darwin.go:265: added 5 search domains to the state. Domain list: bk.local mydomaintestrus.ru mydomaintest.ru mydomaintestrus.hrdoc.ru netbird.selfhosted
2025-09-26T22:51:00+03:00 INFO client/internal/dns/upstream.go:322: upstreams 192.168.102.105:53, 192.168.100.21:53, 192.168.100.146:53 are responsive again. Adding them back to system
2025-09-26T22:51:00+03:00 INFO client/internal/dns/host_darwin.go:344: flushed DNS cache
2025-09-26T22:51:00+03:00 INFO client/internal/dns/host_darwin.go:278: added 1 match domains to the state. Domain list: 64.100.in-addr.arpa
2025-09-26T22:51:00+03:00 INFO client/internal/dns/host_darwin.go:265: added 5 search domains to the state. Domain list: bk.local mydomaintestrus.ru mydomaintest.ru mydomaintestrus.hrdoc.ru netbird.selfhosted
2025-09-26T22:51:00+03:00 WARN [request_id: 6f2af708] client/internal/dns/upstream.go:200: upstream 192.168.102.105:53 timed out for question domain=lb._dns-sd._udp.mydomaintestrus.ru. after 2s (timeout=2s) (routes through NetBird peer peer-t-vpn03.netbird.selfhosted:100.64.56.216 NO_RECENT_HANDSHAKE no_handshake via_relay) - error: with udp: read udp 100.64.143.59:62990->192.168.102.105:53: i/o timeout
2025-09-26T22:51:00+03:00 WARN [request_id: e780999c] client/internal/dns/upstream.go:200: upstream 192.168.102.105:53 timed out for question domain=lb._dns-sd._udp.mydomaintest.ru. after 2s (timeout=2s) (routes through NetBird peer peer-t-vpn03.netbird.selfhosted:100.64.56.216 NO_RECENT_HANDSHAKE no_handshake via_relay) - error: with udp: read udp 100.64.143.59:58051->192.168.102.105:53: i/o timeout
2025-09-26T22:51:00+03:00 WARN [request_id: 8c7446eb] client/internal/dns/upstream.go:200: upstream 192.168.102.105:53 timed out for question domain=lb._dns-sd._udp.mydomaintestrus.hrdoc.ru. after 2s (timeout=2s) (routes through NetBird peer peer-t-vpn03.netbird.selfhosted:100.64.56.216 NO_RECENT_HANDSHAKE no_handshake via_relay) - error: with udp: read udp 100.64.143.59:55000->192.168.102.105:53: i/o timeout
2025-09-26T22:51:00+03:00 WARN [request_id: 0ac5142c] client/internal/dns/upstream.go:200: upstream 192.168.102.105:53 timed out for question domain=bird-t.mydomaintestrus.ru. after 2s (timeout=2s) (routes through NetBird peer peer-t-vpn03.netbird.selfhosted:100.64.56.216 NO_RECENT_HANDSHAKE no_handshake via_relay) - error: with udp: read udp 100.64.143.59:57519->192.168.102.105:53: i/o timeout
2025-09-26T22:51:00+03:00 INFO client/internal/dns/host_darwin.go:344: flushed DNS cache
2025-09-26T22:51:00+03:00 INFO client/internal/dns/upstream.go:322: upstreams 192.168.102.105:53, 192.168.100.21:53, 192.168.100.146:53 are responsive again. Adding them back to system
2025-09-26T22:51:00+03:00 INFO client/internal/dns/host_darwin.go:278: added 1 match domains to the state. Domain list: 64.100.in-addr.arpa
2025-09-26T22:51:00+03:00 INFO client/internal/dns/host_darwin.go:265: added 5 search domains to the state. Domain list: bk.local mydomaintestrus.ru mydomaintest.ru mydomaintestrus.hrdoc.ru netbird.selfhosted
2025-09-26T22:51:00+03:00 INFO client/internal/dns/host_darwin.go:344: flushed DNS cache
2025-09-26T22:51:00+03:00 INFO client/internal/dns/host_darwin.go:278: added 1 match domains to the state. Domain list: 64.100.in-addr.arpa
2025-09-26T22:51:00+03:00 INFO client/internal/dns/host_darwin.go:265: added 5 search domains to the state. Domain list: bk.local mydomaintestrus.ru mydomaintest.ru mydomaintestrus.hrdoc.ru netbird.selfhosted
2025-09-26T22:51:00+03:00 INFO client/internal/dns/host_darwin.go:344: flushed DNS cache

@Lirok228 commented on GitHub (Sep 26, 2025): I can confirm I’m experiencing the same issue. The DNS servers do become reachable after a short period of time, but the client still shows the “DNS unreachable” warning. Is there a way to either increase the TTL/grace period before triggering this warning, or are there any other recommended workarounds to mitigate the problem? 2025-09-26T22:50:59+03:00 WARN [request_id: d26cfaff] client/internal/dns/upstream.go:200: upstream 192.168.102.105:53 timed out for question domain=lb._dns-sd._udp.mydomaintest.ru. after 2s (timeout=2s) (routes through NetBird peer peer-t-vpn03.netbird.selfhosted:100.64.56.216 NO_RECENT_HANDSHAKE no_handshake via_relay) - error: with udp: read udp 192.168.0.25:60741->192.168.102.105:53: i/o timeout 2025-09-26T22:50:59+03:00 WARN [request_id: 33482a54] client/internal/dns/upstream.go:200: upstream 192.168.102.105:53 timed out for question domain=lb._dns-sd._udp.mydomaintestrus.ru. after 2s (timeout=2s) (routes through NetBird peer peer-t-vpn03.netbird.selfhosted:100.64.56.216 NO_RECENT_HANDSHAKE no_handshake via_relay) - error: with udp: read udp 192.168.0.25:61674->192.168.102.105:53: i/o timeout 2025-09-26T22:50:59+03:00 WARN [request_id: 6de4cd11] client/internal/dns/upstream.go:200: upstream 192.168.102.105:53 timed out for question domain=lb._dns-sd._udp.mydomaintestrus.hrdoc.ru. after 2s (timeout=2s) (routes through NetBird peer peer-t-vpn03.netbird.selfhosted:100.64.56.216 NO_RECENT_HANDSHAKE no_handshake via_relay) - error: with udp: read udp 192.168.0.25:55347->192.168.102.105:53: i/o timeout 2025-09-26T22:50:59+03:00 WARN [request_id: 401f2cd9] client/internal/dns/upstream.go:200: upstream 192.168.102.105:53 timed out for question domain=lb._dns-sd._udp.mydomaintest.ru. after 2s (timeout=2s) (routes through NetBird peer peer-t-vpn03.netbird.selfhosted:100.64.56.216 NO_RECENT_HANDSHAKE no_handshake via_relay) - error: with udp: read udp 192.168.0.25:62773->192.168.102.105:53: i/o timeout 2025-09-26T22:50:59+03:00 WARN [request_id: e2971d9b] client/internal/dns/upstream.go:200: upstream 192.168.102.105:53 timed out for question domain=lb._dns-sd._udp.mydomaintestrus.ru. after 2s (timeout=2s) (routes through NetBird peer peer-t-vpn03.netbird.selfhosted:100.64.56.216 NO_RECENT_HANDSHAKE no_handshake via_relay) - error: with udp: read udp 192.168.0.25:54385->192.168.102.105:53: i/o timeout 2025-09-26T22:50:59+03:00 WARN [request_id: e693d6d2] client/internal/dns/upstream.go:200: upstream 192.168.102.105:53 timed out for question domain=lb._dns-sd._udp.mydomaintestrus.hrdoc.ru. after 2s (timeout=2s) (routes through NetBird peer peer-t-vpn03.netbird.selfhosted:100.64.56.216 NO_RECENT_HANDSHAKE no_handshake via_relay) - error: with udp: read udp 192.168.0.25:55441->192.168.102.105:53: i/o timeout 2025-09-26T22:50:59+03:00 WARN [request_id: f91897af] client/internal/dns/upstream.go:200: upstream 192.168.102.105:53 timed out for question domain=lb._dns-sd._udp.mydomaintestrus.ru. after 2s (timeout=2s) (routes through NetBird peer peer-t-vpn03.netbird.selfhosted:100.64.56.216 NO_RECENT_HANDSHAKE no_handshake via_relay) - error: with udp: read udp 100.64.143.59:54984->192.168.102.105:53: i/o timeout 2025-09-26T22:50:59+03:00 WARN [request_id: b6b4cdca] client/internal/dns/upstream.go:200: upstream 192.168.102.105:53 timed out for question domain=lb._dns-sd._udp.mydomaintestrus.hrdoc.ru. after 2s (timeout=2s) (routes through NetBird peer peer-t-vpn03.netbird.selfhosted:100.64.56.216 NO_RECENT_HANDSHAKE no_handshake via_relay) - error: with udp: read udp 100.64.143.59:52787->192.168.102.105:53: i/o timeout 2025-09-26T22:50:59+03:00 WARN [request_id: a1c55e29] client/internal/dns/upstream.go:200: upstream 192.168.102.105:53 timed out for question domain=lb._dns-sd._udp.mydomaintest.ru. after 2s (timeout=2s) (routes through NetBird peer peer-t-vpn03.netbird.selfhosted:100.64.56.216 NO_RECENT_HANDSHAKE no_handshake via_relay) - error: with udp: read udp 100.64.143.59:53591->192.168.102.105:53: i/o timeout 2025-09-26T22:51:00+03:00 WARN [request_id: 887da04b] client/internal/dns/upstream.go:200: upstream 192.168.102.105:53 timed out for question domain=lb._dns-sd._udp.mydomaintest.ru. after 2s (timeout=2s) (routes through NetBird peer peer-t-vpn03.netbird.selfhosted:100.64.56.216 NO_RECENT_HANDSHAKE no_handshake via_relay) - error: with udp: read udp 100.64.143.59:52940->192.168.102.105:53: i/o timeout 2025-09-26T22:51:00+03:00 WARN [request_id: 187f1c12] client/internal/dns/upstream.go:200: upstream 192.168.102.105:53 timed out for question domain=lb._dns-sd._udp.mydomaintestrus.ru. after 2s (timeout=2s) (routes through NetBird peer peer-t-vpn03.netbird.selfhosted:100.64.56.216 NO_RECENT_HANDSHAKE no_handshake via_relay) - error: with udp: read udp 100.64.143.59:61287->192.168.102.105:53: i/o timeout 2025-09-26T22:51:00+03:00 WARN [request_id: 4569e1e7] client/internal/dns/upstream.go:200: upstream 192.168.102.105:53 timed out for question domain=lb._dns-sd._udp.mydomaintestrus.hrdoc.ru. after 2s (timeout=2s) (routes through NetBird peer peer-t-vpn03.netbird.selfhosted:100.64.56.216 NO_RECENT_HANDSHAKE no_handshake via_relay) - error: with udp: read udp 100.64.143.59:65473->192.168.102.105:53: i/o timeout 2025-09-26T22:51:00+03:00 INFO client/internal/dns/upstream.go:322: upstreams 192.168.102.105:53, 192.168.100.21:53, 192.168.100.146:53 are responsive again. Adding them back to system 2025-09-26T22:51:00+03:00 INFO client/internal/dns/upstream.go:322: upstreams 192.168.102.105:53, 192.168.100.21:53, 192.168.100.146:53 are responsive again. Adding them back to system 2025-09-26T22:51:00+03:00 INFO client/internal/dns/host_darwin.go:278: added 1 match domains to the state. Domain list: 64.100.in-addr.arpa 2025-09-26T22:51:00+03:00 WARN [request_id: c41e253d] client/internal/dns/upstream.go:200: upstream 192.168.102.105:53 timed out for question domain=lb._dns-sd._udp.mydomaintestrus.ru. after 2.001s (timeout=2s) (routes through NetBird peer peer-t-vpn03.netbird.selfhosted:100.64.56.216 NO_RECENT_HANDSHAKE no_handshake via_relay) - error: with udp: read udp 100.64.143.59:52421->192.168.102.105:53: i/o timeout 2025-09-26T22:51:00+03:00 WARN [request_id: f62085bd] client/internal/dns/upstream.go:200: upstream 192.168.102.105:53 timed out for question domain=lb._dns-sd._udp.mydomaintest.ru. after 2.001s (timeout=2s) (routes through NetBird peer peer-t-vpn03.netbird.selfhosted:100.64.56.216 NO_RECENT_HANDSHAKE no_handshake via_relay) - error: with udp: read udp 100.64.143.59:55006->192.168.102.105:53: i/o timeout 2025-09-26T22:51:00+03:00 WARN [request_id: 09ec9fd9] client/internal/dns/upstream.go:200: upstream 192.168.102.105:53 timed out for question domain=lb._dns-sd._udp.mydomaintestrus.hrdoc.ru. after 2.001s (timeout=2s) (routes through NetBird peer peer-t-vpn03.netbird.selfhosted:100.64.56.216 NO_RECENT_HANDSHAKE no_handshake via_relay) - error: with udp: read udp 100.64.143.59:52469->192.168.102.105:53: i/o timeout 2025-09-26T22:51:00+03:00 INFO client/internal/dns/host_darwin.go:265: added 5 search domains to the state. Domain list: bk.local mydomaintestrus.ru mydomaintest.ru mydomaintestrus.hrdoc.ru netbird.selfhosted 2025-09-26T22:51:00+03:00 INFO client/internal/dns/upstream.go:322: upstreams 192.168.102.105:53, 192.168.100.21:53, 192.168.100.146:53 are responsive again. Adding them back to system 2025-09-26T22:51:00+03:00 INFO client/internal/dns/host_darwin.go:344: flushed DNS cache 2025-09-26T22:51:00+03:00 INFO client/internal/dns/host_darwin.go:278: added 1 match domains to the state. Domain list: 64.100.in-addr.arpa 2025-09-26T22:51:00+03:00 INFO client/internal/dns/host_darwin.go:265: added 5 search domains to the state. Domain list: bk.local mydomaintestrus.ru mydomaintest.ru mydomaintestrus.hrdoc.ru netbird.selfhosted 2025-09-26T22:51:00+03:00 WARN [request_id: 6f2af708] client/internal/dns/upstream.go:200: upstream 192.168.102.105:53 timed out for question domain=lb._dns-sd._udp.mydomaintestrus.ru. after 2s (timeout=2s) (routes through NetBird peer peer-t-vpn03.netbird.selfhosted:100.64.56.216 NO_RECENT_HANDSHAKE no_handshake via_relay) - error: with udp: read udp 100.64.143.59:62990->192.168.102.105:53: i/o timeout 2025-09-26T22:51:00+03:00 WARN [request_id: e780999c] client/internal/dns/upstream.go:200: upstream 192.168.102.105:53 timed out for question domain=lb._dns-sd._udp.mydomaintest.ru. after 2s (timeout=2s) (routes through NetBird peer peer-t-vpn03.netbird.selfhosted:100.64.56.216 NO_RECENT_HANDSHAKE no_handshake via_relay) - error: with udp: read udp 100.64.143.59:58051->192.168.102.105:53: i/o timeout 2025-09-26T22:51:00+03:00 WARN [request_id: 8c7446eb] client/internal/dns/upstream.go:200: upstream 192.168.102.105:53 timed out for question domain=lb._dns-sd._udp.mydomaintestrus.hrdoc.ru. after 2s (timeout=2s) (routes through NetBird peer peer-t-vpn03.netbird.selfhosted:100.64.56.216 NO_RECENT_HANDSHAKE no_handshake via_relay) - error: with udp: read udp 100.64.143.59:55000->192.168.102.105:53: i/o timeout 2025-09-26T22:51:00+03:00 WARN [request_id: 0ac5142c] client/internal/dns/upstream.go:200: upstream 192.168.102.105:53 timed out for question domain=bird-t.mydomaintestrus.ru. after 2s (timeout=2s) (routes through NetBird peer peer-t-vpn03.netbird.selfhosted:100.64.56.216 NO_RECENT_HANDSHAKE no_handshake via_relay) - error: with udp: read udp 100.64.143.59:57519->192.168.102.105:53: i/o timeout 2025-09-26T22:51:00+03:00 INFO client/internal/dns/host_darwin.go:344: flushed DNS cache 2025-09-26T22:51:00+03:00 INFO client/internal/dns/upstream.go:322: upstreams 192.168.102.105:53, 192.168.100.21:53, 192.168.100.146:53 are responsive again. Adding them back to system 2025-09-26T22:51:00+03:00 INFO client/internal/dns/host_darwin.go:278: added 1 match domains to the state. Domain list: 64.100.in-addr.arpa 2025-09-26T22:51:00+03:00 INFO client/internal/dns/host_darwin.go:265: added 5 search domains to the state. Domain list: bk.local mydomaintestrus.ru mydomaintest.ru mydomaintestrus.hrdoc.ru netbird.selfhosted 2025-09-26T22:51:00+03:00 INFO client/internal/dns/host_darwin.go:344: flushed DNS cache 2025-09-26T22:51:00+03:00 INFO client/internal/dns/host_darwin.go:278: added 1 match domains to the state. Domain list: 64.100.in-addr.arpa 2025-09-26T22:51:00+03:00 INFO client/internal/dns/host_darwin.go:265: added 5 search domains to the state. Domain list: bk.local mydomaintestrus.ru mydomaintest.ru mydomaintestrus.hrdoc.ru netbird.selfhosted 2025-09-26T22:51:00+03:00 INFO client/internal/dns/host_darwin.go:344: flushed DNS cache
saavagebueno commented 2025-11-20 07:07:31 -05:00
Author
Owner
Copy Link

@asdevcapybara commented on GitHub (Oct 23, 2025):

we have the same issue. the DNS server is running on one of the peers, and it looks like there’s a brief interruption when connecting. increasing the timeout would help to wait out the connection initialization period.

@asdevcapybara commented on GitHub (Oct 23, 2025): we have the same issue. the DNS server is running on one of the peers, and it looks like there’s a brief interruption when connecting. increasing the timeout would help to wait out the connection initialization period.
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 triage-needed
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#2306
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?