North American Network Operators Group|
Date Prev | Date Next |
Date Index |
Thread Index |
Author Index |
RE: What is up with 126.96.36.199/16
- From: Hire, Ejay
- Date: Thu Jun 14 15:36:45 2001
A peek at Merit shows that they haven't been advertised since the 8th.
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.
From: Erik Antelman [mailto:email@example.com]
Sent: Thursday, June 14, 2001 11:29 AM
Subject: What is up with 188.8.131.52/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
would diagnose (characterize, locate, identify, etc..) failure to reach a
mail servers (1/2 of the MX servers for fleet.com)
RADB has nothing on this, a New York QWEST looking glass says:
IP address: 184.108.40.206
Location: New York
Timeout: 20 seconds
% Network not in table