Issue metadata
Sign in to add a comment
|
chrome://net-internals/#dns no longer works
Reported by
joseph.c...@gmail.com,
Jan 7
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 Steps to reproduce the problem: 1. Go to chrome://net-internals/#dns What is the expected behavior? A list of the pre-fetched DNS requests should be displayed, and the "Clear host cache" button should work. What went wrong? No resolved domains appear in the list, and "Clear host cache" appears to do nothing...making it impossible to clear the Chrome's internal DNS cache. Did this work before? Yes The version before you stripped out most of the chrome://net-internals guts Chrome version: 71.0.3578.98 Channel: stable OS Version: 10.0 Flash Version:
,
Jan 7
,
Jan 7
The clear host cache button should still work, however #dns will not show anything.
,
Jan 7
It should...but it doesn't seem to do anything in my case. It would help if there were some sort of visual indication that it did something. Before chrome://net-internals was gutted, the host name list disappearing was a pretty good indication. Honestly, if Chromium is going to keep a separate DNS cache from what the host OS uses, there should be some means to view what IP address(es) a particular domain is being resolved to.
,
Jan 7
See the instructions on the duped bug.
,
Jan 7
After exporting the netlog before and after clicking the button, and sifting through the thousands of lines of JSON, I did verify the host resolver cache was cleared by clicking the button. Would still be more user friendly to just display "Host cache cleared" after clicking the button...to show some action was actually performed...at least until #892453 is completed. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by phanindra.mandapaka@chromium.org
, Jan 7