Works as described above, but this didn’t cure the problem for me. A DOS-box window should flash up for a microsecond, the DNS cache is flushed, and the Run box exits. Linux-guy’s claimed solution thinks along these lines and he suggests flushing your local DNS, which on Windows is:ĥ. My first guess was some iffy under-the-hood Chrome update, perhaps some new and imperfect query being made to the some local and rather sluggish and partial DNS cache. ![]() * Visiting the page in ‘Incognito mode’ makes no difference. * Running with all browser extensions and scripts off also makes no difference. * Changing the Windows IVP4 DNS to another (9.9.9.9, 8.8.8.8, 1.1.1.1) makes no difference either. For instance in Opera, it’s possible to select from a number of DNS servers. The problem occurs even if you are using a DNS server other than that of your ISP. I have the same symptoms as he has: Chrome often gives this error while Pale Moon (Firefox) is totally fine. The problem appears to be cross OS, as I’m on Windows and this other guy (linked above) is on Linux. Slack also seems to be badly affected, though that doesn’t affect me… Sometimes there is a 20-30 second delay in reaching a mid-ranking site, and often nothing at all from smaller sites or certain known recalcitrant mid-ranking sites (e.g. took too long to respond.ĭoesn’t appear to affect the mega-sites like YouTube or WordPress. ![]() While browsing a site/page fails to respond to the Chrome browser, but springs instantly into action for Firefox or Pale Moon (based on Firefox). Evidently the problem is now shared by others as well as myself. A curious problem has developed persistently in recent days, for users of Chrome and Edge browser… but not for Firefox / Pale Moon.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |