BTW, core4.wsp.mci.net did not show up in the traceroute due to a bug in the code that we are running. (The bug has been fixed in a later version.) The direct interconnection between MCI and Sprint is in the Chicago area rather than in Denver. The connection speed is OC12 rather than DS3 :-) -- Enke
Date: Wed, 04 Sep 1996 15:23:03 -0400 From: "roy alcala" <roy@mci.net> To: Christian Nielsen <cnielsen@vii.com> CC: nanog@merit.edu
This is a private interconnect between Sprint and MCI, and the serial subnet comes out of address space assigned to MCI (so the inverse mapping is handled by MCI as well). We didn't really know what map the inverse address to in the PTR record, but we wanted it to have *some* mapping, so we just picked an arbitrary hostname.
We'd be happy to change this mapping to some other hostname (or CNAME the inverse address), if the Sprint folks would prefer something different :-)
The other end of the link has a more-descriptive DNS entry:
roy@ns% host -t ptr 89.77.157.206.in-addr.arpa 89.77.157.206.in-addr.arpa PTR core4-hssi5-0.WillowSprings.mci.net
- roy -
------------------------------------------------------------------------- | roy alcala | MCI | | IP Development | 2100 Reston Parkway | | roy@mci.net | Reston, Virginia 22091 | | beep-roy@mci.net (pager) | (703) 715-7425 | | (800) SKY-PAGE PIN 1633689 | (703) 715-7066 FAX | -------------------------------------------------------------------------
I guess sometimes they don't like to tell us what kind of link they have.
4 core1-fddi-1.Denver.mci.net (204.70.3.113) 208 ms 29 ms 19 ms 5 somerouter.sprintlink.net (206.157.77.90) 84 ms 90 ms * 6 somerouter.sprintlink.net (206.157.77.90) 86 ms 88 ms 88 ms 7 * sl-chi-6-F0/0.sprintlink.net (144.228.50.6) 168 ms 92 ms
Christian