On Friday, Jul 11, 2003, at 16:32 Canada/Eastern, Joe Abley wrote:
The APE path to F will also be available through the APE route servers. Networks peering locally with F gain lower transport latency and increased path diversity to the F root nameserver, which helps make the DNS as a whole more reliable.
By way of illustration, with: [jabley(a)new-day-rising]% traceroute f.root-servers.net traceroute to f.root-servers.net (192.5.5.241), 64 hops max, 40 byte packets 1 fa0-0.akl1.nz.2day.com (202.37.240.252) 0.987 ms 0.785 ms 0.738 ms 2 serial0-1.sky1.nz.2day.com (202.37.241.46) 3.561 ms 3.406 ms 17.47 ms 3 isc1.ape.net.nz (192.203.154.98) 3.616 ms 3.611 ms 5.372 ms 4 f.root-servers.net (192.5.5.241) 3.599 ms 3.562 ms 3.554 ms [jabley(a)new-day-rising]% and, kindly donated, without: Tracing route to f.root-servers.net [192.5.5.241] over a maximum of 30 hops: 1 <10 ms <10 ms <10 ms f4-0-1.core1.akl.iconz.net.nz [210.48.1.197] 2 <10 ms <10 ms <10 ms f0-0.gw2.akl.iconz.net.nz [202.14.100.254] 3 <10 ms <10 ms <10 ms f0-0.gw1-air.akl.iconz.net.nz [210.48.1.4] 4 <10 ms <10 ms <10 ms g0-1-0-1030.icore1.acld.telstraclear.net [203.98.54.9] 5 <10 ms <10 ms <10 ms ge0-0-0.nzsx-core1.akl.telstraclear.net [203.98.4.3] 6 <10 ms <10 ms <10 ms i-4-0-0.akl-core02.net.reach.com [202.84.219.82] 7 15 ms 32 ms 31 ms i-2-2.syd-core02.net.reach.com [202.84.249.197] 8 188 ms 187 ms 188 ms i-5-0-0.tmhstcbr02.net.reach.com [202.84.249.169] 9 188 ms 187 ms 188 ms i-10-0.tmhstcar01.net.reach.com [207.176.96.67] 10 344 ms 187 ms 188 ms isc1-FE.hkix.net [202.40.161.202] 11 188 ms 187 ms 188 ms f.root-servers.net [192.5.5.241] Trace complete. [The second trace is being answered by another local node of F, located in Hong Kong. If you don't route out via Reach, you'll likely get your packets answered in Palo Alto or San Francisco instead.]