Severe problems in reaching OARCorp
Ralf Corsepius
ralf_corsepius at rtems.org
Sat Nov 27 05:43:09 UTC 2004
On Thu, 2004-11-25 at 12:10 -0500, Bogdan Vacaliuc wrote:
> On Thursday, November 25, 2004 11:50 AM, Ralf Corsepius wrote:
> > More bizarre: Even trying to access the IP-addresses (216.107.91.229
> > rsp. 216.107.91.227) doesn't work.
>
> It was intermittent, recently for me. Some packet loss, but not always complete loss; its down now. Possibly a temporary ISP
> routing issue?
>
> The namerserver is behaving stragely, however for rtems.org but not for oarcorp.com:
>
> [~] !123
> nslookup www.oarcorp.com NS1.NETWORKTEL.NET
> Server: ns1.networktel.net
> Address: 216.83.236.227
>
> Name: www.oarcorp.com
> Address: 216.107.91.227
Here, you were able to access ns1.networktel.net.
> [~] !125
> nslookup rtems.com NS1.NETWORKTEL.NET
> Server: ns1.networktel.net
> Address: 216.83.236.227
>
> Name: rtems.com
>
> [~]
>
> Where's the address for rtems.com?
>From what I see, {ns1|ns2}.networktel.net currently aren't accessible
from here at all.
> nslookup www.oarcorp.com NS1.NETWORKTEL.NET
;; connection timed out; no servers could be reached
> nslookup www.rtems.com NS1.NETWORKTEL.NET
;; connection timed out; no servers could be reached
> nslookup www.rtems.com NS2.NETWORKTEL.NET
;; connection timed out; no servers could be reached
> nslookup www.oarcorp.com NS2.NETWORKTEL.NET
;; connection timed out; no servers could be reached
> Traceroute says:
>
> Tracing route to www.oarcorp.com [216.107.91.227]
> over a maximum of 30 hops:
>
> 1 <10 ms <10 ms <10 ms 192.168.3.254
> 2 16 ms <10 ms 16 ms gw-dslv-1.mv.net [207.22.18.1]
> 3 15 ms 32 ms 15 ms ag-mvcommun-serial10-1-0.bosma01.paetec.net [64.
> 80.7.197]
> 4 <10 ms 16 ms 15 ms bb-vlan3-eth0-0-1.bosma01.paetec.net [66.155.217
> .34]
> 5 16 ms 16 ms 15 ms 64.80.254.246
> 6 15 ms 16 ms 16 ms ge-0-0-0.ar1.NYC1.gblx.net [64.210.21.93]
> 7 62 ms 47 ms 47 ms so3-0-0-2488M.ar3.DAL1.gblx.net [67.17.70.201]
> 8 47 ms 63 ms 62 ms ITC-Deltacom.so-0-0-0.ar3.DAL1.gblx.net [64.208.
> 169.142]
> 9 47 ms 62 ms 47 ms gig2-0.dllstxal0rw.xr.deltacom.net [66.35.174.21
> 4]
> 10 62 ms 63 ms 78 ms 66.35.174.81
> 11 62 ms 63 ms 62 ms gig2-0.brhmalwd6aw.xr.deltacom.net [66.35.174.20
> 6]
> 12 63 ms 62 ms 78 ms 66.35.174.14
> 13 62 ms 63 ms 62 ms 66.35.170.134
> 14 63 ms 62 ms 63 ms 216.248.128.254
> 15 78 ms 62 ms 63 ms 216-83-239-17.wan.networktel.net [216.83.239.17]
>
> 16 78 ms 63 ms 78 ms 216-83-239-58.wan.networktel.net [216.83.239.58]
>
> 17 62 ms 78 ms 79 ms 216-107-82-70.wan.networktel.net [216.107.82.70]
>
> 18 * * * Request timed out.
..
Meanwhile the situation seems to have worsened:
# traceroute www.oarcorp.com
traceroute to www.oarcorp.com (216.107.91.227), 30 hops max, 38 byte packets
...
6 lndnuk1icx1.wcg.net (195.66.224.105) 160.881 ms 164.084 ms 163.522 ms
7 nycmny2wcx2-pos15-3.wcg.net (64.200.87.61) 163.818 ms 161.338 ms 163.774 ms
8 hrndva1wcx2-pos1-0-oc192.wcg.net (64.200.210.178) 162.603 ms 161.342 ms 163.765 ms
9 hrndva1wcx3-pos4-0-oc192.wcg.net (64.200.89.122) 163.841 ms 162.541 ms 164.773 ms
10 drvlga1wcx2-pos3-0-oc192.wcg.net (64.200.210.237) 173.933 ms 172.956 ms 171.423 ms
11 atlnga6lce1-pos5-0.wcg.net (64.200.127.62) 172.923 ms 172.654 ms 172.155 ms
12 atlnga6lce1-bti-pos.wcg.net (64.200.126.98) 170.483 ms 172.211 ms 172.902 ms
13 66.35.170.134 (66.35.170.134) 176.126 ms 176.702 ms 176.845 ms
14 * * *
15 * * *
Within the last hour, all traceroutes ended with a 66.35.170.x address
(According to whois, owned by ITC-DeltaCom).
So, as it seems to me, the cause probably is the networktel.net
nameservers being unreachable or at least flaky for several days,
may-be due to routing problems between Networktel and ITC-DeltaCom.
I guess, this might have caused some DNS-servers to drop oarcorp.com and
rtems.com, while others still have these in there caches.
Ralf
More information about the users
mailing list