Websites with DNAME records would not be accessed if DoH only mode is enabled
Categories
(Core :: Networking: DNS, defect, P2)
Tracking
()
People
(Reporter: fantasyfate, Assigned: valentin)
References
(Blocks 1 open bug)
Details
(Whiteboard: [necko-triaged])
Attachments
(4 files, 1 obsolete file)
Steps to reproduce:
- Set
network.trr.mode
to 3 - Open https://www3.risc.jku.at/
Actual results:
"Hmm. We’re having trouble finding that site."
Expected results:
This website should be opened.
I speculate that DoH implementation of Firefox might not recognize DNAME records "www3.risc.jku.at" has.
If network.trr.mode
is 0 (disabled) or 2 (enabled with fallback), this website would be opened.
Comment 1•2 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Firefox::Security' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Reporter | ||
Updated•2 years ago
|
Comment 2•2 years ago
|
||
Comment 3•2 years ago
|
||
Updated•2 years ago
|
Updated•2 years ago
|
Comment 4•2 years ago
|
||
Comment 5•2 years ago
|
||
Comment 6•2 years ago
|
||
Hello,
I followed the indicated steps on win 11 and macOS 12.5 and found 3 types of results:
- with Fx versions 102.8.0esr and 109.0 the issue is reproduced;
- with Fx versions 110.0 and Nightly 111.0b3, the issue does not reproduce, instead, we get a "Possible security risk" warning and 3 options: "Try again", "Always continue for this site" (which ensures direct acces to the site in the future) and "Change DNS Settings"
- with FX version 111.0b4 and Nighly 112.0a1 (2023-02-22), we get the security warning, but we have only 2 options: "Try again" and "Change DNS Settings" options
I'm not sure if latest versions behaviour is expected or a bug, I'll set it as new and wait for the developer's input.
Updated•2 years ago
|
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 7•2 years ago
|
||
When encountering an unknown record type in the answers we should be able to ignore it if we don't know how to parse that type.
Comment 9•2 years ago
|
||
bugherder |
Updated•2 years ago
|
Updated•2 years ago
|
Comment 10•2 years ago
|
||
Verified - fixed on MacOs12, Win 11, ubuntu 22 in Fx versions 112.0b8 and latest Nightly 113.0a1 (2023-03-29).
Description
•