Got an idea for improving dnscrypt-proxy? We'd love to hear it!
Please read the documentation first in case the behavior already exists or is already documented.
Start with a discussion
The best way to propose a new feature is to start in Discussions under the "Ideas" category. This lets us:
- Talk through the idea together
- Get feedback from other users
- Figure out the best approach
Once we've discussed and agreed on a direction, we can convert it into a tracked issue here.
This helps keep the issue tracker focused on work that's ready to be done.
Summary
It seems DNSCrypt only send a request to one server and go to the next one when it timeout.
Could you send a domain to 2 or 3 servers at the same time & return the fastest response to the client for better reliability? For example DNSMasq does this - it sends the query to multiple upstreams and return the fastest response back to the client.
dig www.google.com -p 5354 (dnscrypt-proxy port)
1st was timeout,
2nd finally return an answer
Why would this be useful?
Improve reliability!
Possible implementation
Got an idea for improving dnscrypt-proxy? We'd love to hear it!
Please read the documentation first in case the behavior already exists or is already documented.
Start with a discussion
The best way to propose a new feature is to start in Discussions under the "Ideas" category. This lets us:
Once we've discussed and agreed on a direction, we can convert it into a tracked issue here.
This helps keep the issue tracker focused on work that's ready to be done.
Summary
It seems DNSCrypt only send a request to one server and go to the next one when it timeout.
Could you send a domain to 2 or 3 servers at the same time & return the fastest response to the client for better reliability? For example DNSMasq does this - it sends the query to multiple upstreams and return the fastest response back to the client.
Why would this be useful?
Improve reliability!
Possible implementation