1835627 - DNS error message does not reflect ODoH being enabled

Status: NEW

(Core :: Networking: DNS, defect, P3)

Description

[Kestrel]

Attachment: Error message showing incorrect DNS resolver with ODoH enabled

When ODoH is enabled and lookup fails, the error message displayed uses network.trr.uri/network.trr.default_provider_uri instead of network.trr.odoh.target_host:

"This website wasn’t found by mozilla.cloudflare-dns.com"

Comment 1

[Valentin Gosu [:valentin] (he/him) {{ FYI: OOO 14 June - 4 August }}]

Martin, as far as I know we have no intention of supporting ODoH, right?
If that's the case we should rip out the code and preferences.

Comment 2

[Kestrel]

This bug likely applies to OHTTP as well (network.trr.ohttp.uri). I would switch to OHTTP but I haven't been able to find any public relays for it yet so I am stuck using ODoH.

Comment 3

[Martin Thomson [:mt:]]

There isn't much point in supporting ODoH when OHTTP is equally capable and more generally useful. Though it does seem like checking the error page is worthwhile.

Comment 4

[BugBot [:suhaib / :marco/ :calixte]]

The severity field is not set for this bug.
:serg, could you have a look please?

For more information, please visit BugBot documentation.

Comment 5

[Simon Friedberger (:simonf)]

The same error message is shown when DNS security is set to "max" and there is no internet connection. Needless to say that showing people scary messages when nothing scary is happening is bad because people will ignore said messages. :valentin do you want a different bug for this? I am not entirely sure if the cause is the same.

Comment 6

[Valentin Gosu [:valentin] (he/him) {{ FYI: OOO 14 June - 4 August }}]

Bug 1872711 will track the improvement of TRR errors.

Comment 7

[Neha Kochar [:neha]]

Moving to Necko component.