[kictanet] CCK (NOT) Preaching Wine & Drinking Water

Thu Jul 5 11:22:06 EAT 2007

Walu/Alex,

I the issue is not with CCK. They contracted local providers to provide
services here are the results .... I think the regulator did the right
thing.

dhcp-172-28-170-118:~ mucheru$ host cck.go.ke

cck.go.ke has address 195.202.66.52
cck.go.ke mail is handled by 10 smtpgate.cck.go.ke.
cck.go.ke mail is handled by 20 mx1.uunet.co.ke.
cck.go.ke mail is handled by 30 mx2.uunet.co.ke.

......

dhcp-172-28-170-118:~ mucheru$ host www.cck.go.ke
www.cck.go.ke is an alias for meru1.africaonline.co.ke.
meru1.africaonline.co.ke has address 216.251.32.98

......

dhcp-172-28-170-118:~ mucheru$ traceroute www.cck.go.ke
traceroute to meru1.africaonline.co.ke (216.251.32.98), 64 hops max, 40
byte packets
 1  loncoresw1-v250 (172.28.171.253)  1.504 ms  1.117 ms  1.436 ms
 2  lonvpn (172.28.71.65)  1.314 ms  1.392 ms  1.326 ms
 3  194.110.194.12 (194.110.194.12)  1.653 ms  1.606 ms  1.584 ms
 4  pr01-ge-3-3-0.lhr01.net.google.com (72.14.238.93)  34.801 ms  2.028 ms
 1.874 ms
 5  72.14.198.38 (72.14.198.38)  2.235 ms  1.848 ms  1.813 ms
 6  t1-1.mpd02.lon01.atlas.cogentco.com (130.117.2.26)  2.018 ms  1.838 ms
 2.784 ms
 7  t3-2.mpd01.bos01.atlas.cogentco.com (130.117.0.185)  75.256 ms  75.416
ms *
 8  g2-0-0.core01.bos01.atlas.cogentco.com (154.54.2.213)  75.192 ms 
75.581 ms  75.234 ms
 9  p5-0.core01.alb02.atlas.cogentco.com (66.28.4.110)  78.472 ms  78.730
ms  78.886 ms
10  p14-0.core01.yyz01.atlas.cogentco.com (66.28.4.218)  97.846 ms  97.975
ms  98.482 ms
11  v3490.mpd01.yyz01.atlas.cogentco.com (154.54.5.74)  97.922 ms  97.932
ms  97.889 ms
12  v3492.mpd01.yyz02.atlas.cogentco.com (154.54.5.82)  99.237 ms  236.417
ms  179.278 ms
13  * * *
14  *^C

........

dhcp-172-28-170-118:~ mucheru$ traceroute mail.cck.go.ke
traceroute to mail.cck.go.ke (195.202.66.52), 64 hops max, 40 byte packets
 1  loncoresw1-v250 (172.28.171.253)  1.474 ms  1.201 ms  1.196 ms
 2  lonvpn (172.28.71.65)  1.314 ms  1.243 ms  1.244 ms
 3  194.110.194.12 (194.110.194.12)  1.638 ms  1.533 ms  1.588 ms
 4  pr01-ge-3-3-0.lhr01.net.google.com (72.14.238.93)  1.815 ms  1.779 ms 
2.034 ms
 5  bb01-ae0.lhr02.net.google.com (72.14.238.255)  2.129 ms  2.046 ms 
1.865 ms
 6  195.50.118.209 (195.50.118.209)  2.427 ms  2.007 ms  1.946 ms
 7  ae-25-52.car5.london1.level3.net (4.68.116.51)  2.277 ms
ae-15-51.car5.london1.level3.net (4.68.116.19)  2.225 ms
ae-25-52.car5.london1.level3.net (4.68.116.51)  2.154 ms
 8  195.50.116.30 (195.50.116.30)  2.207 ms  2.418 ms  2.267 ms
 9  fus-rt001.so-2-0-0.0.globalconnex.net (80.255.35.170)  18.224 ms 
18.353 ms  18.280 ms
10  fus-rt018.vlan-3.globalconnex.net (80.255.48.18)  18.185 ms  18.848 ms
 18.191 ms
11  fus-verizon-gw.globalconnex.net (80.255.42.154)  18.284 ms  18.383 ms 
18.197 ms
12  fe-3-1.gw1.fuc1.uunet.co.ke (217.199.150.145)  25.365 ms  18.375 ms 
18.610 ms
13  fe-0-0.cr1.nbo1.uunet.co.ke (195.202.69.62)  555.176 ms  573.279 ms 
555.857 ms
14  ge-0-3.bb1.nb01.uunet.co.ke (195.202.64.19)  560.372 ms  585.759 ms 
561.936 ms
15  * * *
16  *^C

Am doing the trace from London and the traces never complete :-)

>
>
> John Walubengo wrote:
>> Michuki can correct us if we are wrong...but my
>> understanding is that ALL .KE (i.e. including ccc.go.KE)
>> would sit in the kenyan domain or name space...
>>
>
> This is the case, hence the domain name resolution process for any
> domain name in the .ke, .com and .net is done locally at the KIXP.
>
>> So I am thinking Yawes Traceroute interpratation is wrong.
>
> Yawes traceroute is right, the website is actually hosted on a server
> sitting in the US (not the UK as per the IP resource allocation). And
> the interesting part is that the server bears a hostname .ke meaning
> that its a local organization that has provided the solution/package.
>
>> Probably, he would have said that from where he is sitting
>> (assuming his desktop in Kenya) his traffic had to go out
>> of the country and then back in, before it landed on the
>> CCK website.  Which is very possible depending on how his
>> ISP has routed his traffic _ particularly if the ISP is not
>> connected through our KIXP (Kenya Internet exchange point).
>
> That is usually the scenario when one is not peering at the KIXP. But in
> this case, the hosting is actually being done in a data center in the US.
>
>
>> So I am willing to bet my pension that ccc.go.ke is on
>> kenyan soil.
>>
>
> I think you just lost your pension Walu :) ... but maybe we can invest
> it in a collocation/data center facility and make you the CEO :)
>
> On serious note there is a dire critical need for cheap colo in this
> region.
>
>
> --
> Michuki Mwangi
> KENIC
>
> _______________________________________________
> kictanet mailing list
> kictanet at lists.kictanet.or.ke
> http://lists.kictanet.or.ke/mailman/listinfo/kictanet
>
> This message was sent to: mucheru at wananchi.com
> Unsubscribe or change your options at
> http://lists.kictanet.or.ke/mailman/options/kictanet/mucheru%40wananchi.com
>