DNS Resolution Fails when HKLM\SOFTWARE\Policies\Microsoft\Windows NT\DNSClient Exists on Windows 11 #1632

Closed
opened 2025-11-20 06:03:49 -05:00 by saavagebueno · 12 comments
Owner

Originally created by @OGDeguy on GitHub (Feb 15, 2025).

Originally assigned to: @lixmal on GitHub.

Describe the problem

DNS Resolution Fails when HKLM\SOFTWARE\Policies\Microsoft\Windows NT\DNSClient Exists on Windows 11

To Reproduce

Steps to reproduce the behavior:

  1. Make sure HKLM\SOFTWARE\Policies\Microsoft\Windows NT\DNSClient exists. This will cause the Netburd-match registry key to be created under an alternative path.
  2. Attempt DNS resolution. (Does not work for me (on version 0.36.7)
  3. Deleting the HKLM\SOFTWARE\Policies\Microsoft\Windows NT\DNSClient key and restarting the netbird service resolve DNS resolution errors.

Expected behavior

I should be able to resolve .wan and other match domains configured in netbird.

Are you using NetBird Cloud?

I am using the self-hosted version.

NetBird version

0.36.7

Hopefully this helps others who encounter this issue and the wonderful folks who work on this project make improvements.

Originally created by @OGDeguy on GitHub (Feb 15, 2025). Originally assigned to: @lixmal on GitHub. **Describe the problem** DNS Resolution Fails when HKLM\SOFTWARE\Policies\Microsoft\Windows NT\DNSClient Exists on Windows 11 **To Reproduce** Steps to reproduce the behavior: 1. Make sure HKLM\SOFTWARE\Policies\Microsoft\Windows NT\DNSClient exists. This will cause the Netburd-match registry key to be created under an alternative path. 2. Attempt DNS resolution. (Does not work for me (on version 0.36.7) 3. Deleting the HKLM\SOFTWARE\Policies\Microsoft\Windows NT\DNSClient key and restarting the netbird service resolve DNS resolution errors. **Expected behavior** I should be able to resolve .wan and other match domains configured in netbird. **Are you using NetBird Cloud?** I am using the self-hosted version. **NetBird version** `0.36.7` Hopefully this helps others who encounter this issue and the wonderful folks who work on this project make improvements.
saavagebueno added the bugwindowsdns labels 2025-11-20 06:03:49 -05:00
Author
Owner

@OGDeguy commented on GitHub (Feb 15, 2025):

Okay I modified client/internal/dns/host_windows.go:27 to SOFTWARE\Policies\Microsoft\Windows NT\DNSClientttt just to confirm and then recompiled the client. I no longer have any DNS resolution issues on my custom compiled client. Will be distributing this internally for now as a temporary work around.

@OGDeguy commented on GitHub (Feb 15, 2025): Okay I modified `client/internal/dns/host_windows.go:27` to ``SOFTWARE\Policies\Microsoft\Windows NT\DNSClientttt`` just to confirm and then recompiled the client. I no longer have any DNS resolution issues on my custom compiled client. Will be distributing this internally for now as a temporary work around.
Author
Owner

@rihards-simanovics commented on GitHub (Feb 17, 2025):

I can confirm that 0.36.7 fails to resolve the nodes' DNS on Windows 11 ent. The temporary workaround without recompiling with a fix is to just use IP for the node. I use RDP with an FQDN to the node, so I noticed today on the way to work.

@rihards-simanovics commented on GitHub (Feb 17, 2025): I can confirm that `0.36.7` fails to resolve the nodes' DNS on Windows 11 ent. The temporary workaround without recompiling with a fix is to just use IP for the node. I use RDP with an FQDN to the node, so I noticed today on the way to work.
Author
Owner

@mlsmaycon commented on GitHub (Feb 17, 2025):

@lixmal can you check this one?

@mlsmaycon commented on GitHub (Feb 17, 2025): @lixmal can you check this one?
Author
Owner

@rihards-simanovics commented on GitHub (Feb 17, 2025):

I can't say for certain if this was the case, but on one of my Linux servers running Ubuntu 22.04.5 LTS, the DNS resolution was completely nuked; not even google.com or the server's hostname would resolve.

@rihards-simanovics commented on GitHub (Feb 17, 2025): I can't say for certain if this was the case, but on one of my Linux servers running Ubuntu 22.04.5 LTS, the DNS resolution was completely nuked; not even google.com or the server's hostname would resolve.
Author
Owner

@lixmal commented on GitHub (Feb 18, 2025):

Hey folks,

can you try this build https://github.com/netbirdio/netbird/actions/runs/13390166152 once it's done building?

@rihards-simanovics regarding Linux, what was your previous version running? v0.36.7 has only touched Windows

@lixmal commented on GitHub (Feb 18, 2025): Hey folks, can you try this build https://github.com/netbirdio/netbird/actions/runs/13390166152 once it's done building? @rihards-simanovics regarding Linux, what was your previous version running? `v0.36.7` has only touched Windows
Author
Owner

@rihards-simanovics commented on GitHub (Feb 18, 2025):

Hey folks,

can you try this build https://github.com/netbirdio/netbird/actions/runs/13390166152 once it's done building?

@rihards-simanovics regarding Linux, what was your previous version running? v0.36.7 has only touched Windows

The update happened on the 16th during the regular maintenance window. here is the exact log entries related to netbird

Image
and also these, it looks like I have downgraded the package back to 0.36.3 at some point:
Image

@rihards-simanovics commented on GitHub (Feb 18, 2025): > Hey folks, > > can you try this build https://github.com/netbirdio/netbird/actions/runs/13390166152 once it's done building? > > [@rihards-simanovics](https://github.com/rihards-simanovics) regarding Linux, what was your previous version running? `v0.36.7` has only touched Windows The update happened on the 16th during the regular maintenance window. here is the exact log entries related to netbird ![Image](https://github.com/user-attachments/assets/d44338aa-34bc-4308-b236-d61d7823c587) and also these, it looks like I have downgraded the package back to `0.36.3` at some point: ![Image](https://github.com/user-attachments/assets/91126b74-8a54-4660-b73e-b62605086c18)
Author
Owner

@OGDeguy commented on GitHub (Feb 19, 2025):

Hey folks,

can you try this build https://github.com/netbirdio/netbird/actions/runs/13390166152 once it's done building?

@rihards-simanovics regarding Linux, what was your previous version running? v0.36.7 has only touched Windows

Gave this a go on my system and it is working great. Thank you @lixmal

I'll keep this open on my end until you folks decide to close the issue.

@OGDeguy commented on GitHub (Feb 19, 2025): > Hey folks, > > can you try this build https://github.com/netbirdio/netbird/actions/runs/13390166152 once it's done building? > > [@rihards-simanovics](https://github.com/rihards-simanovics) regarding Linux, what was your previous version running? `v0.36.7` has only touched Windows Gave this a go on my system and it is working great. Thank you @lixmal I'll keep this open on my end until you folks decide to close the issue.
Author
Owner

@rihards-simanovics commented on GitHub (Feb 19, 2025):

Hey, @lixmal, I just had an email from my ISP. Apparently, they had an outage, which seems to have only affected the DNS resolution. You can disregard the earlier issue with Linux DNS.

@rihards-simanovics commented on GitHub (Feb 19, 2025): Hey, @lixmal, I just had an email from my ISP. Apparently, they had an outage, which seems to have only affected the DNS resolution. You can disregard the earlier issue with Linux DNS.
Author
Owner

@OGDeguy commented on GitHub (Feb 19, 2025):

@lixmal I still seem to be getting some DNS issues on the provided build. Not sure why yet - was working fine today until I needed to reconnect.

@OGDeguy commented on GitHub (Feb 19, 2025): @lixmal I still seem to be getting some DNS issues on the provided build. Not sure why yet - was working fine today until I needed to reconnect.
Author
Owner

@saule1508 commented on GitHub (Feb 23, 2025):

This issue impacts all our windows client, it happened in v0.36.7, resolution is not working. A workaround is to add a match all domain in the dns server configuration. But even when I downgrade to v0.36.6 it is still broken now :-(

The trick to rename HKLM\SOFTWARE\Policies\Microsoft\Windows NT\DNSClient to HKLM\SOFTWARE\Policies\Microsoft\Windows NT\DNSClienttt works

@saule1508 commented on GitHub (Feb 23, 2025): This issue impacts all our windows client, it happened in v0.36.7, resolution is not working. A workaround is to add a match all domain in the dns server configuration. But even when I downgrade to v0.36.6 it is still broken now :-( The trick to rename HKLM\SOFTWARE\Policies\Microsoft\Windows NT\DNSClient to HKLM\SOFTWARE\Policies\Microsoft\Windows NT\DNSClienttt works
Author
Owner

@saule1508 commented on GitHub (Feb 23, 2025):

but after reboot, changing again the key to its original name HKLM\SOFTWARE\Policies\Microsoft\Windows NT\DNSClient and with v0.36.7 it works.
when I search in the registry, the Netbird-Match is in two locations

  • HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\DNSClient\DnsPolicyConfig\NetBird-Match
  • HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Policies\Microsoft\Windows NT\DNSClient\DnsPolicyConfig\NetBird-Match

I did a few stop service/start service and it seems to work, will see with my colleagues oversea when they wake up

@saule1508 commented on GitHub (Feb 23, 2025): but after reboot, changing again the key to its original name HKLM\SOFTWARE\Policies\Microsoft\Windows NT\DNSClient and with v0.36.7 it works. when I search in the registry, the Netbird-Match is in two locations * HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\DNSClient\DnsPolicyConfig\NetBird-Match * HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Policies\Microsoft\Windows NT\DNSClient\DnsPolicyConfig\NetBird-Match I did a few stop service/start service and it seems to work, will see with my colleagues oversea when they wake up
Author
Owner

@saule1508 commented on GitHub (Feb 24, 2025):

it is not working for us, after reboot the key is changed back to the original value and DNS is broken

@saule1508 commented on GitHub (Feb 24, 2025): it is not working for us, after reboot the key is changed back to the original value and DNS is broken
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#1632