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
A peek at Merit shows that they haven't been advertised since the 8th. http://www.merit.edu/ipma/routing_table/ has a daily snapshot of the routing tables since the 8th. >From looking at their DNS entries, I'd guess their Administrator needs to reverse the priority of the MX records. The second one isn't pingable, but is telnet port 25 -able. -EJ -----Original Message----- From: Erik Antelman [mailto:[email protected]] Sent: Thursday, June 14, 2001 11:29 AM To: [email protected] Subject: What is up with 170.36.0.0/16 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?
|