Re:Cloudflare 1.1.1.1 DNS resolving issues
by Scaevolus on Wednesday October 04, 2023 @10:36AM
(#37765816)
Correct. Cloudflare's POP routing is quite extensive, and I'd be shocked if archive.is had more than a handful of backends it's routing to.
Even so, why would an extra few dozen ms matter at all? Archive.is appears to be spindle-limited, is a client with marginally higher RTT an issue? The admin is silly.
Re:Cloudflare 1.1.1.1 DNS resolving issues
by jrochkind1 on Wednesday October 04, 2023 @10:50AM
(#37766004)
It seems so silly and mysterious that it makes me wonder if archive.today wants exact client IP addresses for some other unstated reason. (It's not clear how/if archive.today, a possibly illegal site, brings in revenue?).
The whole thing is very odd.
Re:Cloudflare 1.1.1.1 DNS resolving issues
by depr on Wednesday October 04, 2023 @11:00AM
(#37766164)
There is another reason but it is stated here: https://news.ycombinator.com/item?id=36971650 (routing people to the nearest server _outside_ their own country).
Re:Cloudflare 1.1.1.1 DNS resolving issues
by arkadiyt on Wednesday October 04, 2023 @11:03AM
(#37766218)
> it makes me wonder if archive.today wants exact client IP addresses for some other unstated reason
They still get the client ip from the request to the service itself (unless you're using a VPN, but if you're using a VPN then archive wouldn't get your ip from your DNS request either).
Re:Cloudflare 1.1.1.1 DNS resolving issues
by mike_d on Wednesday October 04, 2023 @05:44PM
(#37772237)
Do you happen to have a mapping of Cloudflare IP space to physical POPs?
To the best of my knowledge they do not publish this, which makes it quite a chore to track all their edge locations manually.
Lack of EDNS only makes DNS based routing slightly worse if your CDN has a POP density similar-or-greater-than Cloudflare's.