zlacker

[return to "Why does 1.1.1.1 not resolve archive.is?"]
◧
1. virapt+F3[view] [source] 2019-10-04 06:22:58
>>stargr+(OP)
> massive mismatch (...) of where DNS and related HTTP requests come from causes so many troubles

Does anyone know what they could mean here? I get that having more open connections and slow requests is not great, but there are popular attacks people will try against them in this case. They already have to handle pathologic cases of slow requests, so handling some small number of slower clients shouldn't be an issue.

Or are they talking about some other problem?

◧◩
2. miyuru+e5[view] [source] 2019-10-04 06:42:20
>>virapt+F3
They are taking about Geo load balancing via DNS.[1]

Just try one of the akamai endpoints to test it. (E.g media.steampowered.com)

For me 1.1.1.1 serves akamai singapore IPs, while 8.8.8.8 serves IPs of my ISPs akamai cache in Sri Lanka.

If your ISP has a bad route to 1.1.1.1, this just gets worse.

[1] https://en.wikipedia.org/wiki/GeoDNS

◧◩◪
3. virapt+r6[view] [source] 2019-10-04 07:02:35
>>miyuru+e5
Yeah, but... why does it matter? They're not some massive retailer where every ms potentially translates to some proportion of lost sales that add up to a significant number. They're serving archived pages.

In what case would some extra delay be worse than no access at all?

◧◩◪◨
4. michae+N6[view] [source] 2019-10-04 07:09:03
>>virapt+r6
> Yeah, but... why does it matter?

Seems pretty anti-competitive if Cloudflare's DNS stops Akamai's local caching at your ISP from working, no?

[go to top]