[GH-ISSUE #3180] DNS-resolved IP not displaying on client 0.35.2 #6774

Closed
opened 2026-08-05 01:10:03 -04:00 by saavagebueno · 3 comments
Owner

Originally created by @ginsul on GitHub (Jan 14, 2025).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/3180

Describe the problem

In Netbird 0.34.1, when adding a route to a specific domain, the resolved IP is displayed in the client's network routes. However, in version 0.35.2, the resolved IP is not shown, causing the route to fail.

To Reproduce
Steps to reproduce the behavior:

  1. Setup networks on Dashboard
  2. Adding resource specific Domain google.com
  3. Connect on client

Expected behavior
The resolved IP should be displayed in the client's network routes after adding a route to a specific domain, ensuring proper functionality.

Are you using NetBird Cloud?
Selfhosted

NetBird version
0.35.2
Windows Client

Screenshots
image
image

Originally created by @ginsul on GitHub (Jan 14, 2025). Original GitHub issue: https://github.com/netbirdio/netbird/issues/3180 **Describe the problem** In Netbird 0.34.1, when adding a route to a specific domain, the resolved IP is displayed in the client's network routes. However, in version 0.35.2, the resolved IP is not shown, causing the route to fail. **To Reproduce** Steps to reproduce the behavior: 1. Setup networks on Dashboard 2. Adding resource specific Domain google.com 3. Connect on client **Expected behavior** The resolved IP should be displayed in the client's network routes after adding a route to a specific domain, ensuring proper functionality. **Are you using NetBird Cloud?** Selfhosted **NetBird version** 0.35.2 Windows Client **Screenshots** ![image](https://github.com/user-attachments/assets/fac046c7-1c07-4bb8-afd9-abb1d3e90c7a) ![image](https://github.com/user-attachments/assets/7f7650a1-4eba-4bb1-a3d7-dc358b6e3bf0)
saavagebueno added the triage-needed label 2026-08-05 01:10:03 -04:00
Author
Owner

@lixmal commented on GitHub (Jan 15, 2025):

Hi @ginsul,

can you provide the netbird debug bundle please (instructions in the template)

<!-- gh-comment-id:2592074236 --> @lixmal commented on GitHub (Jan 15, 2025): Hi @ginsul, can you provide the netbird debug bundle please (instructions in the template)
Author
Owner

@StefVos commented on GitHub (Jan 18, 2025):

Hi, I had the same issue running on netbird on a raspberryPi with the 'wildcard DNS' option active. My problem was the avahi-daemon using port 5353. To disable i used
sudo systemctl disable avahi-daemon
Now netbird dns lookups work as expected.
Hope this helps.

<!-- gh-comment-id:2600408853 --> @StefVos commented on GitHub (Jan 18, 2025): Hi, I had the same issue running on netbird on a raspberryPi with the 'wildcard DNS' option active. My problem was the avahi-daemon using port 5353. To disable i used **sudo systemctl disable avahi-daemon** Now netbird dns lookups work as expected. Hope this helps.
Author
Owner

@ginsul commented on GitHub (Apr 11, 2025):

Thanks, seems like it's working again on the newer NetBird versions.

<!-- gh-comment-id:2795802129 --> @ginsul commented on GitHub (Apr 11, 2025): Thanks, seems like it's working again on the newer NetBird versions.
Sign in to join this conversation.
No Label triage-needed
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#6774