-
Notifications
You must be signed in to change notification settings - Fork 32
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
server tls or https to nextdns.. #68
Comments
Thank you for the response.. greatly appreciated.. What might be wrong with this?
./smartdns run -c local.conf -d
No different if I add in the ca-file / ca-path This is a void linux (glibc) vm.. this machine is also hosted at Vultr.. This seems to work no problem..
(run in debug mode..)
This seems to break..
(start in debug mode..)
dnsdist (the local resolver) is getting the query for dns.google (from the host-name argument it would seem), which is the fallback when there is no bootstrap Packet from 127.0.0.1:35602 for dns.google. A with id 45870 Is there something with the bootstrap? When I set the bootstrap to something that I can see.. -bootstrap-dns is what answers the query.. when its -bootstrap-dns -exclude-default-group the query does not resolve.. With no -bootstrap-dns defined and falling back to system resolver.. Something is weird with nextdns and their names.. (more testing..) NextDNS and their 'names' I can get google to work with and without names quad9, etc..
going to take a break from this.. apparently the ':' is not a valid character.. so -host-name: dns.google.com is rejected but -host-name dns.google is correct.. |
There is a bug here. It seems a bug with this crate: https://github.com/servo/rust-url |
The option use server tls://dns.nextdns.io instead? |
try
oh, no.... it should be |
@bcookatpcsd Hi, This issue should have been fixed with the following PR: Please verify it, thanks! |
@PikuZheng There is no difference here: Lines 1791 to 1793 in 10cf828
|
looks like it fixed now |
Yeah, I close it first. |
I cannot seem to get tls or https working to nextdns.
Using same config with latest smartdns seems to work:
./smartdns-x86_64 -c local.conf -x
Do you think tls/https still a work in progress?
Thank you in advance.
Alma linux (glibc), latest stable smartdns-rs (musl) not sure if that is the 'problem'
The text was updated successfully, but these errors were encountered: