search

juanfont / headscale

An open source, self-hosted implementation of the Tailscale control server
BSD 3-Clause "New" or "Revised" License
23.58k stars 1.3k forks source link

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

Closed noseshimself closed 1 week ago

noseshimself commented 4 weeks ago

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

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.

celevra commented 1 week ago

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

juanfont commented 1 week ago

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.

celevra commented 3 days ago

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...

noseshimself commented 2 days ago

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.