Issues with DNS matching to tunnel

[roberthase]

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

[nazarewk]

Hello @roberthase,

We're currently reviewing our open issues and would like to verify if this problem still exists in the latest NetBird version.

Could you please confirm if the issue is still there?

We may close this issue temporarily if we don't hear back from you within 2 weeks, but feel free to reopen it with updated information.

Thanks for your contribution to improving the project!

[roberthase]

this has been resolved with a workaround. otherwise instructions should be clear, that a match-domain cant be "domain.com" if the netbird-controller is available under "netbird.domain.com".