doggo icon indicating copy to clipboard operation
doggo copied to clipboard
verified publisher icon mr-karan

Support for HTTP3

Open quaintdev opened this issue 7 months ago • 4 comments

There seems to be confusion about HTTP3 and DoQ. It's been already discussed here.

From what I have learned

DNS over HTTP/3 is not DNS over QUIC. DNS over HTTP/3 is based on DNS over HTTPS (DoH), but supports the HTTP/3 protocol DNS over QUIC (DoQ) is based directly on the QUIC protocol and uses the same port 853 as DNS over TLS (DoT) by default, but with UDP.

I am requesting that DNS over HTTPS3 be supported within Doggo.

quaintdev avatar May 15 '25 07:05 quaintdev

+1

gdyan2022 avatar Jul 22 '25 05:07 gdyan2022

+1, I definitely need this feature as well! In my use cases, supporting HTTP/3 would bring significant performance improvements and connection stability. Looking forward to seeing this implemented.

jameouni avatar Aug 07 '25 03:08 jameouni

I want to understand the use case better. Currently, doggo supports:

  • DNS over HTTPS (DoH) - RFC 8484, HTTP/2 over TLS
  • DNS over QUIC (DoQ) - RFC 9250, direct DNS messaging over QUIC

HTTP/3 is built on QUIC at the transport layer, so DNS over HTTP/3 would effectively be: DNS → HTTP/3 → QUIC

Since doggo already supports DoQ (DNS directly over QUIC), you're getting the core QUIC benefits.

Could you help me understand:

  1. What specific servers/providers you need to query that support DoH3 but not DoQ?
  2. What performance/stability benefits would DoH3 provide over existing DoQ support?
  3. Are there compliance or infrastructure requirements that mandate HTTP/3 specifically?

The main concern is that adding DoH3 support introduces HTTP/3 layer complexity for benefits that DoQ already provides at the transport level.

mr-karan avatar Oct 29 '25 15:10 mr-karan

I use these tools for test purposes, but doesn't matter who's better or enough. Also all the http family dns are natively good at anti-censorship.
Cloudflare, Google DNS, and AliDNS all support http3. They can be tested with natesales/q:

q @https://cloudflare-dns.com/dns-query --http3 example.com
# http3:// or h3:// is better, I think

But it's indeed not an urgent thing(just for me, because udp is unstable).

I do pay more attention to censorship, because from my and my friends' tests, the cloudflare-dns.com which should be banned site in mainland china can be unstablely accessible via http3.

SourLemonJuice avatar Oct 30 '25 13:10 SourLemonJuice