A few weeks ago I setup a cloud install to test Netbird features. I am usually working remotely on a Windows 10 notebook, and I get connected to a LAN with a Synology NAS acting as routing peer, as well as a couple of PCs running the agent as peers.
Since a few days ago (may be windows update related or Netbird related) I can no longer ping LAN machines using names rather than IP addresses.
This was fully functional, now it is broken. I have a couple of scripts I run on each Synology startup. However it looks like DNS resolution within Netbird is not running, even though I have set up DNS server being a LAN router with its specific IP address.
Is there any sequence of commands that I could run in order to find out why Netbird has ping reply when using IP addresses but none when using computer names?
Router acting as DNS server is 192.168.3.100
Events as follows:
Events:
[WARNING] DNS (31bd3926-3eed-)
Message: The host dns manager does not support match domains
Time: 1 hour, 23 minutes ago
Metadata: manager: file
[WARNING] DNS (32d03434-1f76-4630-)
Message: The host dns manager does not support match domains
Time: 1 hour, 23 minutes ago
Metadata: manager: file
[WARNING] DNS (cb606ab3-fb12-4cf0-)
Message: All upstream servers failed (probe failed)
Time: 1 hour, 23 minutes ago
Metadata: upstreams: 192.168.3.100:53
[INFO] SYSTEM (1fbf75be-594e-4bcb-)
Message: Network map updated
Time: 1 hour, 23 minutes ago
OS: linux/amd64
Daemon version: 0.51.2
CLI version: 0.51.2
Management: Connected to
Signal: Connected to
Relays:
[stun:stun.netbird.io:443] is Available
[stun:stun.netbird.io:5555] is Available
[turns:turn.netbird.io:443?transport=tcp] is Available
[rels://streamline-sa-east-1a.relay.netbird.io:443] is Available
Nameservers:
[192.168.3.100:53] for [anon-bIFKg.domain] is Unavailable, reason: 1 error occurred:
* with udp: read udp 192.168.3.199:49678->192.168.3.100:53: read: connection refused