zlacker

>>stargr+(OP)
A lot of folks here seem to be saying "if you're going to make a DNS query, you're only going to make a HTTP request," which is simply untrue. Hell, you can add a HTML tag to your page to prefetch DNS queries. Browsers prefetch DNS just for hovering your mouse over a link or typing something into your address bar (without actually navigating). Should some DNS server know your IP address just because you moved your mouse over a link? IMO, no.

>>bastaw+6E
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.

>>jivetu+L31
If 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.

>>tracke+To1
That 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.