North American Network Operators Group Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical e: Shared network services and transit providers
Network Solutions, Inc. (NET-INTERNIC1) INTERNIC1 198.41.0.0 - 198.41.3.0 *>i198.41.0.0 207.99.10.2 100 0 3549 6245 i * 209.191.130.93 0 10910 1239 6245 i *>i198.41.1.0 207.99.10.2 100 0 3549 6245 i * 209.191.130.93 0 10910 1239 6245 i *>i198.41.2.0 207.99.10.2 100 0 3549 6245 i * 209.191.130.93 0 10910 1239 6245 i *> 198.41.3.0 209.191.130.93 0 10910 1239 11840 i * i 209.83.160.97 100 0 6347 1239 11840 i 198.41.0/24 is where rs.internic.net is, and 198.41.3/24 is where crsnic.net is. nitrogen:~$ host -l 3.41.198.in-addr.arpa 3.41.198.in-addr.arpa name server ns1.crsnic.net 3.41.198.in-addr.arpa name server rs0.internic.net 243.3.41.198.in-addr.arpa domain name pointer trrp1.crsnic.net 53.3.41.198.in-addr.arpa domain name pointer rrp.crsnic.net 38.3.41.198.in-addr.arpa domain name pointer a.gtld-servers.net 40.3.41.198.in-addr.arpa domain name pointer sns.crsnic.net 39.3.41.198.in-addr.arpa domain name pointer ns1.crsnic.net 54.3.41.198.in-addr.arpa domain name pointer whois.crsnic.net 55.3.41.198.in-addr.arpa domain name pointer www.crsnic.net 56.3.41.198.in-addr.arpa domain name pointer mx.crsnic.net 57.3.41.198.in-addr.arpa domain name pointer ftp.crsnic.net 19.3.41.198.in-addr.arpa domain name pointer masq.crsnic.net 49.3.41.198.in-addr.arpa domain name pointer tivoli.crsnic.net Interesting, as 198.41.3/24 is the only one who has different announcements. However, this behavior from NSI wouldn't surprise me. (another company who has become overly money-motivated, rather than customer service oriented; it's disgusting what NSI has done since 1994). On Sat, 14 Aug 1999, Sean Donelan wrote: > > Shared registries and backup, note: this is not intended to be NSI bashing. > > Although NSI receives free transit from a number of backbone's, it appears > NSI is only announcing its own registry via the free transit it receives. > The shared registry whois.crsnic.net appeared to be single-homed through > Sprint today. This came up, because there was a network problem reaching > whois.crsnic.net, but it didn't affect NSI's own service. > > I also looked at several of the other well-known registries. From my > network vantage point (BGP only shows the 'best' transit): ARIN seems > to have at least two ISP connections, RIPE at least three connections. > APNIC appears single-homed through Telstra, I guess shouldn't be > surprising since its in Australia. > > Are these shared services important enough for network operators to try > to coordinate multiple connections for them? Or with competition coming, > let them each do whatever they want? > -- > Sean Donelan, Data Research Associates, Inc, St. Louis, MO > Affiliation given for identification not representation > > >
|