subdomain added but can't get to site

[DarkShado]

Ok I am having a bit of an issue. I just added a subdomain
http://www.darkshado.22web.net/

But every time I try and go to my newly added site it just
times out.

The message I am getting is

"The connection was reset
The connection to the server was reset while the page was loading.

* The site could be temporarily unavailable or too busy. Try again in a few
moments.

* If you are unable to load any pages, check your computer's network
connection.

* If your computer or network is protected by a firewall or proxy, make sure
that Firefox is permitted to access the Web.


Now I found another site here on the forums just to make sure
I can go to that site and I can. Another one of your customers sites
who were saying they can't get to their site.. but I tried and I could
reach their site with no problem

http://byet.net/showthread.php?16460...t-go-to-my-web

so being able to reach another site on your network means it isn't
anything here on my side.. Something isn't right on the server side.

So why can't I go to my own site that I just setup. Whats going on.
I can go to other sites of your customers but not my own?

can some one please look into this?

Jamie

[kaze]

The website is working.

Please make a traceroute to your site and send it to me by PM.
http://byet.org/traceroute.php
_
Kaze

[kevin_admin]

we use several ip addresses for accounts you will find the url you CAN access will be on a different ip address to the newly added sites, and this ip is probably blocked by your ISP (based on what your saying) , a traceroute as Kaze suggests would be a good starting point.

Kev

[DarkShado]

There is the one from my machine for darkshado.22web.net

traceroute www.darkshado.22web.net
traceroute to www.darkshado.22web.net (209.51.196.253), 30 hops max, 40 byte packets
1 64.230.197.51 (64.230.197.51) 15.232 ms 19.935 ms 7.792 ms
2 dis10-london14_Vlan104.net.bell.ca (64.230.222.145) 5.628 ms 4.851 ms 5.116 ms
3 core2-london14_POS8-0-0.net.bell.ca (64.230.158.105) 5.393 ms 5.030 ms 4.857 ms
4 NEWCORE4-TORONTO12_POS9-0-0.net.bell.ca (64.230.149.222) 23.206 ms 22.496 ms 22.668 ms
5 newcore2-chicago23_so2-0-0.net.bell.ca (64.230.147.174) 22.330 ms 22.240 ms 22.591 ms
6 bx4-chicagodt_xe0-1-1-0.net.bell.ca (64.230.186.110) 27.090 ms 22.497 ms 23.362 ms
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *


Now since it cut off shortly after my ISP you are going to start screaming that it is my ISP
well it is not I went to a 3rd party site which does traceroutes and I get the same results
from there. This is NOT on my ISP these are external to my ISP on other networks.

http://network-tools.com/default.asp...hado.22web.net

209.51.196.253 is from United States(US) in region North America


TraceRoute to 209.51.196.253 [darkshado.22web.net]
Hop (ms) (ms) (ms) IP Address Host name
1 335 427 487 72.249.0.65 -
2 814 Timed out 325 64.129.174.181 -
3 1001 Timed out 336 64.129.246.132 hagg-03-ge-0-0-0-460.clmd.twtelecom.net
4 Timed out 221 236 206.222.24.2 2.18.de.static.xlhost.com
5 626 603 623 206.222.25.110 -
6 661 535 568 206.222.7.10 -
7 Destination port unreachable Destination port unreachable Destination port unreachable -
8 Destination port unreachable Destination port unreachable Destination port unreachable -
9 Destination port unreachable Destination port unreachable Destination port unreachable -
10 Timed out Destination port unreachable Destination port unreachable -

Trace aborted.


And here is a 3rd one on a 3rd different network.

http://davespeed.com/cgi-bin/traceroute.cgi

Traceroute to darkshado.22web.net

1133 EST (-0500) Thu Mar 11, 2010 from davespeed.com server in Stratford, CT

1. 64.33.48.2 (64.33.48.2) 0.897 ms
2. 69.94.3.5 (69.94.3.5) 0.979 ms
3. gi0-2.7206b.trum.fastdns.net (69.94.1.105) 338.517 ms
4. *
5. *
6. *
7. *
8. *

Halted after 5 nonresponsive hops. (more)


So this isn't an issue on my side it is occurring from 3 different networks!
This is definitely something on the server side. I clearly showed that so
please don't try and say it is on my side because it is not!

[kevin_admin]

looks like a USA carrier has added a block for 209.51.196.253 (which looks correct, its getting to our network)

As you are affected (your isp) and you can not access your site using your internet connection (that you are paying for) , you should contact your ISP's techs and escalate the issue up to a senior tech that understands `what a carrier is` (front line call center staff at an isp will not be able to help) and get them to have the block removed by the carrier ( in order to get 'access to the FULL internet which you ARE paying for) .

[DarkShado]

Kevin my ISP does NOT block any traffic. Infact the traceroutes are telling me that this is an
issue on your side. 3 different networks and all 3 are having problems.

Also if my ISP is blocking IPs then I would not be able to go to OTHER customers
websites that you host. The IP is NOT blocked my ISP does NOT block IPs like
you claim on thier routers like that.

Kevin the problem is coming from 3 different networks this is NOT an issue on my
side so stop trying to blame my connection because it is NOT an issue on my side!
l
This is an issue on YOUR side. Fix it please! All 3 traceroutes I did show that this is a
network issue on YOUR SIDE. I did traces from 3 different networks and all are having problems

That shows that it is NOT in fact an issue on my side!

God how long have you been an admin for? That is some pretty basic troubleshooting!

[kevin_admin]

Hi there,

We have seen this several times over the last 8 years we have been providing free hosting, this being a single null route added at the carrier, please be aware that a carrier is the one that supplies the bandwith / fat pipes to the ISP, the isp would not know this is happening unless they contact the carrier.

We can keep going round in circles here if you are not wanting to accept the actual issue and talk to the correct people getting it resolved.

If you try tracing from several sources here : http://www.traceroute.org/#USA you will see the packets get routed correctly, however 1 carrier (probably time warner) has nulled this ip.

best regards

[DarkShado]

Ok try and explain this one ... I added another subdomain of darkshad.byethost31.com
and it works! http://darkshad.byethost31.com

I can reach that site. It is something when it is adding the subdomain that it is working
sometimes and other times it is NOT! this is something on your side!

Maybe something is going wrong as it is adding the domains and it propagating to your
DNS servers I don't know but you need to look into it! This isn't on my side I can assure
you of that.

guys I am not trying to give you a hard time here I am trying to HELP u. But you immediately
dismiss everything as being on my side. When I have pretty well ruled that out since I did
3 traceroutes from 3 different networks and all of them were having issues.

Maybe it is something when new subdomains are added something with a script there
that is causing problems and it not propagating to your DNS or something right
this doesn't look like an issue on my side at all!

Even if it is some one in the USA that has null routed the connection to u
MY ISP can not do anything about it. So contacting my ISP would be totally
useless there would be absolutely nothing my ISP could or would do.

So telling me to contact my ISP would NOT do a darn thing.

[kevin_admin]

that site is resolving to 209.51.196.254 which does not = 209.51.196.253 which is blocked at one of your isp's carriers.

when a domain is added the subdomain is allocated an ip address from the pool, it is NOT always the same ip even on the same hosting account.

Kev

[DarkShado]

that site is resolving to 209.51.196.254 which does not = 209.51.196.253 which is blocked at one of your isp's carriers.

when a domain is added the subdomain is allocated an ip address from the pool, it is NOT always the same ip even on the same hosting account.

Kev

Kevin my ISP is NOT blocking anything there are 3 different networks that I did traceroutes from and all of them are having problems
God what is wrong with u. How long have you been a network admin for ... can't be that long.

Listen buddy You are talking to another network admin here too. and 1st off my ISP isn't blocking anything. 2nd. 3 different
networks are all experiencing the same problem.

You need to look on YOUR SIDE this isn't an issue on my side. and an ISP is not going to block a single IP they would
probably do at least a /28 or a /24 Come on .. you are just blowing this off trying to say it is on my side when it is not.

I think it is more likely something screwed with the script on your side when you add in a new subdomain
and something isn't propagating though to your DNS servers right therefore some people can't resolve
the hosts.

I have not seen a SINGLE bit of evidence yet that this is on my side.. but i have provided plenty of proof that this
IS infact an issue on your side.

Who is your manager I think at this point I need to speak with them obviously I am getting no where with u