Dns Problem, Website Shows, Then Doesnt, Then Does

[Mecca Perspective]

Hello,

 

Could some please take a moment and read my post and try to help me understand something.

 

First, hello, Im a new member, and I got here by searching yahoo about my problem, and it lead me here.

 

But heres my question.

 

2 of my Domains, www.monvalleylive.com and www.afterthoughtproductions.com have been acting WEIRD for the past few weeks.

 

MonValleyLIVE.com is a hosting reseller account with a company named HostForWeb.com, monvalleylive.com is the Name Server of itself, and afterthoughtproductions.com

( NS1.MONVALLEYLIVE.COM and NS2.MONVALLEYLIVE.COM )

 

But EVERYDAY since I changed the Nameservers for those 2 domains, the websites have been up online for say 5 hours, down for 2 hours, up for 5, down for 2,...etc. etc. I can see them only by their IP address during the time they are down. But a couple other URL's that are under that same Name Server, do the same thing, up, down, up, down. Does ANYONE know why this has been happening?

 

I called my ISP, they had me do a Trace Route, and when it started timing out, they got the information (I pasted it to them from command prompt,) and gave me a phone number of a company, who they said is OFF their network. They said the problem is caused by a hop that is off their network. I dont understand.

 

And why are the Domains sometime UP,...and sometimes DOWN? EVERYDAY. I dont understand. Who do I call about this? The people HostforWeb.com, who have the Name Server registered? My ISP again? The people who my ISP said is at fault?

 

Also, I have had a couple people check my domains that are down, and they say they can see them fine. And these people have the same ISP as I do.

 

I dont understand at all why this is happening, or if it will ever fix itself, or what I have to do to fix this.

 

ANY information someone can help me with is TRULY appriciated.

 

 

Thanks,

Mecca

[TCH-RobertM]

Mecca

This forum is a forum for Total choice hosting not sure if this is what you were looking for but If you are having problems with your HOST then I would suggest you do a few things..

 

First contact them and find out what is happening.... if they cant help you then I would certainly escalate it up there support chain.

 

 

Secondly if this is a reaccuring problem or one that you dont want to see I would suggest switching hosts ....

I STONGLY reccomend TCH TCH LINK not only because this is where I chose to host my site but MORE SO because the STAFF and People here are more than willing to jump through hoops to make the Customer Happy...

 

just my 2 cents......

[youneverknow]

Mecca,

I suggest you go to http://hostforweb.com/support.html

It looks as though they have telephone, live chat and support ticket help. Your sites both loaded here in Seattle just fine. Good Luck with your delema.

youneverknow

[Madmanmcp]

Hi Mecca, from what I can see there is a possible problem with the "NS2" nameserver and this would explain why it sometimes works and sometimes doesn't. When the request uses NS1 it works, when NS1 is busy and the NS2 is used you get the problem.

 

I ran traceroutes and on the trace to NS2 it hung up trying to get to the last hop, which would be the NS2 server from looking at the successful traceroute. So talk with your hosting company and sho them the traces that fail on THEIR nameserver, they are the ones that need to fix the problem.

 

Here are the traces:

 

Results: NS1.MONVALLEYLIVE.COM => 66.225.217.10

Results: NS2.MONVALLEYLIVE.COM => 69.61.9.75

Results: www.MONVALLEYLIVE.COM => 205.234.139.36

 

 

traceroute: Warning: Multiple interfaces found; using 198.202.76.52 @ hme0

traceroute to 69.61.9.75 (69.61.9.75), 30 hops max, 40 byte packets

1 thing-i.sdsc.edu (198.202.76.40) 1.169 ms 0.402 ms 0.999 ms

2 thunder.sdsc.edu (198.202.75.5) 1.495 ms 0.782 ms 1.044 ms

3 piranha.sdsc.edu (132.249.30.8) 1.877 ms 1.760 ms 0.961 ms

4 sdg-dc1--sdsc-sdsc2-ge.cenic.net (137.164.24.157) 2.608 ms 1.751 ms 0.988 ms

5 lax-dc1-sdg-dc1-pos.cenic.net (137.164.22.46) 3.469 ms 3.399 ms 3.837 ms

6 dc-sac-dc1--lax-dc1-pos.cenic.net (137.164.22.127) 13.019 ms 13.053 ms 13.595 ms

7 dc-oak-dc2--csac-dc1-ge.cenic.net (137.164.22.110) 15.200 ms 14.700 ms 14.647 ms

8 dc-oak-dc1--oak-dc2-p2p-1.cenic.net (137.164.22.192) 14.944 ms 14.839 ms 15.054 ms

9 dc-paix-px1--oak-dc1-ge.cenic.net (137.164.40.11) 17.115 ms 15.866 ms 16.985 ms

10 webusenet.needs.to.reg.ptr.info.with.paix (198.32.176.164) 16.622 ms 15.927 ms 16.353 ms

11 ve701.sjc-b1-01.wvfiber.net (63.223.0.189) 17.877 ms 16.420 ms 17.674 ms

12 gbe1-25-5.sjc-b0-00.wvfiber.net (63.223.1.146) 19.853 ms 18.513 ms 17.312 ms

13 pos1-36-1.lax-b0-00.wvfiber.net (63.223.0.178) 17.288 ms 15.362 ms 15.357 ms

14 63.223.0.73 (63.223.0.73) 45.736 ms 46.307 ms 45.730 ms

15 63.223.0.69 (63.223.0.69) 64.810 ms 63.491 ms 63.863 ms

16 pos10-0.atl-e00.wvfiber.net (63.223.2.90) 63.027 ms 63.719 ms 63.085 ms

17 ge-cust-globalcompass-amm-b1-00.gw.ibis7.net (63.223.3.50) 63.514 ms 63.708 ms 63.707 ms

18 ge-1-atl1-cust1.globalcompass.com (66.154.95.221) 66.303 ms 65.580 ms 66.037 ms

19 * * *

20 * * *

21 * * *

22 *

 

 

traceroute: Warning: Multiple interfaces found; using 198.202.76.52 @ hme0

traceroute to 205.234.139.36 (205.234.139.36), 30 hops max, 40 byte packets

1 thing-i.sdsc.edu (198.202.76.40) 0.730 ms 0.416 ms 0.467 ms

2 thunder.sdsc.edu (198.202.75.5) 1.561 ms 0.772 ms 1.101 ms

3 piranha.sdsc.edu (132.249.30.8) 0.962 ms 0.733 ms 1.504 ms

4 sdg-dc1--sdsc-sdsc2-ge.cenic.net (137.164.24.157) 1.276 ms 1.542 ms 0.911 ms

5 lax-dc1-sdg-dc1-pos.cenic.net (137.164.22.46) 3.337 ms 3.410 ms 3.389 ms

6 dc-sac-dc1--lax-dc1-pos.cenic.net (137.164.22.127) 12.936 ms 12.749 ms 13.747 ms

7 dc-oak-dc2--csac-dc1-ge.cenic.net (137.164.22.110) 15.302 ms 14.655 ms 15.177 ms

8 dc-oak-dc1--oak-dc2-p2p-2.cenic.net (137.164.22.194) 14.760 ms 15.817 ms 14.863 ms

9 dc-paix-px1--oak-dc1-ge.cenic.net (137.164.40.11) 15.784 ms 16.674 ms 16.813 ms

10 ge-0-1-0-501.cr1.pao1.us.nlayer.net (69.22.153.29) 16.281 ms 17.602 ms 16.001 ms

11 0.ge-1-1-0.cr1.sfo1.us.nlayer.net (69.22.143.178) 16.987 ms 18.413 ms 17.225 ms

12 0.so-0-2-0.cr1.ord1.us.nlayer.net (69.22.142.77) 64.676 ms 64.934 ms 65.063 ms

13 ge0-0-1-101.j2.ord.scnet.net (64.202.110.73) 69.705 ms 69.892 ms 69.080 ms

14 * * *

15 * * *

16 * *

 

 

traceroute: Warning: Multiple interfaces found; using 198.202.76.52 @ hme0

traceroute to 66.225.217.10 (66.225.217.10), 30 hops max, 40 byte packets

1 thing-i.sdsc.edu (198.202.76.40) 1.837 ms 0.406 ms 0.525 ms

2 thunder.sdsc.edu (198.202.75.5) 1.271 ms 1.454 ms 0.687 ms

3 piranha.sdsc.edu (132.249.30.8) 1.318 ms 1.879 ms 1.516 ms

4 sdg-dc1--sdsc-sdsc2-ge.cenic.net (137.164.24.157) 1.167 ms 1.522 ms 1.117 ms

5 lax-dc1-sdg-dc1-pos.cenic.net (137.164.22.46) 4.661 ms 4.088 ms 3.273 ms

6 dc-sac-dc1--lax-dc1-pos.cenic.net (137.164.22.127) 13.306 ms 13.500 ms 13.556 ms

7 dc-oak-dc2--csac-dc1-ge.cenic.net (137.164.22.110) 15.427 ms 14.703 ms 15.515 ms

8 dc-oak-dc1--oak-dc2-p2p-1.cenic.net (137.164.22.192) 14.879 ms 14.673 ms 14.688 ms

9 dc-paix-px1--oak-dc1-ge.cenic.net (137.164.40.11) 15.909 ms 17.701 ms 16.102 ms

10 ge-0-1-0-501.cr1.pao1.us.nlayer.net (69.22.153.29) 16.794 ms 17.041 ms 16.825 ms

11 0.ge-0-1-1.cr1.sfo1.us.nlayer.net (69.22.143.161) 16.996 ms 17.154 ms 17.187 ms

12 0.so-0-2-0.cr1.ord1.us.nlayer.net (69.22.142.77) 65.435 ms 64.945 ms 66.036 ms

13 ge0-0-1-101.j2.ord.scnet.net (64.202.110.73) 69.289 ms 69.182 ms 355.817 ms

14 ns1.servershost.net (66.225.217.10) 84.054 ms !X 70.176 ms !X 69.864 ms !X

[Mecca Perspective]

WOW,

 

Thanks for all the quick replys.

 

I agree too Madmanmcp, and everyone else who suggest that it is Host For Webs issue. Its SOOOOOO disapointing, and frustrating. Mail is the main issue here, cause when they cant be found, neither can the mail server, and thats the MAIN-MAIN issue for me. I depend on being able to interact with my websites everyday.

 

So, again, I honestly and truly appriciate the help.

 

And rmulhern, I know, (after I spent some time here) that this is for TCH. But you guys are so educated from what I have read so far, that I felt like I may as well see if someone would help me here. Because I felt like, if these guys cant help me, no one can

 

Thanks again for the help everyone. Because I really dont understand this too much, my skills are in front-end stuff.

 

Thanks,

Mecca

[TCH-Rob]

Mecca,

 

We are really happy to help in any way we can. Sometimes it makes it difficult to troubleshoot when you arent hosted here but our family will always give best effort.

 

I am glad we could point you in the right direction.