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

[Bug] Different behavior depending on override_local_dns definition #1150

New Issue
Open
opened 2025-12-29 02:28:35 +01:00 by adam · 0 comments
adam commented 2025-12-29 02:28:35 +01:00
Owner
Copy Link

Originally created by @aalewis on GitHub (Nov 17, 2025).

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

Headscale 0.27.1, tailscale 1.90.6

relevant config:
dns:
  magic_dns: true
  base_domain: myexample.com
  override_local_dns: yes
  nameservers:
    global:
      - 8.8.8.8
      - 1.1.1.1

With this setup, tailscale client reports:

Resolvers (in preference order):
  (no resolvers configured, system default will be used: see 'System DNS configuration' below)

Changing override_local_dns to "no":

Resolvers (in preference order):
  (no resolvers configured, system default will be used: see 'System DNS configuration' below)

Commenting out override_local_dns results in:

  - 8.8.8.8
  - 1.1.1.1

There are now three outcomes around the override_local_dns config variable, seems like? Yes/No/Undefined.

Expected Behavior

I expect variables to have a default value, not to have different behavior if undefined.

Steps To Reproduce

See above for outcomes.

Environment

- OS: Debian Trixie
- Headscale version: 0.27.1 non-container
- Tailscale version: 1.90.6

Runtime environment

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

Debug information

n/a

Originally created by @aalewis on GitHub (Nov 17, 2025). ### 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 Headscale 0.27.1, tailscale 1.90.6 ``` relevant config: dns: magic_dns: true base_domain: myexample.com override_local_dns: yes nameservers: global: - 8.8.8.8 - 1.1.1.1 ``` With this setup, tailscale client reports: ``` Resolvers (in preference order): (no resolvers configured, system default will be used: see 'System DNS configuration' below) ``` Changing override_local_dns to "no": ``` Resolvers (in preference order): (no resolvers configured, system default will be used: see 'System DNS configuration' below) ``` Commenting out override_local_dns results in: ```Resolvers (in preference order): - 8.8.8.8 - 1.1.1.1 ``` There are now three outcomes around the override_local_dns config variable, seems like? Yes/No/Undefined. ### Expected Behavior I expect variables to have a default value, not to have different behavior if undefined. ### Steps To Reproduce See above for outcomes. ### Environment ```markdown - OS: Debian Trixie - Headscale version: 0.27.1 non-container - Tailscale version: 1.90.6 ``` ### Runtime environment - [x] Headscale is behind a (reverse) proxy - [ ] Headscale runs in a container ### Debug information n/a
adam added the bugDNS labels 2025-12-29 02:28:35 +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 DNS 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#1150
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?