starred/headscale
1
0
Fork 0
mirror of https://github.com/juanfont/headscale.git synced 2026-01-12 04:10:32 +01:00
Code Issues 98 Packages Projects Releases 10 Wiki Activity

Should "namespace" or "user" be a part of the MagicDNS? #137

New Issue
Closed
opened 2025-12-29 01:23:49 +01:00 by adam · 5 comments
adam commented 2025-12-29 01:23:49 +01:00
Owner
Copy Link

Originally created by @kradalby on GitHub (Feb 25, 2022).

Originally created by @kradalby on GitHub (Feb 25, 2022).
adam added the enhancementquestion labels 2025-12-29 01:23:49 +01:00
adam closed this issue 2025-12-29 01:23:49 +01:00
adam commented 2025-12-29 01:23:49 +01:00
Author
Owner
Copy Link

@restanrm commented on GitHub (Feb 25, 2022):

My first thought on this subject would be “no”. In personal usage, the number of hosts should stay relatively small. When a machine is tagged, the first owner shouldn't have any meaning to the host to not bring confusion.

@restanrm commented on GitHub (Feb 25, 2022): My first thought on this subject would be “no”. In personal usage, the number of hosts should stay relatively small. When a machine is tagged, the first owner shouldn't have any meaning to the host to not bring confusion.
adam commented 2025-12-29 01:23:50 +01:00
Author
Owner
Copy Link

@nosklo commented on GitHub (Feb 25, 2022):

The idea is that the user can add more hosts, so I would like that option, otherwise I believe we will need to figure out some way to deal with hostname conflicts between users/namespaces

we could round-robin the hosts

hmm maybe the tag could be published to the dns, and accessing it round-robins the hosts under that tag

@nosklo commented on GitHub (Feb 25, 2022): The idea is that the user can add more hosts, so I would like that option, otherwise I believe we will need to figure out some way to deal with hostname conflicts between users/namespaces we could round-robin the hosts hmm maybe the tag could be published to the dns, and accessing it round-robins the hosts under that tag
adam commented 2025-12-29 01:23:50 +01:00
Author
Owner
Copy Link

@restanrm commented on GitHub (Feb 28, 2022):

On tailscale when there is a conflict on the hostname, the suffix _1 is automatically added

@restanrm commented on GitHub (Feb 28, 2022): On tailscale when there is a conflict on the hostname, the suffix `_1` is automatically added
adam commented 2025-12-29 01:23:51 +01:00
Author
Owner
Copy Link

@e-zk commented on GitHub (Mar 2, 2022):

I personally like the idea of keeping it so each namespace/user has it's own subdomain, like machine.user.example.com. Just my 2c.

@e-zk commented on GitHub (Mar 2, 2022): I personally like the idea of keeping it so each namespace/user has it's own subdomain, like `machine.user.example.com`. Just my 2c.
adam commented 2025-12-29 01:23:51 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (Jun 12, 2022):

Yep, we will keep it that way.

@kradalby commented on GitHub (Jun 12, 2022): Yep, we will keep it that way.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
CLI
DERP
DNS
Nix
OIDC
SSH
bug
database
documentation
duplicate
enhancement
faq
good first issue
grants
help wanted
might-come
needs design doc
needs investigation
no-stale-bot
out of scope
performance
policy 📝
pull-request
Mirrored from GitHub Pull Request
 question
regression
routes
stale
tags
tailscale-feature-gap
well described ❤️
wontfix
No Label enhancement question
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#137
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?