North American Network Operators Group Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical Re: What is up with 170.36.0.0/16
HAve youtried doing a BGP lookup for the MX's IP, rather than the whole /16? That will return the smallest aggregate that includes the target IP(s). It's entirely possible that the block is not in the table as a /16, but as a set of sub-aggregates. -Chris On Thu, Jun 14, 2001 at 11:28:36AM -0400, Erik Antelman wrote: > > Is someone renumbering around this area? > My motivation is to understand the mechanisms and techniques \ > by which a non-privelaged user (ie someone without login access to a BGP fed > router) > would diagnose (characterize, locate, identify, etc..) failure to reach a > large corporations > mail servers (1/2 of the MX servers for fleet.com) > > RADB has nothing on this, a New York QWEST looking glass says: > Query: bgp > IP address: 170.36.73.11 > Location: New York > Timeout: 20 seconds > > % Network not in table > > What's up? > > > > -- --------------------------- Christopher A. Woodfield [email protected] PGP Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xB887618B
|