[GH-ISSUE #1543] Custom DNS over peer routing not working #2636

Closed
opened 2026-08-05 00:48:10 -04:00 by saavagebueno · 1 comment
Owner

Originally created by @Riza-Aslan on GitHub (Feb 8, 2024).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/1543

Describe the problem

Since v. 0.25.5 of the Netbird client, custom DNS over routing peers isn't working most of the time. I'm using a Windows DNS server internally. If I try to reach an internal server with its FQDN, the client tries to resolve the IP with other DNS-Servers. I've configured a custom-DNS in Netbird, a routing-peer (the server is reachable) and a access rule. It is working perfectly fine with v. 0.25.4
If I look into "ipconfig /all", it is showing just the netbird domain as searchdomain, but not my own searchdomains. Sometimes they show up after a while and it works for a while but stops working again and the searchdomains disappear.

To Reproduce

Steps to reproduce the behavior:

  1. Install Windows Client v. 0.25.5 or later
  2. Try to resolve a FQDN with a custom-DNS-Server behind a routing-peer

Expected behavior

The client should resolve FQDNs with my custom-DNS over peer-routing

Are you using NetBird Cloud?

No, selfhosted

NetBird version

0.25.5 and later do have this issue

NetBird status -d output:

Please ask if you need it. There are some information which I wouldn't like to share public

Screenshots

If applicable, add screenshots to help explain your problem.

Additional context
I've found this in the changelog of v. 0.25.5
Validate upstream reachability on first DNS configuration by @lixmal in https://github.com/netbirdio/netbird/pull/1489

Originally created by @Riza-Aslan on GitHub (Feb 8, 2024). Original GitHub issue: https://github.com/netbirdio/netbird/issues/1543 **Describe the problem** Since v. 0.25.5 of the Netbird client, custom DNS over routing peers isn't working most of the time. I'm using a Windows DNS server internally. If I try to reach an internal server with its FQDN, the client tries to resolve the IP with other DNS-Servers. I've configured a custom-DNS in Netbird, a routing-peer (the server is reachable) and a access rule. It is working perfectly fine with v. 0.25.4 If I look into "ipconfig /all", it is showing just the netbird domain as searchdomain, but not my own searchdomains. Sometimes they show up after a while and it works for a while but stops working again and the searchdomains disappear. **To Reproduce** Steps to reproduce the behavior: 1. Install Windows Client v. 0.25.5 or later 2. Try to resolve a FQDN with a custom-DNS-Server behind a routing-peer **Expected behavior** The client should resolve FQDNs with my custom-DNS over peer-routing **Are you using NetBird Cloud?** No, selfhosted **NetBird version** 0.25.5 and later do have this issue **NetBird status -d output:** Please ask if you need it. There are some information which I wouldn't like to share public **Screenshots** If applicable, add screenshots to help explain your problem. **Additional context** I've found this in the changelog of v. 0.25.5 Validate upstream reachability on first DNS configuration by @lixmal in https://github.com/netbirdio/netbird/pull/1489
saavagebueno added the triage label 2026-08-05 00:48:10 -04:00
Author
Owner

@Riza-Aslan commented on GitHub (Feb 21, 2024):

Just tried v. 0.25.9 and everything looks fine now.

<!-- gh-comment-id:1955926149 --> @Riza-Aslan commented on GitHub (Feb 21, 2024): Just tried v. 0.25.9 and everything looks fine now.
Sign in to join this conversation.
No Label triage
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#2636