-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Comments
Updating the NextDNS url to "https://dns.nextdns.io/abc123" doesn't fix it either. |
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? |
Fixes juanfont#2064 Signed-off-by: Kristoffer Dalby <[email protected]>
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 {
"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"
} |
cool, I think I just missed a conditional cause a warning to be printet that wasnt needed. |
Awesome, thanks for the quick fix. |
Fixes juanfont#2064 Signed-off-by: Kristoffer Dalby <[email protected]>
Is this a support request?
Is there an existing issue for this?
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
Environment
Runtime environment
Anything else?
config.yaml
The text was updated successfully, but these errors were encountered: