0.47.2 Match Domain Issue

[roberthase]

After updating a client with windows 11 to 0.47.2 the first match domain configured in the netbird controller is not routed trough the tunnel. All other domains work fine. The domain shows up fine when checking netbird status --detail and is correctly stored in the registry.

Disconnecting, reconnecting and rebooting do not fix this issue.

After downgrading to 0.47.1. everything is back to normal.

Controller and routing peers are on 0.43.0.

This is reproducable and happens each time after updating to 0.47.2 on multiple devices.

[nazarewk]

Could you upload a debug bundle while demonstrating the issue and send us the upload key + output of the commands you're using to verify?

Some of the commands that could help us with debugging this:

ipconfig /all
Get-DnsClientGlobalSetting
Get-DnsClientNrptGlobal
Get-DnsClientNrptRule
Get-DnsClientNrptPolicy
Get-ChildItem -Path "HKLM:\SYSTEM\CurrentControlSet\Services\Dnscache\Parameters\DnsPolicyConfig"
Get-ChildItem -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows NT\DNSClient\DnsPolicyConfig"

Feel free to email it to [email protected] if you're not feeling comfortable posting all that data here.

[nazarewk]

TLDR; we have determined that @roberthase has used the same domain (let's call it example.com) for both NetBird account's "DNS domain" and tried to supply a Nameserver handling the same example.com domain. This scenario is not allowed and will be filtered out on the client side.

@roberthase please let us know and close the issue if changing the DNS domain to something else resolves your issue.

[roberthase]

this has been resolved, thank you.

[nazarewk]

just noting this seems related to https://github.com/netbirdio/netbird/issues/3933