3 ms·
Chrome uses its own integrated DNS client rather than relying on the host OS resolver, so your problem may lie with broken DNS settings for your wifi configurat
by ginkoes 9y ago
Chrome uses its own integrated DNS client rather than relying on the host OS resolver, so your problem may lie with broken DNS settings for your wifi configuration. You can test it by running nslookup while specifying alternative name servers.
- fastball 9y agoWow, hot tip. Thanks! Changed my system's wifi settings on the network to use Google's DNS (8.8.8.8, 8.8.4.4) and it worked a treat. Does Safari also have it's own DNS resolution? That is why I missed this - googling worked just fine in Safari.
- DavideNL 9y agoExactly. This is also somewhat of a privacy issue, since Chrome sends all Dns requests for all websites you visit to Googles own dns servers, regardless of which Dns servers you have cofigured in your OS... :(