so i’ve been doing some maintenance on sedentarysousa dot com. i uploaded the last of the changes, and refreshed the browser, only to get one of those “Firefox can’t find the server at www.sedentarysousa.com” messages.
i restarted firefox. i flushed my DNS cache, and the DNS cache of my router. i rebooted the machine, and the router. i switched browsers five times, i switched machines three times, and i switched platforms twice, but i basically got “there is no server” messages from every browser and machine combination i tried.
i then went to browsershots dot org, which uses a whole bunch of different network nodes, a whole bunch of different browsers and three different platforms, and confirmed that sedentarysousa.com was up and working the way it’s supposed to, and that made me suspicious.
because of the fact that one of my machines is wireless, and my neighbour uses a different ISP and runs an unsecured wireless network, i can switch networks fairly easily, so i did, and sedentarysousa.com showed up without a problem.
aha, i thought. the problem is with drizzle (big surprise). so i called drizzle. sure enough, the drizzle tech support people – two of them! – confirmed that sedentarysousa – and only sedentarysousa – was “offline”.
they recommended that i “contact the host provider” and have them do a traceroute to my IP address, to figure out where the problem lies.
let me get this straight… they would rather that the host provider – who is conveniently located in London, doesn’t have a problem with anybody else, and only has a problem with one route connecting – should contact the person responsible for that route to fix the problem, instead of the person responsible for the route that’s having a problem being contacted by ME to fix the problem.
it sounds very much to me as though they are saying “we don’t care, we don’t have to” – which is not the way to keep me as a customer.
very likely, what they are saying, as well, is “we don’t actually know what the problem is, or how to fix it”, which is a valid point, but it makes me feel like they are deliberately misleading me, rather than being honest and admitting that they don’t know – which is also not the way to keep me as a customer.
what really irritates me is that, what with the network being the fluid place that it is, by the time i actually discover what the problem really is, it will have fixed itself and there won’t be any evidence that whatever was causing the problem really was causing the problem. it irritates me that random things like this happen on what should be a very predictable medium. 8P
ETA: so i had the host provider do a traceroute to my IP address:
traceroute to 18.104.22.168 (22.214.171.124), 30 hops max, 40 byte packets
1 216-18-215-65.hosted.static.webnx.com (126.96.36.199) 0.316 ms 0.371 ms 0.436 ms
2 cr3-lax01.webnx.com (188.8.131.52) 0.294 ms 0.357 ms 0.410 ms
3 cust-webnx.ar10.owlax.us.easynet.net (184.108.40.206) 0.576 ms 0.723 ms 0.807 ms
4 ge-7-48.car1.SanJose2.Level3.net (220.127.116.11) 9.538 ms 9.535 ms 9.528 ms
5 * * *
6 ae-93-93.ebr3.SanJose1.Level3.net (18.104.22.168) 21.896 ms 19.398 ms 17.990 ms
7 ae-2-2.ebr3.LosAngeles1.Level3.net (22.214.171.124) 12.894 ms 9.468 ms 9.456 ms
8 ae-71-78.ebr1.LosAngeles1.Level3.net (126.96.36.199) 16.406 ms ae-91-98.ebr1.LosAngeles1.Level3.net (188.8.131.52) 16.362 ms 16.354 ms
9 ae-7-7.car1.SaltLakeCity1.Level3.net (184.108.40.206) 22.380 ms 22.130 ms 22.771 ms
10 ae-11-11.car2.SaltLakeCity1.Level3.net (220.127.116.11) 22.099 ms 22.531 ms 22.291 ms
11 18.104.22.168 (22.214.171.124) 22.579 ms 22.703 ms 22.765 ms
12 126.96.36.199 (188.8.131.52) 38.893 ms 38.961 ms 38.866 ms
13 184.108.40.206 (220.127.116.11) 43.406 ms 42.878 ms 43.912 ms
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
the place where the timeout occurred was 18.104.22.168, which is Internet Professionals & Network Solutions.
it IS drizzle’s problem! 8|