starred/headscale
1
0
Fork 0
mirror of https://github.com/juanfont/headscale.git synced 2026-01-12 04:10:32 +01:00
Code Issues 98 Packages Projects Releases 10 Wiki Activity

[Bug] headscale uses cfg.BaseDomain for building FQDNs #892

New Issue
Closed
opened 2025-12-29 02:25:32 +01:00 by adam · 0 comments
adam commented 2025-12-29 02:25:32 +01:00
Owner
Copy Link

Originally created by @valkum on GitHub (Dec 27, 2024).

Is this a support request?

  • This is not a support request

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

The config currently knows of:

  • cfg.BaseDomain: not configurable through the config.yaml, set to cfg.DNSConfig.BaseDomain, used for Domain in MapResponse
  • cfg.DNSConfig.BaseDomain: described as the magic DNS base domain.

MapResponse.Domain is used by GUIs to show the tailnet organization name (text below your username).
Currently, you can only configure the magic DNS base domain which will be used as the organization name. This is also used to build the FQDNs in host mappings.

Expected Behavior

Be able to configure the organization name (organization domain) independently of the magic DNS base domain, as it is possible with tailscale.

Steps To Reproduce

  1. run tailscale with webclient=true and observe that the magic DNS (called suffix in tailscale dns status) base domain is used as the org name at the top.

Environment

- OS: n/a
- Headscale version: 0.23
- Tailscale version: 1.78.1 macos/windows

Runtime environment

  • Headscale is behind a (reverse) proxy
  • Headscale runs in a container

Anything else?

I have a PR ready to fix this.

Originally created by @valkum on GitHub (Dec 27, 2024). ### Is this a support request? - [X] This is not a support request ### Is there an existing issue for this? - [X] I have searched the existing issues ### Current Behavior The config currently knows of: * `cfg.BaseDomain`: not configurable through the config.yaml, set to `cfg.DNSConfig.BaseDomain`, used for `Domain` in `MapResponse` * `cfg.DNSConfig.BaseDomain`: described as the magic DNS base domain. `MapResponse.Domain` is used by GUIs to show the tailnet organization name (text below your username). Currently, you can only configure the magic DNS base domain which will be used as the organization name. This is also used to build the FQDNs in host mappings. ### Expected Behavior Be able to configure the organization name (organization domain) independently of the magic DNS base domain, as it is possible with tailscale. ### Steps To Reproduce 1. run tailscale with webclient=true and observe that the magic DNS (called suffix in `tailscale dns status`) base domain is used as the org name at the top. ### Environment ```markdown - OS: n/a - Headscale version: 0.23 - Tailscale version: 1.78.1 macos/windows ``` ### Runtime environment - [ ] Headscale is behind a (reverse) proxy - [ ] Headscale runs in a container ### Anything else? I have a PR ready to fix this.
adam added the bug label 2025-12-29 02:25:32 +01:00
adam closed this issue 2025-12-29 02:25:32 +01:00
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 bug
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#892
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?