Support DNS-over-HTTPS/3
Categories
(Core :: Networking: DNS, enhancement, P3)
Tracking
()
People
(Reporter: tataisoka, Unassigned)
References
(Blocks 2 open bugs)
Details
(Whiteboard: [necko-triaged])
Steps to reproduce:
Set DNS-over-HTTP options to the following
user_pref("network.trr.uri", "https://doh3.dns.nextdns.io/dns-query");
user_pref("network.trr.custom_uri", "https://doh3.dns.nextdns.io/dns-query");
user_pref("network.trr.mode", 3);
Then open test page at https://test.nextdns.io
Actual results:
The returned JSON field protocol is "DoH" (DNS-over-HTTP/2)
Expected results:
The returned JSON field protocol should be "DoH3" (DNS-over-HTTP/3)
|
||
Comment 1•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Networking: DNS' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
|
||
Comment 2•3 years ago
|
||
I took a "quic" look at the logs with the STR above, and it seems the h3 connection is closed with NS_ERROR_CONNECTION_REFUSED which causes it to be added to the excluded origins.
I haven't verified yet if this is because of Firefox or the server.
|
|
||
Updated•3 years ago
|
I don't think it is a server issue. I tested the DoH3 domain on chromium browsers and https://test.nextdns.io returned the expected result.
Some more things I noticed:
- When opening https://doh3.dns.nextdns.io on a new tab, the Network Monitor shows that it connects using HTTP/3
- However, about:networking#HTTP shows that the TRR connections to doh3.dns.nextdns.io always use HTTP/2
Don't know if this is intended behavior, though.
Description
•