Can't resolve .netbird.selfhosted suffix FQDNs with Cloudflare DNS set up #1920

Open
opened 2025-11-20 06:09:17 -05:00 by saavagebueno · 0 comments
Owner

Originally created by @HammyHavoc on GitHub (May 28, 2025).

Hi all,

Not really dug much into NetBird's DNS options until now, but we've always used it with Cloudflare's public DNS via the DNS feature on NetBird, which works great.

However, a problem that has plagued us ever since is that it seems to kill the ability to resolve the auto-assigned .netbird.selfhosted suffix FQDNs, forcing us to use IPs instead, which is obviously less than ideal.

Is there a way to set .netbird.selfhosted suffix FQDNs to resolve via NetBird's internal DNS and use Cloudflare for everything else?

Originally created by @HammyHavoc on GitHub (May 28, 2025). Hi all, Not really dug much into NetBird's DNS options until now, but we've always used it with Cloudflare's public DNS via the `DNS` feature on NetBird, which works great. However, a problem that has plagued us ever since is that it seems to kill the ability to resolve the auto-assigned `.netbird.selfhosted` suffix FQDNs, forcing us to use IPs instead, which is obviously less than ideal. Is there a way to set `.netbird.selfhosted` suffix FQDNs to resolve via NetBird's internal DNS and use Cloudflare for everything else?
saavagebueno added the triage-needed label 2025-11-20 06:09:17 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#1920