custom DNS not assigned to the interface wt0 after agent upgrade to V0.37.2 #1685

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

Originally created by @abdou84 on GitHub (Mar 8, 2025).

Agent V0.37.1 windows 10 DNS was working fine.
After agent upgrade to V0.37.2 the server stop assigning DNS server to wt0 interface.
Anyone face this issue.
Is this a bug, or just miss configuration
Note : netbird server selfhosted

Originally created by @abdou84 on GitHub (Mar 8, 2025). Agent V0.37.1 windows 10 DNS was working fine. After agent upgrade to V0.37.2 the server stop assigning DNS server to wt0 interface. Anyone face this issue. Is this a bug, or just miss configuration Note : netbird server selfhosted
saavagebueno added the windowstriage-neededdns labels 2025-11-20 06:04:43 -05:00
Author
Owner

@Cikaros commented on GitHub (Mar 13, 2025):

#3418 same issue

@Cikaros commented on GitHub (Mar 13, 2025): #3418 same issue
Author
Owner

@Maescool commented on GitHub (Mar 14, 2025):

This might be caused by this #3332

@Maescool commented on GitHub (Mar 14, 2025): This might be caused by this #3332
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#1685