Allow DNS wildcards in config #523

Closed
opened 2025-12-29 02:19:31 +01:00 by adam · 6 comments
Owner

Originally created by @gymnae on GitHub (Jun 26, 2023).

Why

I have a bunch of domains and subdomains being served by a reverse proxy. I'd like to directly speak to this reverse proxy by using a wildcard DNS entry like:
"*.domain.tld"
"A"
"192.0.0.2"

Right now I need to add every DNS entry served by this reverse proxy by hand.

Description

Allow wildcards for DNS entries

Originally created by @gymnae on GitHub (Jun 26, 2023). <!-- 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 have a bunch of domains and subdomains being served by a reverse proxy. I'd like to directly speak to this reverse proxy by using a wildcard DNS entry like: "*.domain.tld" "A" "192.0.0.2" Right now I need to add every DNS entry served by this reverse proxy by hand. <!-- 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 Allow wildcards for DNS entries <!-- A clear and precise description of what new or changed feature you want. -->
adam added the enhancementstale labels 2025-12-29 02:19:31 +01:00
adam closed this issue 2025-12-29 02:19:31 +01:00
Author
Owner

@almereyda commented on GitHub (Sep 13, 2023):

This may also be relevant for #1356.

@almereyda commented on GitHub (Sep 13, 2023): This may also be relevant for #1356.
Author
Owner

@tctlrd commented on GitHub (Nov 20, 2023):

This would indeed be a huge time saver...

@tctlrd commented on GitHub (Nov 20, 2023): This would indeed be a huge time saver...
Author
Owner

@termermc commented on GitHub (Feb 11, 2024):

I would also like to see this. A workaround for now would be redirecting DNS to an internal CoreDNS server or similar to set up records manually, but that's not a great solution.

@termermc commented on GitHub (Feb 11, 2024): I would also like to see this. A workaround for now would be redirecting DNS to an internal CoreDNS server or similar to set up records manually, but that's not a great solution.
Author
Owner

@github-actions[bot] commented on GitHub (May 11, 2024):

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

@github-actions[bot] commented on GitHub (May 11, 2024): This issue is stale because it has been open for 90 days with no activity.
Author
Owner

@github-actions[bot] commented on GitHub (May 18, 2024):

This issue was closed because it has been inactive for 14 days since being marked as stale.

@github-actions[bot] commented on GitHub (May 18, 2024): This issue was closed because it has been inactive for 14 days since being marked as stale.
Author
Owner

@PatrickHuetter commented on GitHub (Jun 4, 2024):

This would be very nice!

@PatrickHuetter commented on GitHub (Jun 4, 2024): This would be very nice!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#523