Dear lazyweb: a Chrome question for you. I am working on a site locally, all hostnames defined in /etc/hosts, extensions off, yet Chrome hangs a lot on load with the message "resolving host..." Any idea what this is, or how to investigate it further?
-
-
Gold star here goes to
@derivativeburke. The issue was that my /etc/hosts entry didn't have an ipV6 address. Adding it fixed the timeout. 127.0.0.1 site.local <-- 10.0 second DNS timeout 127.0.0.1 ::1 site.local <-- works instantlyhttps://twitter.com/derivativeburke/status/1283253490811236352 …Show this thread -
Now the important question: who do I murder, and in what order?
Show this thread
End of conversation
New conversation -
-
-
If the local domain you've defined in /etc/hosts is *also* a valid TLD (eg .dev) you may be getting caught up by the async DNS cache. The only way I know to fix that is by doing a factory reset.
-
From user Milli on the SuperUser forum: The setting to disable the built-in asynchronous DNS cache was removed from the chrome://flags page as of this writing, but it can be disable using the command-line switch --disable-async-dns Good luck
End of conversation
New conversation -
-
-
Cloud hosting and 90 layers of abstraction will cut that down to three seconds for ya
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.