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] wildcard dns name rule #806

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

Originally created by @warlordattack on GitHub (Sep 29, 2024).

Use case

I like to have nice local dns names,
-in the LAN i use AdGuard to rewrite all local DNS names to traefik with one rule using wildcard : see picture
-in headscale there is " dns: > extra_records: " section for this, but unfortunatly you must add all your local dns names one by one : see picture

Description

image

Would be very nice to have record like this (to replace all the individual lines) :
image

The comented line would replace everything below :
image

image

Best regards :)

Contribution

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

How can it be implemented?

No response

Originally created by @warlordattack on GitHub (Sep 29, 2024). ### Use case I like to have nice local dns names, -in the LAN i use AdGuard to rewrite all local DNS names to traefik with one rule using wildcard : see picture -in headscale there is " dns: > extra_records: " section for this, but unfortunatly you must add all your local dns names one by one : see picture ### Description ![image](https://github.com/user-attachments/assets/4e296149-ce2d-4db7-bc8b-467aaefecd73) Would be very nice to have record like this (to replace all the individual lines) : ![image](https://github.com/user-attachments/assets/241df073-adcd-49d9-aac6-2ffb4117ce28) The comented line would replace everything below : ![image](https://github.com/user-attachments/assets/098c613b-defc-445b-b639-35c35887be3e) ![image](https://github.com/user-attachments/assets/bb3d3c95-2544-4e59-b72d-03402b0964ab) Best regards :) ### Contribution - [ ] I can write the design doc for this feature - [ ] I can contribute this feature ### How can it be implemented? _No response_
adam added the enhancementstale labels 2025-12-29 02:24:15 +01:00
adam closed this issue 2025-12-29 02:24:15 +01:00
adam commented 2025-12-29 02:24:16 +01:00
Author
Owner
Copy Link

@jlbribeiro commented on GitHub (Oct 4, 2024):

@warlordattack Can you confirm this is a duplicate of #1840?

@jlbribeiro commented on GitHub (Oct 4, 2024): @warlordattack Can you confirm this is a duplicate of #1840?
adam commented 2025-12-29 02:24:16 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (Oct 4, 2024):

Not sure if it is a duplicate, but I am not sure we are able to do anything there, the extra_record option is just passing the options defined straight through the client (see https://github.com/tailscale/tailscale/blob/main/tailcfg/tailcfg.go#L1612), so if the client does not support it, we cant really do anything about it.

@kradalby commented on GitHub (Oct 4, 2024): Not sure if it is a duplicate, but I am not sure we are able to do anything there, the `extra_record` option is just passing the options defined straight through the client (see https://github.com/tailscale/tailscale/blob/main/tailcfg/tailcfg.go#L1612), so if the client does not support it, we cant really do anything about it.
adam commented 2025-12-29 02:24:16 +01:00
Author
Owner
Copy Link

@warlordattack commented on GitHub (Oct 4, 2024):

@warlordattack Can you confirm this is a duplicate of #1840?

i don't know :)

@warlordattack commented on GitHub (Oct 4, 2024): > @warlordattack Can you confirm this is a duplicate of #1840? i don't know :)
adam commented 2025-12-29 02:24:17 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jan 3, 2025):

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

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

@github-actions[bot] commented on GitHub (Jan 10, 2025):

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

@github-actions[bot] commented on GitHub (Jan 10, 2025): This issue was closed because it has been inactive for 14 days since being marked as stale.
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 stale
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#806
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?