research icon indicating copy to clipboard operation
research copied to clipboard

add dns-over-https resolving utility

Open picatz opened this issue 6 years ago • 7 comments

CloudFlare and Google do this.

https://developers.google.com/speed/public-dns/docs/dns-over-https

picatz avatar Jul 11 '18 16:07 picatz

I'll work on this one.

Ice3man543 avatar Jul 12 '18 01:07 Ice3man543

@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 avatar Jul 31 '18 04:07 bugbaba

@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.

Ice3man543 avatar Jul 31 '18 09:07 Ice3man543

@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.

picatz avatar Jul 31 '18 14:07 picatz

concern regarding leaking is valid @picatz

bugbaba avatar Aug 01 '18 11:08 bugbaba

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.

picatz avatar Nov 26 '18 17:11 picatz

The work made on doh might also be a good fit for https://github.com/domainr/whois#todo

picatz avatar Nov 26 '18 17:11 picatz