Google.com unreachable when DoH to 1.1.1.1 enabled
Categories
(Core :: Networking: DNS, defect)
Tracking
()
People
(Reporter: marwanmfayed, Unassigned)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:74.0) Gecko/20100101 Firefox/74.0
Steps to reproduce:
Attempts to visit google.com are returned with FF's 'unreachable' page.
Similar issue reported here, indpendently - https://twitter.com/martinrojas/status/1243303129149562880?s=20
It occurs randomly, no warning and no ability to reproduce. Browser DNS cache issue suspected, as all other attempts to reach google.com succeeded (non-private window, CLI tools, other browsers, all succeeded).
Actual results:
This issue occurred (to me) 3 times in the week leading up to 2020/03/25, with no occurrences since. It happened as follows:
-
FF private window + DoH to CF enabled
-
"google.com" is completely unreachable; FF presents the 'unreachable' page.
-->Note that google.xxx is reachable in the window, however, where xxx \in valid TLD AND xxx != com (e.g. .co.uk, .ca, etc.)
- If I turn off DoH, clear cache, and re-enable DoH the problem is resolved
I have not tried toggling DoH on/off without the cache clear between.
Expected results:
google.com should have been reachable.
(Thanks.)
Two clarifications:
-
week leading up to --> ~7 days leading up to
-
google.com was unreachable not upon enabling DoH, but rather suddenly unreachable after extended hours or days of being fine (same window remained open with tabs opening/closing).
(Thanks.)
|
||
Comment 2•6 years ago
|
||
Hi,
Unfortunately I'm not able to reproduce this issue on Windows 10 or Mac OS 10.14. Anyway I'm setting component to Core - Networking: DNS for someone to take a look at this.
Meanwhile @marwanmfayed@gmail.com could you please try to reproduce this on our latest Nightly build? You can download it from here https://nightly.mozilla.org/. Also could you provide more info on steps to reproduce.
Thanks
Hello,
Thanks for follow-up. Unfortunately there are no steps I can offer, as this happened seemingly at random.
I can, however, report that since update to 75 I have not seen the issue. Not much to go on, unfortunately, but hopefully just enough to help identify the issue that was, or indicate this is no longer an issue.
Thanks!
|
||
Comment 4•6 years ago
|
||
The priority flag is not set for this bug.
:mayhemer, could you have a look please?
For more information, please visit auto_nag documentation.
|
||
Comment 5•6 years ago
|
||
(In reply to marwan from comment #3)
Hello,
Thanks for follow-up. Unfortunately there are no steps I can offer, as this happened seemingly at random.
I can, however, report that since update to 75 I have not seen the issue. Not much to go on, unfortunately, but hopefully just enough to help identify the issue that was, or indicate this is no longer an issue.
Thanks!
Maybe this bug is already fixed by another TRR bug, so close this as WFM.
Feel free to reopen this if you see this again. Thanks.
Description
•