zlacker

[return to "Why does 1.1.1.1 not resolve archive.is?"]
1. bastaw+6E[view] [source] 2019-10-04 13:41:09
>>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.
◧◩
2. jivetu+L31[view] [source] 2019-10-04 16:18:06
>>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.

◧◩◪
3. tracke+To1[view] [source] 2019-10-04 18:26:28
>>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.
◧◩◪◨
4. joveia+PK1[view] [source] 2019-10-04 20:56:04
>>tracke+To1
Browsers 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

[go to top]