News for hackers. Stuff that matters.

A comment on Google to restrict modern ad blocking Chrome extensions to enterprise users. Parent comment

Re:Google to restrict modern ad blocking Chrome extensions t... by ptmcc on Wednesday May 29, 2019 @09:51PM (#20047639)
> 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.

[ Parent | on HN ]
Re:Google to restrict modern ad blocking Chrome extensions t... by nanny on Wednesday May 29, 2019 @10:11PM (#20047744)
Switch 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.
[ Parent | on HN ]
Re:Google to restrict modern ad blocking Chrome extensions t... by ptmcc on Thursday May 30, 2019 @12:46AM (#20048472)
That 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.

[ Parent | on HN ]
Re:Google to restrict modern ad blocking Chrome extensions t... by amaccuish on Thursday May 30, 2019 @06:17PM (#20056503)
Double check it's not using or trying to autodetect a proxy?
[ Parent | on HN ]
Re:Google to restrict modern ad blocking Chrome extensions t... by bradstewart on Wednesday May 29, 2019 @09:55PM (#20047666)
Me 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.
[ Parent | on HN ]