0.49.0 windows client kills the DNS resolving #2005

Open
opened 2025-11-20 06:11:04 -05:00 by saavagebueno · 2 comments
Owner

Originally created by @SasSam on GitHub (Jun 25, 2025).

Describe the problem

I have a self-hosted Netbird server.

After I updated the client from 0.48.0 to 0.49.0 on Windows, the DNS service went down. I could ping IP addresses, but the DNS resolution didn't work.

To Reproduce

Steps to reproduce the behavior:
Updated the client from 0.48.0 to 0.49.0. Try to ping any domain on the mesh VPN or any public network. Then try to ping IP addresses. Domain ping won't work, IP ping will work.

Expected behavior

Everything should work as expected.

Are you using NetBird Cloud?

self-host NetBird's control plane

Originally created by @SasSam on GitHub (Jun 25, 2025). **Describe the problem** I have a self-hosted Netbird server. After I updated the client from 0.48.0 to 0.49.0 on Windows, the DNS service went down. I could ping IP addresses, but the DNS resolution didn't work. **To Reproduce** Steps to reproduce the behavior: Updated the client from 0.48.0 to 0.49.0. Try to ping any domain on the mesh VPN or any public network. Then try to ping IP addresses. Domain ping won't work, IP ping will work. **Expected behavior** Everything should work as expected. **Are you using NetBird Cloud?** self-host NetBird's control plane
saavagebueno added the triage-needed label 2025-11-20 06:11:04 -05:00
Author
Owner

@MarS0K commented on GitHub (Jun 26, 2025):

I encountered the same issue after updating from 0.48.0 to 0.49.0.
I deleted the registry key HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Dnscache\Parameters\DnsPolicyConfig\NetBird-Match https://github.com/netbirdio/netbird/issues/2895#issuecomment-2483968386, and the issue disappeared after PC reboot.

@MarS0K commented on GitHub (Jun 26, 2025): I encountered the same issue after updating from 0.48.0 to 0.49.0. I deleted the registry key HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Dnscache\Parameters\DnsPolicyConfig\NetBird-Match [https://github.com/netbirdio/netbird/issues/2895#issuecomment-2483968386](https://github.com/netbirdio/netbird/issues/2895#issuecomment-2483968386), and the issue disappeared after PC reboot.
Author
Owner

@WGOS commented on GitHub (Jun 28, 2025):

I did have similar issue on Windows 11 24H2 PC with Netbird 0.48.0. Besides DNS resolution the DNS service itself was consuming up to 100% of the CPU. Though removing registry key was no help

@WGOS commented on GitHub (Jun 28, 2025): I did have similar issue on Windows 11 24H2 PC with Netbird 0.48.0. Besides DNS resolution the DNS service itself was consuming up to 100% of the CPU. Though removing registry key was no help
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#2005