DNS entries (without IP addresses) started showing up in about:networking#dns at startup even when the system is not connected to the Internet
Categories
(Core :: Networking: DNS, defect)
Tracking
()
People
(Reporter: aoia7rz7l, Unassigned)
Details
(Whiteboard: [necko-triaged][necko-priority-new])
Prerequisite:
An offline environment. Note that this issue is not reproducible in Offline Mode. To bisect this I had to allow a build to be downloaded > disconnect from the Internet > hit retry > determine if that build is good or bad > reconnect to the Internet > move on to the next build, and so on.
STR:
- Start Firefox.
- Visit
about:networking#dns.
Expected Behavior:
Nothing shows up in about:networking#dns when the system is not connected to the Internet.
Actual Behavior:
A bunch of DNS entries (without any IP addresses) that would expire within the next 60 seconds showed up in about:networking#dns. If you tried to visit e.g.bugzilla.mozilla.org in the address bar then bugzilla.mozilla.org will also show up with its own ^partitionKey= and what not.
Last good revision: f2a1d0b442ab14b7d00c4229444d4845d14cbb68
First bad revision: eb748cbf195dc2195a5a26910efb0f35a0967e03
Pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=f2a1d0b442ab14b7d00c4229444d4845d14cbb68&tochange=eb748cbf195dc2195a5a26910efb0f35a0967e03
After reading bug 1910593, I wouldn't necessarily consider this issue as a bug, but would still like to check that this was intended behavior and not some side effect.
|
||
Comment 1•9 months 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•9 months ago
•
|
||
Dont think this is a bug as well.
But need to ensure this behaviour is not hinting at some other problem due to Bug 1910593.
kershaw any thoughts?
|
||
Comment 3•9 months ago
|
||
(In reply to Sunil Mayya from comment #2)
Dont think this is a bug as well.
But need to ensure this behaviour is not hinting at some other problem due to Bug 1910593.
kershaw any thoughts?
This issue is caused by changes in nsHostResolver::GetDNSCacheEntries.
Before bug 1910593, only address records with valid addresses were shown. We changed this behavior in bug 1910593 to test whether Firefox performed DNS lookups for HTTPS records.
I don’t think this is a bug, so I'll close it. Feel free to reopen if you disagree. Thanks!
Description
•