RFC 8484 - DNS Queries over HTTPS (DoH)

[git001]

Output of haproxy -vv and uname -a

Future version

What should haproxy do differently? Which functionality do you think we should add?

I would like to have a option for a DoH url in the resolver, as we have now a robust HTTP/2 implementation ;-).

RFC: https://tools.ietf.org/html/rfc8484

There are now several provider for DoH which are listed here.
https://github.com/curl/curl/wiki/DNS-over-HTTPS

Companies can run there own DoH Servers similar to the classical server, a possible setup is described here.

https://www.aaflalo.me/2018/10/tutorial-setup-dns-over-https-server/

Suggestion

My suggestion is a similar syntax as for spoe.

resolvers mydoh
  type doh # new option [dns|doh|dot]
  dohservers be_MyDoH # The backend for the doh servers
  ...             # some other options

backend be_MyDoH 
  option http-use-htx # RECOMMENDED as DoH needs HTTP/2 
                                   # https://tools.ietf.org/html/rfc8484#section-5.2
  ...             # some other options
  server DoH_1 ip:port ...
  server DoH_2 ip:port ...

[lukastribus]

Mailing list discussion:
https://www.mail-archive.com/haproxy@formilux.org/msg32698.html

[git001]

Looks like this feature is not yet necessary or ready to implement.
It could be reopened in the future