0.47.2 Match Domain Issue #1971

Open
opened 2025-11-20 06:10:26 -05:00 by saavagebueno · 0 comments
Owner

Originally created by @roberthase on GitHub (Jun 18, 2025).

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.

Originally created by @roberthase on GitHub (Jun 18, 2025). 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.
saavagebueno added the config-issuedns labels 2025-11-20 06:10:26 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#1971