feature suggestion: add DNS-over-HTTPS support (RFC 8484)

[fantuz]

Recently discussed at Hackathon 101 in London this past weekend, having library support for such standard is desired.

https://tools.ietf.org/html/draft-ietf-doh-dns-over-https-05

As status draft, specifications (all the verbal process of specifiyng details) are being refined and re-defined in a work-in-progerss fashion.

I am not part of IETF but as independent I developed a similar protocol, back in time, on my own. This is why I participated to the event, and will keep listening and developing with high focus.

So @mikepultz why don't you give a read to draft, and also check the github https://github.com/dohwg/draft-ietf-doh-dns-over-https for corresponding evolving document ?

Having more implementors is surely a good support for interoperability testing, your library should have a look into this draft protocol, resolving "DNS over HTTP" with one (or more) specific MIME types, being outlined in the IETF draft.
The response format input/output is easy to understand, easy to develop if you talk DNS (the hex dump of response packet corresponds to the print() output format required, for example)

thanks for your interest in doh !

[fantuz]

Hello @mikepultz the DoH specification has become RFC 8484, see https://tools.ietf.org/html/rfc8484

Are you anyhow planning to add an option to output raw dns packet (MIME type application/dns-message) in order to support DoH proxying of responses ?

I think it would be trivial for you to add a "switch" (or API) to replace the actual response "content" with "raw" response packet.

Is such function considered useful WRT your project?

Best regards,
Massimiliano