4 ms·
I don't understand what side you're taking here. Please can you rephrase your argument. 100% serious, I'd like to know what point you're making. Pre-emptively
by jiveturkey 7y ago
I don't understand what side you're taking here.
Please can you rephrase your argument. 100% serious, I'd like to know what point you're making.
Pre-emptively: because whatever DNS server you are using already knows your IP address, regardless whether it's the first query for the site itself, or subsequent queries for site-related additional resources.
- tracker1 7y agoIf you hover your mouse over an ad linking to sketchy-service.com ... then the remote dns host for sketchy-service.com now has your IP address.
- jiveturkey 7y agoThat seems neither here-nor-there for the 1.1.1.1 service. Doesn't the browser's internal resolver use an external recursive server (either the host's configured ones or browser-determined ones)? Chrome does, AFAICT. As opposed to being a recursive resolver itself, it just implements a caching stub resolver. The remote DNS host for sketchy-service.com doesn't see your IP address, they see the recursive server's address.
- joveian 7y agoBrowsers can also prefetch pages under some circumstances (I'm not sure of the details). In that case, the web server for sketchy-service.com now has your exact IP address (vs. the truncated address encouraged by this extension). In firefox this can be prevented with: network.dns.disablePrefetch True network.prefetch-next False
- bastawhiz 7y agoMy argument is that the "hiding your IP is pointless because the third party will get your IP anyway" is a nonsense argument. The DNS query being prefetched may have nothing to do with the current site you're on. If I go to a page that links to a bunch of sketchy websites, I don't want my IP (and thus, identity) tied to those sketchy websites just because I hovered my mouse over the links.