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

[Feature] Plea: keep "use_username_in_magic_dns" even after tags are fixed #841

New Issue
Closed
opened 2025-12-29 02:24:43 +01:00 by adam · 6 comments
adam commented 2025-12-29 02:24:43 +01:00
Owner
Copy Link

Originally created by @noseshimself on GitHub (Oct 25, 2024).

Use case

We do have a sufficient number of identical host names that have been personalized based on user names as intermediate components in DNS names. This has become necessary after deciding that we will be giving up centralized offices AND a number of centralized IT services during the Covid lockdown phase. One of the tools enabling us to do so was being able to use unqualified host names and having magicDNS do the job. Now you're pulling the rug under our lazy asses away.

Description

Keep "use_username_in_magic_dns" if it is possible at all.

Contribution

  • I can write the design doc for this feature
  • I can contribute this feature

How can it be implemented?

Just don't delete what is necessary. The flag "use_username_in_magic_dns" can be used to turn it off as default setting and those who really need it can continue using it.

Originally created by @noseshimself on GitHub (Oct 25, 2024). ### Use case We do have a sufficient number of identical host names that have been personalized based on user names as intermediate components in DNS names. This has become necessary after deciding that we will be giving up centralized offices AND a number of centralized IT services during the Covid lockdown phase. One of the tools enabling us to do so was being able to use unqualified host names and having magicDNS do the job. Now you're pulling the rug under our lazy asses away. ### Description Keep "use_username_in_magic_dns" if it is possible at all. ### Contribution - [ ] I can write the design doc for this feature - [ ] I can contribute this feature ### How can it be implemented? Just don't delete what is necessary. The flag "use_username_in_magic_dns" can be used to turn it off as default setting and those who really need it can continue using it.
adam added the enhancement label 2025-12-29 02:24:43 +01:00
adam closed this issue 2025-12-29 02:24:44 +01:00
adam commented 2025-12-29 02:24:45 +01:00
Author
Owner
Copy Link

@celevra commented on GitHub (Nov 13, 2024):

we use them also to organize "group" of hosts.
it is a great feature! So please keep it

@celevra commented on GitHub (Nov 13, 2024): we use them also to organize "group" of hosts. it is a great feature! So please keep it
adam commented 2025-12-29 02:24:45 +01:00
Author
Owner
Copy Link

@juanfont commented on GitHub (Nov 15, 2024):

Sorry, this was my bad.

It was never ment to be added in the first place and it will not be added back, the goal of this project is to align with Tailscale.

@juanfont commented on GitHub (Nov 15, 2024): Sorry, this was my bad. It was never ment to be added in the first place and it will not be added back, the goal of this project is to align with Tailscale.
adam commented 2025-12-29 02:24:45 +01:00
Author
Owner
Copy Link

@celevra commented on GitHub (Nov 19, 2024):

this could be a optional feature
So in the default configuration you are fully compatible to tailscale
but for us it is a killer feature.
All our logic is based on it, so that we need a way to build it, if you really remove it (why remove a working feature?).
than we need a webhook for new devices and create custom dns entries...

@celevra commented on GitHub (Nov 19, 2024): this could be a optional feature So in the default configuration you are fully compatible to tailscale but for us it is a killer feature. All our logic is based on it, so that we need a way to build it, if you really remove it (why remove a working feature?). than we need a webhook for new devices and create custom dns entries...
adam commented 2025-12-29 02:24:45 +01:00
Author
Owner
Copy Link

@noseshimself commented on GitHub (Nov 20, 2024):

we need a webhook for new devices and create custom dns entries...

I don't think that will be sufficient unless you can override Magic DNS with another source based on that source's answer (if it is providing a CNAME or A/AAAA, fine but if there is a negative answer coming back it has to try Magic-ing. On receiving a CNAME it you need to add even more checks. It's a nightmare.

@noseshimself commented on GitHub (Nov 20, 2024): > we need a webhook for new devices and create custom dns entries... I don't think that will be sufficient unless you can override Magic DNS with another source based on that source's answer (if it is providing a CNAME or A/AAAA, fine but if there is a negative answer coming back it has to try Magic-ing. On receiving a CNAME it you need to add even more checks. It's a nightmare.
adam commented 2025-12-29 02:24:45 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (Nov 29, 2024):

I will add a way for you to programatically provide the DNS server with new entries, see https://github.com/juanfont/headscale/issues/2262.

We will not reintroduce the feature, it is not a fully working feature and it is not safe.

@kradalby commented on GitHub (Nov 29, 2024): I will add a way for you to programatically provide the DNS server with new entries, see https://github.com/juanfont/headscale/issues/2262. We will not reintroduce the feature, it is not a fully working feature and it is not safe.
adam commented 2025-12-29 02:24:46 +01:00
Author
Owner
Copy Link

@celevra commented on GitHub (Nov 29, 2024):

Awesome!
Thank you

@celevra commented on GitHub (Nov 29, 2024): Awesome! Thank you
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
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#841
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?