Subdomain "broken"

[madden]

About a week ago, I set up a new subdomain: http://essays.quotidiana.com. By the next day, it was accessible from my browser, no problem.

 

The day after that, from another computer, the subdomain wasn't accessible. I thought it might be a problem with the place I was at, like the DNS update hadn't propagated everywhere. That afternoon, the subdomain was still accessible from home.

 

Now, today, three days after, I can't access the subdomain anymore. This screws up links and CSS and javascript files and images (though I can still access the text at http://quotidiana.com/essays/). Other subdomains at the same site (http://writing.quotidiana.com/ or http://bobcats.quotidiana.com/) are fine.

 

What's going on? Any way for me to fix things?

 

Thanks,

 

Pat

[TCH-Bruce]

I have no problems accessing essays.quotidiana.com from Ohio.

 

Run a tracert to that address from the machine that cannot connect and see what's happening.

[madden]

Run a tracert to that address from the machine that cannot connect and see what's happening.

 

I'm not sure what that is or how to do it. Can you explain or point me to some instructions? Thanks,

 

Pat

[TCH-Bruce]

I am going to steal instructions one of our members wrote.

 

To run a traceroute, if you are using windows,

 

1. CLick on Start

2. Click on Run

3. In the box, type:

[tt]cmd[/tt]

Press enter

4. A Dos-like window will appear. Type tracert ******

 

So to do a tracert on Google.com, you would type tracert google.com

 

If the tracert is able to successfully contact your server, then you probably aren't currently experiencing a routing problem.

 

If the tracert gets stuck along the way, then that is the computer where you are having your routing trouble.

[madden]

Thanks. I have a Mac, though, so I don't know how to run the tracert function. If anybody knows, please pass it on. Meanwhile: doesn't it seem weird that only one subdomain is failing, and that I can access the files anyway?

[TCH-Bruce]

If it's the only one failing you can open a ticket with the help desk and ask them to take a look at it.

 

I am able to access it from home as well as from work this morning.

[madden]

I just ran a traceroute using Mac's "Network Utility" program, and got only this:

 

>traceroute: unknown host essays.quotidiana.com

 

When I run it on http://writing.quotidiana.com, I get:

 

>traceroute to writing.quotidiana.com (69.50.222.51), 64 hops max, 40 byte packets
1  * * *
2  * * *
3  slkc-dsl-gw10-202.slkc.qwest.net (67.41.239.202)  46.611 ms  47.036 ms  45.952 ms
4  slkc-agw1.inet.qwest.net (67.41.239.93)  45.962 ms  55.147 ms  46.129 ms
5  slk-core-01.inet.qwest.net (205.171.131.21)  46.841 ms  72.629 ms  58.579 ms
6  svx-core-02.inet.qwest.net (67.14.1.58)  76.660 ms  130.054 ms  64.252 ms
7  sjp-brdr-01.inet.qwest.net (205.171.214.138)  70.879 ms  167.075 ms  167.544 ms
8  cpr1-pos-13-0.sanjoseequinix.savvis.net (208.173.54.5)  171.447 ms  63.085 ms  65.976 ms
9  dcr1-so-0-3-0.sanfranciscosfo.savvis.net (204.70.194.5)  65.902 ms  70.203 ms  64.053 ms
10  dcr2-so-5-0-0.sanfranciscosfo.savvis.net (204.70.192.150)  68.936 ms  73.360 ms  64.286 ms
11  bpr2-so-7-0-0.paloaltopaix.savvis.net (208.172.147.98)  68.618 ms bpr2-so-0-0-0.paloaltopaix.savvis.net (208.172.147.94)  72.216 ms bpr2-so-7-0-0.paloaltopaix.savvis.net (208.172.147.98)  71.859 ms
12  electric-lightwave.paloaltopaix.savvis.net (206.24.241.230)  64.981 ms  70.095 ms  64.539 ms
13  p7-0.cr01.sntd.eli.net (207.173.114.137)  70.019 ms  72.831 ms  65.071 ms
14  srp3-0.cr02.sntd.eli.net (208.186.21.34)  126.980 ms  75.248 ms  64.780 ms
15  p9-0.cr01.lsan.eli.net (207.173.114.53)  125.803 ms  130.515 ms  74.338 ms
16  so-0-0-0--0.cr01.phnx.eli.net (207.173.113.106)  118.590 ms  129.565 ms  133.710 ms
17  ge-0-0-0--0.gw05.phnx.eli.net (207.173.113.94)  135.082 ms  129.161 ms  134.712 ms
18  gw0-cust-atjeu-com.phnx.eli.net (70.98.188.242)  135.289 ms  83.301 ms  84.409 ms
19  server377.snhdns.com (69.50.222.51)  83.857 ms  105.405 ms  102.956 ms

 

So, still mysterious, especially if you can access it from Ohio.

[TCH-Bruce]

Since your trace is fine please open a ticket with the help desk and have the techs take a look.

[madden]

Site is now accessible. What a frustrating thing, now knowing what was wrong or how it got fixed...

 

But thanks for the help.