DNS Problems - Update
I've done a LOT of screwing around over the past 24 hours and have isolated the problem via various traceroutes.
It's not a DNS problem as I had thought, there is a router (or the Tabulas box itself) dropping my packets enroute to Tabulas.
The only thing I can think of is that some router along the way, or Tabulas itself (although Roy says this isn't the case), has an IP ban in effect that is catching me in its net.
This wouldn't be the first time I've had problems with my Shaw IP. When I was (ahem) running my own mail server, many Spam eliminator programs were bouncing my emails because my IP was associated with spamming (undoubtably due to zombies on Shaw's network).
I'm going to phone Shaw and see if they'll give me a new IP since releasing and renewing just gives me the same IP back.
I'll give this another day or so and if I can't get it rectified then I'm going to have to leave Tabulas. I can't have a blog host that I can't get to from home - that's unworkable for me.
It's a pisser because I'm pretty sure I'm the only person that can't get to my blog. Everyone else I've asked to check can get there no problem. I'm loathe to leave Tabulas because I really, really like Tabulas and I don't want to move my blog again.
We'll see how it turns out. If anyone has any bright ideas, let me know.
Here's the .
tracert www.tabulas.com
Tracing route to www.tabulas.com [207.44.144.39]
over a maximum of 30 hops:
1 397 ms 69 ms 61 ms 68.145.77.1
2 56 ms 65 ms 37 ms rd1so-ge2-1-5.cg.shawcable.net [64.59.130.194]
3 89 ms 24 ms 28 ms rc1so-ge6-0.cg.shawcable.net [66.163.71.129]
4 94 ms 34 ms 37 ms rc2nr-pos13-0.wp.shawcable.net [66.163.76.86]
5 49 ms 35 ms 28 ms rc1nr-pos15-0.wp.shawcable.net [66.163.73.129]
6 80 ms 58 ms 90 ms rc1sh-pos13-0.mt.shawcable.net [66.163.76.73]
7 170 ms 72 ms 79 ms rc1hu-pos5-0.ny.shawcable.net [66.163.76.90]
8 125 ms 147 ms 73 ms fast0-0.iix-igr01.nycl.twtelecom.net [198.32.160
.35]
9 253 ms 62 ms 61 ms core-02-so-3-0-0-0.nycl.twtelecom.net [66.192.24
0.53]
10 216 ms 117 ms 83 ms core-02-so-0-0-0-0.atln.twtelecom.net [66.192.25
5.23]
11 120 ms 93 ms 95 ms dist-02-so-0-1-0-0.hsto.twtelecom.net [66.192.24
3.16]
12 145 ms 129 ms 98 ms hagg-02-ge-2-3-0-503.hsto.twtelecom.net [66.192.
246.121]
13 * * * Request timed out.
14 * *
It's not a DNS problem as I had thought, there is a router (or the Tabulas box itself) dropping my packets enroute to Tabulas.
The only thing I can think of is that some router along the way, or Tabulas itself (although Roy says this isn't the case), has an IP ban in effect that is catching me in its net.
This wouldn't be the first time I've had problems with my Shaw IP. When I was (ahem) running my own mail server, many Spam eliminator programs were bouncing my emails because my IP was associated with spamming (undoubtably due to zombies on Shaw's network).
I'm going to phone Shaw and see if they'll give me a new IP since releasing and renewing just gives me the same IP back.
I'll give this another day or so and if I can't get it rectified then I'm going to have to leave Tabulas. I can't have a blog host that I can't get to from home - that's unworkable for me.
It's a pisser because I'm pretty sure I'm the only person that can't get to my blog. Everyone else I've asked to check can get there no problem. I'm loathe to leave Tabulas because I really, really like Tabulas and I don't want to move my blog again.
We'll see how it turns out. If anyone has any bright ideas, let me know.
Here's the .
tracert www.tabulas.com
Tracing route to www.tabulas.com [207.44.144.39]
over a maximum of 30 hops:
1 397 ms 69 ms 61 ms 68.145.77.1
2 56 ms 65 ms 37 ms rd1so-ge2-1-5.cg.shawcable.net [64.59.130.194]
3 89 ms 24 ms 28 ms rc1so-ge6-0.cg.shawcable.net [66.163.71.129]
4 94 ms 34 ms 37 ms rc2nr-pos13-0.wp.shawcable.net [66.163.76.86]
5 49 ms 35 ms 28 ms rc1nr-pos15-0.wp.shawcable.net [66.163.73.129]
6 80 ms 58 ms 90 ms rc1sh-pos13-0.mt.shawcable.net [66.163.76.73]
7 170 ms 72 ms 79 ms rc1hu-pos5-0.ny.shawcable.net [66.163.76.90]
8 125 ms 147 ms 73 ms fast0-0.iix-igr01.nycl.twtelecom.net [198.32.160
.35]
9 253 ms 62 ms 61 ms core-02-so-3-0-0-0.nycl.twtelecom.net [66.192.24
0.53]
10 216 ms 117 ms 83 ms core-02-so-0-0-0-0.atln.twtelecom.net [66.192.25
5.23]
11 120 ms 93 ms 95 ms dist-02-so-0-1-0-0.hsto.twtelecom.net [66.192.24
3.16]
12 145 ms 129 ms 98 ms hagg-02-ge-2-3-0-503.hsto.twtelecom.net [66.192.
246.121]
13 * * * Request timed out.
14 * *
Currently feeling: pissed