[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: (TV) The Wonder Site



Keith Allison <keith@marquee.demon.co.uk> wrote:
> Just checked again with my ISP. They have no problems our end but say
> that, if the above from Maurice is the case, then the problem is
> definitely with the DNS setting/configuration at the user/browser end

I can definitely say that they are full of...  beans.

Here are traceroutes from 3 different networks here in the US:

>From riconnect.com:
zappa:~% traceroute www.marquee.demon.co.uk
traceroute to www.marquee.demon.co.uk (193.238.185.151), 30 hops max, 40 byte packets
 1  cisco.riconnect.com (209.113.194.141)  4.897 ms  2.516 ms  5.6 ms
 2  216.41.24.61 (216.41.24.61)  13.399 ms  6.217 ms  6.491 ms
 3  ri3-gw0.s2-1.conversent.net (206.53.1.241)  16.805 ms  14.029 ms  7.96 ms
 4  ri1-bb.s1-0-4-0.conversent.net (216.41.111.29)  21.226 ms  13.077 ms  10.458 ms
 5  ma1-gw1-bb.102-53.conversent.net (206.53.0.49)  14.775 ms  15.832 ms  19.733 ms
 6  63.145.0.45 (63.145.0.45)  16.224 ms  19.623 ms  17.835 ms
 7  * * *
 8  * 63.145.0.45 (63.145.0.45)  18.319 ms !N  23.096 ms !N

>From Qwest:
# traceroute www.marquee.demon.co.uk
traceroute to www.marquee.demon.co.uk (193.238.185.151), 30 hops max, 40 byte packets
 1  crunchy.dynamicdiagrams.com (216.207.71.128)  2 ms  2 ms  2 ms
 2  jfk-edge-10.inet.qwest.net (205.171.62.13)  33 ms  33 ms  33 ms
 3  jfk-edge-10.inet.qwest.net (205.171.62.13)  33 ms (ttl=254!) !H *  33 ms (ttl=254!) !H


>From HarvardNet (which has multiple backbone connections):
bass:~# traceroute www.marquee.demon.co.uk
traceroute to www.marquee.demon.co.uk (193.238.185.151), 30 hops max, 40 byte packets
 1  lucent (64.55.164.254)  0.676 ms  0.422 ms  0.396 ms
 2  192.168.200.250 (192.168.200.250)  1.144 ms  1.135 ms  0.915 ms
 3  wks240.ingenta.com (140.239.229.240)  2.019 ms  1.860 ms  1.585 ms
 4  64.55.36.131 (64.55.36.131)  1.714 ms  1.657 ms  1.658 ms
 5  140.239.225.140 (140.239.225.140)  1.606 ms  1.446 ms  1.380 ms
 6  bar1-serial5-1-0-0.Bostonbol.cw.net (208.172.53.153)  2.749 ms  2.562 ms  3.120 ms
 7  acr1-loopback.Bostonbol.cw.net (208.172.50.61)  3.208 ms  4.712 ms  2.876 ms
 8  acr2-loopback.NewYorknyr.cw.net (206.24.194.62)  8.549 ms  7.907 ms  8.577 ms
 9  bcr2-so-6-0-0.Brussels.cw.net (206.24.193.226)  90.612 ms  90.151 ms  90.746 ms
10  bcr2-so-6-0-0.Thamesside.cw.net (208.173.209.174)  92.012 ms  91.570 ms bcr1.Thamesside.cw.net (166.63.210.61)  87.015 ms
11  cable-and-wireless-internal-isp.Thamesside.cw.net (166.63.211.198)  319.808 ms  349.293 ms  414.061 ms
12  213.38.239.91 (213.38.239.91)  499.267 ms  493.584 ms  513.654 ms
13  tele-border-12.router.demon.net (194.159.252.240)  85.961 ms  85.352 ms  86.137 ms
14  tele-backbone-11-167.router.demon.net (194.159.36.73)  97.741 ms  88.127 ms  87.647 ms
15  tele-service-12-167.router.demon.net (194.159.36.76)  85.919 ms  85.630 ms *
16  tele-service-12-167.router.demon.net (194.159.36.76)  97.690 ms  97.596 ms  97.016 ms
17  www.marquee.demon.co.uk (193.238.185.151)  96.898 ms  97.434 ms  98.509 ms


Only one out of 3 worked; my guess is that they've hosed their BGP routing
tables so that some parts of the internet have the wrong routes advertised.

Interestingly, I can't get to marquee.demon.co.uk either - all traces end
at anchor-access-2-171.router.demon.net (194.159.36.52) but that might be
because that's your home machine which wasn't connected when I did the tests.

Trest me as a networking professional when I say that it is *not* any
sort of problem with Maurice's or my browser or DNS settings - they've
hosed something, and they're not 'fessing up to it.


--------------
To post: Mail tv@obbard.com
To unsubscribe: Mail majordomo@obbard.com with message "unsubscribe tv"