[GH-ISSUE #4165] Punctuation-separated hostnames for peers #8181

Open
opened 2026-08-05 01:16:39 -04:00 by saavagebueno · 1 comment
Owner

Originally created by @KunJakob on GitHub (Jul 17, 2025).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/4165

Is your feature request related to a problem? Please describe.
Being unable to, essentially, namespace or otherwise group peers by having multiple levels of sub domains is proving to be annoying for the rest of our stack that tries to group resources by zone in internal tools.

Describe the solution you'd like
A peer with punctuation in the name has the same punctuation reflected in its hostname. For instance the peer "unit1.site2" gets the address "unit1.site2.netbird.cloud" instead of "unit1-site2.netbird.cloud". I understand this introduces a question of what to do in the case of conflicts where it currently appends -N to the hostname. For my case this is not a concern, so any of "N.unit1.site2.netbird.cloud", "unit1-N.site2.netbird.cloud" or "unit1.site2-N.netbird.cloud" would be fine for me. I suspect the last one is the one with the most expected behaviour compared to how it is now, but I don't have much of an issue with any of these.

Describe alternatives you've considered
I've considered abandoning the automatic DNS names in favor of a private nameserver in the mesh. I do find the maintenance overhead of this fairly daunting for "just" getting some dot-separation in our FQDN's though. If this feature isn't feasible I'll likely pursue this or have to look into an alternative to Netbird.

Originally created by @KunJakob on GitHub (Jul 17, 2025). Original GitHub issue: https://github.com/netbirdio/netbird/issues/4165 **Is your feature request related to a problem? Please describe.** Being unable to, essentially, namespace or otherwise group peers by having multiple levels of sub domains is proving to be annoying for the rest of our stack that tries to group resources by zone in internal tools. **Describe the solution you'd like** A peer with punctuation in the name has the same punctuation reflected in its hostname. For instance the peer "unit1.site2" gets the address "unit1.site2.netbird.cloud" instead of "unit1-site2.netbird.cloud". I understand this introduces a question of what to do in the case of conflicts where it currently appends -N to the hostname. For my case this is not a concern, so any of "N.unit1.site2.netbird.cloud", "unit1-N.site2.netbird.cloud" or "unit1.site2-N.netbird.cloud" would be fine for me. I suspect the last one is the one with the most expected behaviour compared to how it is now, but I don't have much of an issue with any of these. **Describe alternatives you've considered** I've considered abandoning the automatic DNS names in favor of a private nameserver in the mesh. I do find the maintenance overhead of this fairly daunting for "just" getting some dot-separation in our FQDN's though. If this feature isn't feasible I'll likely pursue this or have to look into an alternative to Netbird.
saavagebueno added the feature-request label 2026-08-05 01:16:40 -04:00
Author
Owner

@KunJakob commented on GitHub (Jul 17, 2025):

Probably very related to #2660 which would also solve this :)

<!-- gh-comment-id:3083313466 --> @KunJakob commented on GitHub (Jul 17, 2025): Probably very related to #2660 which would also solve this :)
Sign in to join this conversation.
No Label feature-request
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#8181