4 ms·
> It also seems to get stuck resolving DNS sometimes, which is probably an artifact of the corporate network, but Chrome doesn't have that problem. OMG I thoug
by ptmcc 7y ago
> It also seems to get stuck resolving DNS sometimes, which is probably an artifact of the corporate network, but Chrome doesn't have that problem.
OMG I thought I was the only one running into this exact same problem! This has been a deal killer for me.
- bradstewart 7y agoMe too actually... I haven't spent any time trying to actually track it down. Unsure if it's the internal DNS servers, the Squid proxies, or what exactly. It doesn't seem to happen at home, but I don't have much runtime on FF at home yet.
- nanny 7y agoSwitch your DNS servers (I suggest 1.1.1.1). Chrome uses Google's DNS servers by default, they're probably just faster than whatever you're using.
- ptmcc 7y agoThat isn't an effective solution on a corporate network that depends on internal name resolution. And FWIW I run into the same DNS-like issues with Firefox on my home network, which uses Cloudflare's 1.1.1.1 DNS. Perhaps it is something to do with the way my company provisions my machine, I don't know. All I know is that Chrome has no issues. I've made efforts to track down the issue but it's ultimately not worth my time.
- amaccuish 7y agoDouble check it's not using or trying to autodetect a proxy?