4 ms·
70 metros translate to many more POPs (also for redundancy reasons). The metros can be seen in e.g. the 1e100.net hosts in a traceroute. They're usually the cl
by puzzle 10y ago
70 metros translate to many more POPs (also for redundancy reasons).
The metros can be seen in e.g. the 1e100.net hosts in a traceroute. They're usually the closest airport code, so e.g. lhr for London.
Somebody in China reverse engineered the metro/POP naming and addressing for latency reasons. You can see that, for example, there are at least three POPs in Sydney:
https://docs.google.com/spreadsheets/d/1a5HI0lkc1TycJdwJnCVDVd3x6_gemI3CQhNHhdsVmP8 https://docs.google.com/spreadsheets/d/1a5HI0lkc1TycJdwJnCVD...
https://github.com/lennylxx/ipv6-hosts https://github.com/lennylxx/ipv6-hosts
- walrus01 10y agoyes, the practice of using IATA airport codes or similar for reverse DNS is a practice that long pre-dates google. They just adopted industry best practices when they started building consistent rDNS.
- dingaling 10y agoIt's also short-sighted as the four-character ICAO code system encodes geographical data and encompasses a magnitude more airfields. For example one can determine that EGLL is in Western Europe, UK without having to look up tables to determine that it is Heathrow.
- walrus01 10y agothis is why some ISPs use a format that maps to two letter country code, then state or subdivision, then POP. where 01 is the first pop in the city, 02 is second, etc. The ISP's own internal documentation system will tell their NOC and neteng staff which pop number is which street address/datacenter (info that does not need to be available in rDNS). in a totally random example, nyc01 POP for an ISP might be 25 broadway, nyc02 would be 60 hudson, nyc03 would be 111 8th, and so on. example agg router: agg1.nyc01.ny.us.ASNUMBER.net and then individual interfaces and subinterfaces would be defined under hierarchically under agg1.