Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wildcard DNS-Records #1840

Open
Neon-44 opened this issue Mar 20, 2024 · 0 comments
Open

Wildcard DNS-Records #1840

Neon-44 opened this issue Mar 20, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@Neon-44
Copy link

Neon-44 commented 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

@Neon-44 Neon-44 added the enhancement New feature or request label Mar 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant