FEATURE REQUEST: HTTP/2 support into DoH

RouterOS RouterOS beta
1

To use the DNS4EU DoH server, HTTP/2 support is required, which seems to be missing from ROS for now. Please add HTTP/2 support for DoH.
It would be truly great if MikroTik, as a European company, supported this excellent DNS service created to provide a more secure internet, which is also backed by the EU.
https://www.joindns4.eu/learn

According to https://www.rfc-editor.org/rfc/rfc8484#page-10:
HTTP/2 [RFC7540] is the minimum RECOMMENDED version of HTTP for use with DoH.

The messages in classic UDP-based DNS [RFC1035] are inherently unordered and have low overhead. A competitive HTTP transport needs to support reordering, parallelism, priority, and header compression to achieve similar performance. Those features were introduced to HTTP in HTTP/2 [RFC7540].
Earlier versions of HTTP are capable of conveying the semantic requirements of DoH but may result in very poor performance.

2

Why to use DNS4EU, what advantages comparing to global ones like 8.8.8.8 and 1.1.1.1?

3
4

Quad9 Is also going to drop support in favor of HTTP/2,
this is somethings I would love to see in v7.21

5

Yeap, both Quad9 and DNS4EU are great choices for EU citizens, so it would be great to see the HTTP/2 released soon.

6

I’d like to see it happen too. Choosing a DNS server takes a lot of trust and discovering it went down overnight was not pleasant at all (Quad9 in my case).

7

Please add support for HTTP/2, ASAP

My trusted DNS service will no longer work on Dec. 15.
https://quad9.net/news/blog/doh-http-1-1-retirement/

8

Mikrotik is aware of the problem.

Unfortunately, it is not possible to give any ETA when the HTTP2 support will be implemented.

9

Now that Quad9 DoH no longer works, of course it is again obvious that the implementation of DoH in the DNS resolver is strange and unreliable.

It should at least be possible to have multiple DoH servers in the configuration, and also a combination of DoH and normal servers. So you could have configured 9.9.9.9 both as DoH and normal DNS, and not lose all DNS resolution as a result of this (hastened) change by Quad9.

10

This feature is very much needed. The alternative (setting up a local DNS<>DoH service) is really cumbersome. Is this even planned or should we look somewhere else?

11

Mikrotik is aware of it. And maybe even working on it. But as usual: Mikrotik does not give ETA.

12

I’m trying out pi-hole to dnscrypt-proxy to quad9 seems pretty snappy to me while I wait!

dnscrypt
dnscrypt1099×603 35.4 KB

13

Knowing that this was coming and support for DOH over HTTP/1 will be dropped it’s not to understand that Mikrotik was not resolving this coming problem already. To me Mikrotik is and will stay my first joyce when it comes to network infrastructure but some shortcomings are really hard to understand.

14

Google DNS still works, you may use them.

15

dnscrypt-proxy has a dashboard? nice

16

Well, it was quite a short notice by Quad9, and there are always services that become unusable due to changes at their end, impossible to catch up with that.

17

Impossible to catch up with 10 year old http/2 protocol. :upside_down_face:

18

Yeah but there are so many 10 year old protocols to catch up…

VTI, DNSSEC, …

19

RFC for DOH is from 2018, while http/2 is from 2015. RFC for DOH recommends http/2 as minimum http version. Still Mikrotik implemented DOH with http/1.1.
But it is just a software implementation, I am sure there will be http/2. But the 16mib flash decision is not fixable by an software update. :sad_but_relieved_face:

20

Has anyone tried the 7.22beta if DoH to DNS4EU works now with the added HTTP/2 support?