Quad9 Enables DNS over HTTP/3 and DNS over QUIC(quad9.net)
quad9.net
Quad9 Enables DNS over HTTP/3 and DNS over QUIC
https://quad9.net/news/blog/quad9-enables-dns-over-http-3-and-dns-over-quic/
19 comments
Excellent. Since privacy and cybersecurity are goals, TLS Encrypted Client Hello (RFC 9849, ECH) and its DNS service bindings (RFC 9848) were finalized last month.
Quad9 has enabled DNS over HTTP/3 (DoH3) and DNS over QUIC (DoQ) across its global resolver network.
Quad9 is quite unreliable. Lots of outages and the like.
I've been using Quad9 at home for years as my only upstream DNS resolver and your comment does not track at all with my experience. My ISP goes out more often.
Well, my experience differs. Lots and lots of downtimes in the EU region. Not using the default one, I'm using the one without any malware etc. related protections.
Does quad9 have a resolver that includes ad blocking?
"Does Quad9 offer content filtering? No. Quad9 has no plans to provide content filtering. Quad9 is dedicated solely to internet security and the blocking of malicious domains, such as phishing, malware, and exploit kits." https://quad9.net/support/faq/#dns_crypt
That's a shame, because ad blocking would seem to fit in:
> blocking of malicious domains
> blocking of malicious domains
I expect Mullvad will implement all this soon enough, and they do have adblocking with public endpoints.
[deleted]
So many more layers than the original simple DNS protocol.
"Simple" doesn't always mean "better". A car without seatbelts is less complicated than one with, but it definitely doesn't make it a better car.
Similarly, The original DNS protocol doesn't have any form of verification: it is is trivially easy for a MitM attacker to alter the responses - or even for a non-MitM one to send spoofed responses "in the blind". It also doesn't have any form of confidentiality: it is trivially easy for a MitM attacker to log all the requests you make, which essentially means your entire browser history.
It takes an awful lot of hacking to turn classic DNS into something even remotely representing a mature and well-designed protocol. By the time you are done bolting on all the other stuff it really isn't all that simple anymore.
Similarly, The original DNS protocol doesn't have any form of verification: it is is trivially easy for a MitM attacker to alter the responses - or even for a non-MitM one to send spoofed responses "in the blind". It also doesn't have any form of confidentiality: it is trivially easy for a MitM attacker to log all the requests you make, which essentially means your entire browser history.
It takes an awful lot of hacking to turn classic DNS into something even remotely representing a mature and well-designed protocol. By the time you are done bolting on all the other stuff it really isn't all that simple anymore.
> it is is trivially easy for a MitM attacker to alter the responses
This is true even for DOH. There is no guaranty that your TLS certificate issuer is to be trusted. And, by the way, most of them are in the USA, a country known for its surveillance programs.
This is true even for DOH. There is no guaranty that your TLS certificate issuer is to be trusted. And, by the way, most of them are in the USA, a country known for its surveillance programs.
Too bad ISPs are real dicks and capture all your DNS requests for tracking and resale.
OK. It is still there, and you are welcome to use it.
[1] https://joindns4.eu/