Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] NextDNS does not work in 0.23.0-beta2 #2064

Closed
4 tasks done
mitchellkellett opened this issue Aug 20, 2024 · 5 comments · Fixed by #2075
Closed
4 tasks done

[Bug] NextDNS does not work in 0.23.0-beta2 #2064

mitchellkellett opened this issue Aug 20, 2024 · 5 comments · Fixed by #2075
Labels
bug Something isn't working
Milestone

Comments

@mitchellkellett
Copy link

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: []
~~~
@mitchellkellett mitchellkellett added the bug Something isn't working label Aug 20, 2024
@mitchellkellett mitchellkellett changed the title [Bug] Next DNS does not work in 0.23.0-beta2 [Bug] NextDNS does not work in 0.23.0-beta2 Aug 20, 2024
@mitchellkellett
Copy link
Author

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

@kradalby kradalby added this to the v0.23.0 milestone Aug 21, 2024
@kradalby
Copy link
Collaborator

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 added a commit to kradalby/headscale that referenced this issue Aug 23, 2024
@mitchellkellett
Copy link
Author

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"
}

@kradalby
Copy link
Collaborator

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

@mitchellkellett
Copy link
Author

Awesome, thanks for the quick fix.

kradalby added a commit to kradalby/headscale that referenced this issue Aug 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants