i have a selfhosted netbird server reachable from the public internet with domain-name "domain.own"
When netbird is connected i want to route the domain "domain.own" through the wireguard tunnel, as internal system must be reachable with the same name (split-dns).
Sometimes after booting a windows-device i cant connect to the the netbird-controller, because a registry entry seems to restrict acces to "domain.own" to the wireguard tunnel. Because the tunnel is down, i cant connect to "netbird.domain.own"
To fix this issue, only deleting the registry-key Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Dnscache\Parameters\DnsPolicyConfig\NetBird-Match helps.
This is happening everynow and then on windows-devices with windows 11
Are you using NetBird Cloud?
self-hosted
NetBird version
0.31.0 on servers, routings-peers and clients - but it already happend in earlier versions
Describe the problem
i have a selfhosted netbird server reachable from the public internet with domain-name "domain.own" When netbird is connected i want to route the domain "domain.own" through the wireguard tunnel, as internal system must be reachable with the same name (split-dns).
Sometimes after booting a windows-device i cant connect to the the netbird-controller, because a registry entry seems to restrict acces to "domain.own" to the wireguard tunnel. Because the tunnel is down, i cant connect to "netbird.domain.own"
To fix this issue, only deleting the registry-key Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Dnscache\Parameters\DnsPolicyConfig\NetBird-Match helps.
This is happening everynow and then on windows-devices with windows 11
Are you using NetBird Cloud?
self-hosted
NetBird version
0.31.0 on servers, routings-peers and clients - but it already happend in earlier versions