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

Wildcard DNS-Records #676

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

Originally created by @Neon-44 on GitHub (Mar 20, 2024).

Why

I use Headscale to securely selfhost my Applications. Currently i just route the Local IPs to my Server and force all my Tailscale Devices to use the Local DNS-Server. however, if i could define the Domains in the Headscale DNS-Config (Via a Wildcard in the best Case) i could stop advertising local routes and instead resolve those Domains to the Tailscale Domain.

I would prefer Wildcards, as i sometimes add / remove Services with unique subdomains and I'm a bit scared of a indent-mistake in the config when adding the new record bringing the Server down, locking me out.

Description

currently the DNS of Headscale (this one: https://github.com/juanfont/headscale/blob/main/docs/dns-records.md#Limitations) can only resolve specific Domains. I would like to be able to put a wildcard in there and all subdomains getting redirected off of that Wildcard

Originally created by @Neon-44 on GitHub (Mar 20, 2024). <!-- We typically have a clear roadmap for what we want to improve and reserve the right to close feature requests that does not fit in the roadmap, or fit with the scope of the project, or we actually want to implement ourselves. Headscale is a multinational community across the globe. Our language is English. All bug reports needs to be in English. --> ## Why I use Headscale to securely selfhost my Applications. Currently i just route the Local IPs to my Server and force all my Tailscale Devices to use the Local DNS-Server. however, if i could define the Domains in the Headscale DNS-Config (Via a Wildcard in the best Case) i could stop advertising local routes and instead resolve those Domains to the Tailscale Domain. I would prefer Wildcards, as i sometimes add / remove Services with unique subdomains and I'm a bit scared of a indent-mistake in the config when adding the new record bringing the Server down, locking me out. <!-- Include the reason, why you would need the feature. E.g. what problem does it solve? Or which workflow is currently frustrating and will be improved by this? --> ## Description currently the DNS of Headscale (this one: https://github.com/juanfont/headscale/blob/main/docs/dns-records.md#Limitations) can only resolve specific Domains. I would like to be able to put a wildcard in there and all subdomains getting redirected off of that Wildcard <!-- A clear and precise description of what new or changed feature you want. -->
adam added the enhancement label 2025-12-29 02:21:57 +01:00
adam closed this issue 2025-12-29 02:21:57 +01:00
adam commented 2025-12-29 02:21:58 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 19, 2024):

This issue is stale because it has been open for 90 days with no activity.

@github-actions[bot] commented on GitHub (Jun 19, 2024): This issue is stale because it has been open for 90 days with no activity.
adam commented 2025-12-29 02:21:58 +01:00
Author
Owner
Copy Link

@Neon-44 commented on GitHub (Jun 24, 2024):

hey, can I get a quick feedback instead of just a stale? even if it's a wontfix, just so we know what's up.

@Neon-44 commented on GitHub (Jun 24, 2024): hey, can I get a quick feedback instead of just a stale? even if it's a wontfix, just so we know what's up.
adam commented 2025-12-29 02:21:58 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Sep 23, 2024):

This issue is stale because it has been open for 90 days with no activity.

@github-actions[bot] commented on GitHub (Sep 23, 2024): This issue is stale because it has been open for 90 days with no activity.
adam commented 2025-12-29 02:21:58 +01:00
Author
Owner
Copy Link

@dennisoderwald commented on GitHub (Sep 23, 2024):

Ping :)

@dennisoderwald commented on GitHub (Sep 23, 2024): Ping :)
adam commented 2025-12-29 02:21:58 +01:00
Author
Owner
Copy Link

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

I think this is a duplicate of #2159, I've replied there that it needs investigation, but I think it is a client limitation we cant do anything about. If it does currently not work, it probably wont as we just pass the option straight too the client.

@kradalby commented on GitHub (Nov 22, 2024): I think this is a duplicate of #2159, I've replied there that it needs investigation, but I think it is a client limitation we cant do anything about. If it does currently not work, it probably wont as we just pass the option straight too the client.
adam commented 2025-12-29 02:21:58 +01:00
Author
Owner
Copy Link

@Neon-44 commented on GitHub (Nov 24, 2024):

wait, but this Issue is older?

Shouldn't you mark 2159 as a duplicate of 1840, the older one?

oh well, whatever, I'll check it out over there.

@Neon-44 commented on GitHub (Nov 24, 2024): wait, but this Issue is older? Shouldn't you mark 2159 as a duplicate of 1840, the older one? oh well, whatever, I'll check it out over there.
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#676
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?