dns - My ISP is blocking my website?
2014-04
Questioner
I am not sure if this is the right place to ask this. If not, please tell me where.
I hosted my website in awardspace.com but now I am unable to connect to my site or awardspace.com. This happened a couple of times before, but now it happens very often. At first I thought it was just a crappy hosting service, but then I realized that awardspace and my site have been always online...it is just being blocked by a damn server. I can access my website and awardspace from any proxy. But from spain, I can't.
This is the traceroute:
traceroute to awardspace.com (82.197.131.36), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 7.446 ms 6.969 ms 8.445 ms
2 89.red-80-58-67.staticip.rima-tde.net (80.58.67.89) 56.382 ms 67.697 ms 58.488 ms
3 41.red-80-58-76.staticip.rima-tde.net (80.58.76.41) 53.632 ms 57.980 ms 71.693 ms
4 21.red-80-58-76.staticip.rima-tde.net (80.58.76.21) 65.289 ms 47.801 ms 48.096 ms
5 so2-0-0-0-grtmadpe3.red.telefonica-wholesale.net (84.16.6.201) 76.706 ms * 51.404 ms
6 xe8-1-0-0-grtpartv2.red.telefonica-wholesale.net (84.16.15.210) 66.847 ms 66.923 ms 65.311 ms
7 213.140.55.50 (213.140.55.50) 77.796 ms 116.578 ms 80.169 ms
8 xe-0-3-1.fra21.ip4.tinet.net (89.149.186.37) 136.179 ms
xe-3-1-1.fra21.ip4.tinet.net (89.149.181.162) 98.915 ms
xe-0-3-1.fra21.ip4.tinet.net (89.149.186.37) 104.872 ms
9 eunetworks-gw.ip4.tinet.net (77.67.72.150) 80.423 ms 96.706 ms 129.389 ms
10 ae2-irt1.dus03.de.as13237.net (217.71.96.117) 84.497 ms 86.116 ms 79.715 ms
11 xe3-0-0.irt1.dus53.de.as13237.net (217.71.96.113) 82.364 ms 83.968 ms 81.745 ms
12 xe0-2-0.irt1.han87.de.as13237.net (217.71.96.77) 86.432 ms 89.351 ms 85.103 ms
13 xe0-2-0.irt1.ham21.de.as13237.net (217.71.96.89) 105.067 ms 90.882 ms *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
Is there a solution for this? Or should I just change hosting?
thanx in advance
NickW
Actually you're probably not seeing a block, a block would be there permanently, you are probably seeing some routing problems between your ISP (or their provider) and the network you need to reach. If it were your ISP, you'd be seeing the traffic dropped much sooner. Notice the traffic gets to somewhere in Germany from the last tinet, it goes to Dusseldorf, then Hanover, then Hamburg, all in the AS13237 network. If your traffic is dying there, it's usually a routing problem, unless there literally is no other route to that network, which would be awfully odd for a hosting provider.
If it's a common issue, it might be worth changing hosters.
Mark
I'm having trouble connecting to a particular website. I can view it through a proxy, but not from home. So I ran a traceroute:
Tracing route to fvringette.com [76.74.225.90]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms <snip>
2 * * * Request timed out.
3 9 ms 7 ms 27 ms rd2bb-ge2-0-0-22.vc.shawcable.net [64.59.146.226]
4 8 ms 7 ms 7 ms rc2bb-tge0-9-2-0.vc.shawcable.net [66.163.69.41]
5 10 ms 9 ms 9 ms rc2wh-tge0-0-1-0.vc.shawcable.net [66.163.69.65]
6 27 ms 23 ms 22 ms ge-gi0-2.pix.van.peer1.net [206.223.127.1]
7 18 ms 18 ms 20 ms 10ge.xe-0-2-0.van-spenc-dis-1.peer1.net [216.187.89.206]
8 9 ms 11 ms 10 ms 64.69.91.245
9 * * * Request timed out.
10 * * * Request timed out.
...
Looks like this "64.69.91.245" is somehow blocking me. Can I tell my computer to avoid/bypass that IP when trying to connect?
squircle
For one, I can load the site fine. See the route:
0 04:35:23pm ~ $ mtr -4 --report fvringette.com
HOST: Defcon.local Loss% Snt Last Avg Best Wrst StDev
1. woodcrest.local 0.0% 10 0.6 0.5 0.4 0.8 0.1
2. bas1-oakville30_lo0_SYMP.net 0.0% 10 14.0 16.1 13.1 31.2 5.4
3. core1-hamilton14_10-0-3_150. 0.0% 10 13.3 12.8 11.6 15.7 1.1
4. newcore1-chicago23_so2-0-0.n 0.0% 10 23.6 31.4 23.6 66.3 16.0
5. bx5-chicagodt_xe-0-0-3_0.net 0.0% 10 24.7 24.6 23.2 28.5 1.6
6. ge-3-2-4.chi10.ip4.tinet.net 0.0% 10 26.7 26.9 26.3 28.0 0.5
7. xe-2-0-0.sea11.ip4.tinet.net 0.0% 10 107.0 106.8 106.0 107.5 0.4
8. peer1-gw.ip4.tinet.net 0.0% 10 83.9 83.9 83.6 84.6 0.3
9. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
10. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11. 64.69.91.245 0.0% 10 88.6 87.9 87.1 88.6 0.6
12. van-hc21e-cs1.wappyzappy.net 10.0% 10 88.7 88.0 87.4 88.7 0.5
It would appear that (somehow) the two nodes, 9 & 10 in my route, are either blocking ICMP packets or have some other form of network voodoo implemented. It could be that when you were accessing the site through the proxy, you were accessing some cached version when the website was really down, who knows. The fact that there is 100% packet loss in nodes 9 & 10 is odd, but since I can (obviously) reach the site, it doesn't appear that 64.69.91.245 (Peer1 Internet Bandwidth & Server Co-Location Facilities, 2155-500 West Hastings St., Vancouver) is doing anything to block any traffic (in all likelihood, they are just ignoring ICMP packets).
To more directly answer your question, it's pretty much impossible to define your own route to a site. Since (I would assume) all packets would pass through that address at one point or another to get to the actual host (as it's the external IP of the datacentre the servers are hosted in), there would be no route around it. Once your packet gets outside of your router, it's up to Shaw what route your packet takes; you have no control whatsoever. Hope that helps a bit!
raw_noob
I think you can do this by forcing a particular IP routing using the route add command at the command prompt, but it will take a better man than I am to explain exactly how. You might do a search on 'add a static IP route' or 'force IP routing' to get some idea. I don't know if you can block a specific node, but I wouldn't be surprised if you can. Forcing a specific route that avoids the node would be the alternative.
Blackbeagle
Are you going to a site that is somehow geographically restricted? There are sites that will only accept traffic from certain regions and if your IP address is not within their allowed list, the packets may be eaten. The reason I'm asking is that you said you can access through a proxy.