-
Notifications
You must be signed in to change notification settings - Fork 223
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
question: how to use random resolving? #66
Comments
In the # available selector: random or weighted_round_robin or lvs_weighted_round_robin
upstream_selector = "random" The default is already "random". When you have more than one upstream servers, a random upstream server will be chosen for each request. |
thanks, see #67
|
One problem with pure randomization is that "over time (days, weeks) any resolver you use (either in round robin or with a random distribution) will likely acquire enough information about an end user to profile", which is a problem for privacy (source) One solution for that is a pseudo-random choice: "the choice of the server is consistent: if the same domain is resolved twice, the same DoH server for both queries is used". This is implemented for instance in nss-tls. What about supporting |
It's a good idea. And I suggest we name the selector "hostname_hash" or "hash" to match the naming of other load balancers. I currently do not have time to implement new feature. So please help me if you are willing to. Pull requests are welcome. <3 |
Hi!
the code suggests that one can randomize the upstream servers:
How to configure dns-over-https to use it?
The text was updated successfully, but these errors were encountered: