[Zope] access to zope.com ? a bad router

[Robert OConnor]

Hi Ken,
Thanks for your note on Friday on zope.com NOT working.
(Still not working Monday morning.
I've used this as my default in the past
to get to zope but will now use zope.org

This does point out and reinforce
Michel Pelletier's point about the usefulness of
tracert.  Below is the tracert for zope.com
which seems to point to cw.net as the problem:


Tracing route to www.zope.com [206.156.192.139]
over a maximum of 30 hops:
  1   160 ms   140 ms   129 ms  208.153.17.1
  2   399 ms   538 ms   275 ms  stan-r1.pivot.net [206.98.61.126]
  3   350 ms   160 ms   140 ms  prtl-r0-e3-0.cyberTours.com [206.98.60.253]
  4   164 ms   150 ms   145 ms  borderx1-hssi4-0.Boston.cw.net
[204.70.179.109]

  5   146 ms   145 ms   140 ms  core-fddi-0.Boston.cw.net [204.70.2.33]
  6   158 ms   155 ms   155 ms  core2.Washington.cw.net [204.70.4.189]
  7   165 ms   155 ms   150 ms  border6-fddi-0.Washington.cw.net
[204.70.74.66]

  8   169 ms   159 ms   155 ms  infinet.Washington.cw.net [204.70.76.50]
  9     *        *        *     Request timed out.
10     *        *        *     Request timed out.

The route that works is zope.org:

Tracing route to zope.org [209.67.167.110]
over a maximum of 30 hops:

  1   164 ms   135 ms   145 ms  208.153.17.1
  2   135 ms   150 ms   135 ms  stan-r1.pivot.net [206.98.61.126]
  3   140 ms   150 ms   140 ms  prtl-r0-e3-0.cyberTours.com [206.98.60.253]
  4   230 ms   240 ms   200 ms  borderx1-hssi4-0.Boston.cw.net
[204.70.179.109]

  5   155 ms   153 ms   150 ms  core2-fddi0-0.Boston.cw.net [204.70.179.49]
  6   155 ms   145 ms   149 ms  core4.WestOrange.cw.net [204.70.4.77]
  7   160 ms   159 ms   155 ms  sprint3-nap.WestOrange.cw.net
[204.70.10.226]
  8   160 ms   164 ms   150 ms  pnnj-01.core.exodus.net [192.157.69.25]
  9   160 ms   170 ms   170 ms  dcr01-h10-0-0.jrcy01.exodus.net
[209.1.169.209]

10   165 ms   155 ms   160 ms  bbr01-p1-3.jrcy01.exodus.net
[216.32.173.122]
11   160 ms   160 ms   155 ms  bbr01-p5-0.hrnd01.exodus.net
[209.185.249.214]
12   165 ms   170 ms   170 ms  bbr02-p6-0.hrnd01.exodus.net [209.185.249.2]
13   240 ms   230 ms   235 ms  bbr02-p0-1.irvn01.exodus.net [209.185.9.206]
14   235 ms   235 ms   230 ms  dcr01-p6-0-0.irvn01.exodus.net
[209.185.249.17]

15  1875 ms   245 ms   235 ms  rsm-ir-b-vl921.lan.exodus.net
[209.67.128.70]
16   250 ms   250 ms   229 ms  zope.org [209.67.167.110]

Trace complete.

-----Original Message-----
From: Ken Manheimer <klm@digicool.com>
To: 'Scott Robertson' <sroberts@codeit.com>
Cc: Michel Pelletier <michel@digicool.com>; zope@zope.org <zope@zope.org>;
'billr@coinet.com' <billr@coinet.com>
Date: Friday, April 09, 1999 6:19 PM
Subject: RE: [Zope] access to zope.com ? a bad router


>On Friday, April 09, Scott Robertson sroberts@codeit.com wrote:
>> > I just ran a traceroute from here to zope.org and got pretty
>reasonable
>> > response times. Now if I try for "zope.com", that's a different
>story....
>> That's interesting two different DNS servers say zope.com is
>> 206.156.192.139, shouldn't it be 209.67.167.110 ???
>Looks like the registered DNS stuff (NIC,etc) for the other zope domains
>have to be revised - the right guys been notified.  For now, though, the
>thing to do is to not do that:-) (Ie, go to zope.org, not .com or
>.net...)
>
>Ken Manheimer
>klm@digicool.com