mirror of
https://github.com/hickory-dns/hickory-dns.git
synced 2026-04-25 11:15:54 +03:00
[GH-ISSUE #1939] DNS over HTTP/3 (DoH3) #826
Labels
No labels
blocked
breaking-change
bug
bug:critical
bug:tests
cleanup
compliance
compliance
compliance
crate:all
crate:client
crate:native-tls
crate:proto
crate:recursor
crate:resolver
crate:resolver
crate:rustls
crate:server
crate:util
dependencies
docs
duplicate
easy
easy
enhance
enhance
enhance
feature:dns-over-https
feature:dns-over-quic
feature:dns-over-tls
feature:dnsssec
feature:global_lb
feature:mdns
feature:tsig
features:edns
has workaround
ops
perf
platform:WASM
platform:android
platform:fuchsia
platform:linux
platform:macos
platform:windows
pull-request
question
test
tools
tools
trust
unclear
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hickory-dns#826
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @daxpedda on GitHub (May 20, 2023).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/1939
I couldn't find an RFC for this, but RFC9250 (DoQ) mentions:
This would probably use the
h3crate.@bluejekyll commented on GitHub (Jun 1, 2023):
Is the reasoning on this one based on the port usage? I think this should be possible. I haven't reviewed the h3 crate, so I don't know how hard/easy it would be to enable this.
@daxpedda commented on GitHub (Jun 1, 2023):
I assume so. My impression until now was that the only advantage DoH has over DoT is that it hides behind HTTP traffic. So I assume DoH3 vs DoQ is the same.