[GH-ISSUE #3619] [client] Custom DNS cannot resolve CNAME records. #7234

Open
opened 2026-08-05 01:12:07 -04:00 by saavagebueno · 0 comments
Owner

Originally created by @Cikaros on GitHub (Apr 4, 2025).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/3619

Originally assigned to: @nazarewk on GitHub.

I encountered issues while attempting to configure a CNAME record for custom DNS, as the netbird client does not support CNAME resolution on Windows and Linux. However, it is quite strange that using PowerShell's Resolve-DnsName can query the correct CNAME record, while nslookup.exe and browsers are unable to resolve it properly.

Originally created by @Cikaros on GitHub (Apr 4, 2025). Original GitHub issue: https://github.com/netbirdio/netbird/issues/3619 Originally assigned to: @nazarewk on GitHub. I encountered issues while attempting to configure a CNAME record for custom DNS, as the netbird client does not support CNAME resolution on Windows and Linux. However, it is quite strange that using PowerShell's `Resolve-DnsName` can query the correct CNAME record, while `nslookup.exe` and browsers are unable to resolve it properly.
saavagebueno added the bugdns labels 2026-08-05 01:12:08 -04:00
Sign in to join this conversation.
No Label bug dns
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#7234