-
Notifications
You must be signed in to change notification settings - Fork 8
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
add dns-over-https resolving utility #47
Comments
I'll work on this one. |
@Ice3man543 Could you share a brief on how are you planning to do this. Did you guys found the way to send a multiple values in a single request ? Sending so many http requests doesn't sounds right. |
@bugbaba that's a good question. We are considering whether it is really needed since dns request cost less resources than HTTP requests. But we think a combination of both could be useful. |
@bugbaba I'd like for version 2 to have the DNS-over-HTTPs resolvers be an optional, configurable part of the application in the sense you can opt-out of using them and provide custom endpoints. I don't want to force users into using this at all. One of the main draws I see in supporting this feature is to provide a way to make DNS requests without "leaking" those plaintext requests you're making on a network. |
concern regarding |
I have made a separate command-line utility that does dns-over-http: https://github.com/picatz/doh I think that the majority of that code could be ripped out (or used as a library) to support resolving domains. |
The work made on |
CloudFlare and Google do this.
https://developers.google.com/speed/public-dns/docs/dns-over-https
The text was updated successfully, but these errors were encountered: