[GH-ISSUE #2021] Nameserver cannot be scoped to TLD #4039

Open
opened 2026-08-05 00:55:36 -04:00 by saavagebueno · 0 comments
Owner

Originally created by @ednxzu on GitHub (May 20, 2024).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/2021

Describe the problem

Netbird currently does not allow you to pass a top level domain to resolve.

Example: one cannot have a match domain scoped to consul., that would allow to resolve anything under *.consul

I believe this is only a GUI issue in the dashboard, and the feature should (???) work, it just cannot be set because of some UI input filter.

To Reproduce

Steps to reproduce the behavior:

  1. Go to DNS settings
  2. Try adding a domain match that is a TLD (com, fr, eu, etc..)

Expected behavior

match domain should support TLD scope

Are you using NetBird Cloud?

No

NetBird version

0.27.3

Originally created by @ednxzu on GitHub (May 20, 2024). Original GitHub issue: https://github.com/netbirdio/netbird/issues/2021 **Describe the problem** Netbird currently does not allow you to pass a top level domain to resolve. Example: one cannot have a match domain scoped to `consul.`, that would allow to resolve anything under *.consul I believe this is only a GUI issue in the dashboard, and the feature should (???) work, it just cannot be set because of some UI input filter. **To Reproduce** Steps to reproduce the behavior: 1. Go to DNS settings 2. Try adding a domain match that is a TLD (com, fr, eu, etc..) **Expected behavior** match domain should support TLD scope **Are you using NetBird Cloud?** No **NetBird version** 0.27.3
saavagebueno added the feature-requestdns labels 2026-08-05 00:55:36 -04:00
Sign in to join this conversation.
No Label dns feature-request
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#4039