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] NextDNS does not work in 0.23.0-beta2 #768

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

Originally created by @mitchellkellett on GitHub (Aug 20, 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

Since upgrading to 0.23.0-beta2 from 0.23.0-beta1, I now get this error in the logs.

2024-08-20T21:03:53Z WRN Invalid global nameserver "https://dns.nextdns.io/abc123". Parsing error: ParseAddr("https://dns.nextdns.io/abc123"): each colon-separated field must have at least one digit (at "https://dns.nextdns.io/abc123") ignoring

Expected Behavior

NextDNS continues to work like versions prior to 0.23.0-beta2.

Steps To Reproduce

  1. Update config.yaml as per the new format.
  2. Start Headscale 0.23.0-beta2.
  3. Review logs.

Environment

- OS: Ubunutu 22.04
- Headscale version: 0.23.0-beta2
- Tailscale version: 1.70.0

Runtime environment

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

Anything else?

config.yaml

~~~
dns:
  magic_dns: true
  base_domain: hs.net
  nameservers:
    global:
      - https://dns.nextdns.io/abc123
  search_domains: []
  extra_records: []
~~~
Originally created by @mitchellkellett on GitHub (Aug 20, 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 Since upgrading to 0.23.0-beta2 from 0.23.0-beta1, I now get this error in the logs. 2024-08-20T21:03:53Z WRN Invalid global nameserver "https://dns.nextdns.io/abc123". Parsing error: ParseAddr("https://dns.nextdns.io/abc123"): each colon-separated field must have at least one digit (at "https://dns.nextdns.io/abc123") ignoring ### Expected Behavior NextDNS continues to work like versions prior to 0.23.0-beta2. ### Steps To Reproduce 1. Update config.yaml as per the new format. 2. Start Headscale 0.23.0-beta2. 3. Review logs. ### Environment ```markdown - OS: Ubunutu 22.04 - Headscale version: 0.23.0-beta2 - Tailscale version: 1.70.0 ``` ### Runtime environment - [X] Headscale is behind a (reverse) proxy - [X] Headscale runs in a container ### Anything else? config.yaml ``` ~~~ dns: magic_dns: true base_domain: hs.net nameservers: global: - https://dns.nextdns.io/abc123 search_domains: [] extra_records: [] ~~~ ```
adam added the bug label 2025-12-29 02:23:45 +01:00
adam closed this issue 2025-12-29 02:23:45 +01:00
adam commented 2025-12-29 02:23:46 +01:00
Author
Owner
Copy Link

@mitchellkellett commented on GitHub (Aug 20, 2024):

Updating the NextDNS url to "https://dns.nextdns.io/abc123" doesn't fix it either.

@mitchellkellett commented on GitHub (Aug 20, 2024): Updating the NextDNS url to "https://dns.nextdns.io/abc123" doesn't fix it either.
adam commented 2025-12-29 02:23:46 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (Aug 23, 2024):

I think this is an error in the warning condition and the nameserver is still added correctly? can you test if it works even tho you get the error?

@kradalby commented on GitHub (Aug 23, 2024): I think this is an error in the warning condition and the nameserver is still added correctly? can you test if it works even tho you get the error?
adam commented 2025-12-29 02:23:47 +01:00
Author
Owner
Copy Link

@mitchellkellett commented on GitHub (Aug 23, 2024):

Looks like it works, when I change it to the https version, I get the above error message printed twice in the log and then the usual start up messages. Nodes connect fine.

Navigating to https://test.nextdns.io gives me this.

{
	"status": "ok",
	"protocol": "DOH",
	"profile": "<Profile Removed>",
	"client": "<IPv6 Removed>",
	"srcIP": "<IPv6 Removed>",
	"anycast": true,
	"server": "vultr-syd-1",
	"clientName": "tailscale",
	"deviceName": "mk-mbp",
	"deviceID": "HVOPM",
	"deviceIP": "100.95.33.68",
	"deviceModel": "macOS"
}
@mitchellkellett commented on GitHub (Aug 23, 2024): Looks like it works, when I change it to the https version, I get the above error message printed twice in the log and then the usual start up messages. Nodes connect fine. Navigating to `https://test.nextdns.io` gives me this. ```json { "status": "ok", "protocol": "DOH", "profile": "<Profile Removed>", "client": "<IPv6 Removed>", "srcIP": "<IPv6 Removed>", "anycast": true, "server": "vultr-syd-1", "clientName": "tailscale", "deviceName": "mk-mbp", "deviceID": "HVOPM", "deviceIP": "100.95.33.68", "deviceModel": "macOS" } ```
adam commented 2025-12-29 02:23:47 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (Aug 23, 2024):

cool, I think I just missed a conditional cause a warning to be printet that wasnt needed.

@kradalby commented on GitHub (Aug 23, 2024): cool, I think I just missed a conditional cause a warning to be printet that wasnt needed.
adam commented 2025-12-29 02:23:47 +01:00
Author
Owner
Copy Link

@mitchellkellett commented on GitHub (Aug 23, 2024):

Awesome, thanks for the quick fix.

@mitchellkellett commented on GitHub (Aug 23, 2024): Awesome, thanks for the quick fix.
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#768
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?