4 ms·
Last I knew, you couldn't disable Chrome's async DNS feature, which will bypass your system's configured DNS servers and use Google's own. So, while certainly n
by nirvdrum 9y ago
Last I knew, you couldn't disable Chrome's async DNS feature, which will bypass your system's configured DNS servers and use Google's own. So, while certainly not the same level of tracking that Google Analytics or even browser history can perform, many (all?) domains you visit are still sent back to Google in one form or another:
https://bugs.chromium.org/p/chromium/issues/detail?id=432236 https://bugs.chromium.org/p/chromium/issues/detail?id=432236
- irrational 9y agoWell, I don't use Chrome. Do you know if this affects Firefox as well?
- nirvdrum 9y agoIt shouldn't. I must've just gotten myself mixed up. I thought this thread was about Chrome phoning home. Sorry for propagating confusion.
- TeMPOraL 9y agoHoly hell. So this is the dumb DNS crap Chrome is doing. I had occasional issues with Chrome suddenly not being able to load anything due to what looked like obvious DNS issues, except they didn't affect anything else and there was no way for me to do anything with it except wait it out. There were moments I thought I'm imagining things.
- nirvdrum 9y agoYeap! And if you're on a private network you can leak internal domain names. Or, if you some hosts that are available publicly but resolve differently internally, you'll get the wrong IP. I think the only real solution is to kill Google's DNS IPs in your routing table.