Jump to content
xisto Community
Sign in to follow this  
MusicOnly

Www Problem! Trap17 Fault! [resolved] thats what they said

Recommended Posts

hello, i am having problems with my site.
i cant access my site if i type www prefix. it works fine without www.
i contacted my domain provider and they said that this is your problem!

Hello,
that is the issue with your hosting provider not with us. They have badly configured zone for your domain at their nameservers. Explain your problem to them, they will definetely fix it.

Let us know if there is anything else.


Share this post


Link to post
Share on other sites

http: // jlhaslip.trap17.com/ *note* spaces added to avoid parsing in the Forumhttp: // http://forums.xisto.com/no_longer_exists/ *same here*Even "jlhaslip.trap17.com" works. (the Browser adds the http:// for protocol)All of these work fine for me. Might this be a Browser issue? I am using Firefox 2.0.0.3, but I'm certain it works fine in all "modern" Browsers.

Share this post


Link to post
Share on other sites

Nice title to implicate how terrible Xisto has been to you.Your DNS records are being reviewed by OpaQue and he will fix why your prefix www is not responding as soon as he can. OpaQue was made aware of your situation at the time of this post.Stay tuned.

Share this post


Link to post
Share on other sites

Nice title to implicate how terrible Xisto has been to you.

read the subtitle :lol:

thx for help! i am waiting for opaque to fix this if its possible.

Share this post


Link to post
Share on other sites

Well 4 days have passed! any possible solution?

Share this post


Link to post
Share on other sites
C:\>ping http://forums.xisto.com/no_longer_exists/ 
Pinging http://forums.xisto.com/no_longer_exists/
[64.69.46.210] with 32 bytes of data:Reply from 64.69.46.210: bytes=32 time=296ms TTL=52Reply from 64.69.46.210: bytes=32 time=331ms TTL=52Reply from 64.69.46.210: bytes=32 time=346ms TTL=52Reply from 64.69.46.210: bytes=32 time=338ms TTL=52Ping statistics for 64.69.46.210: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 296ms, Maximum = 346ms, Average = 327ms

If it is some other site, May I have the domain name please ?

Share this post


Link to post
Share on other sites

Strange but it all works now!thanks OpaQue and BH for your help!so BH where was the problem? I doubt it was problem with T17!

Share this post


Link to post
Share on other sites

Honestly I do not know. My speculations are 1) we had many dropouts from hosting group in past few days--they were either non-interested or made mistakes and decided to terminate. This lead to too many clustered and uncleared data that bottlenecked WHM, which controls your DNS and cPanel. Perhaps in during this time your domain got "lost" in it and pointed to the never, never land. 2) and my best assumption is that OpaQue somehow forcefully contacted your previous nameserver or hacked into whatever is needed to be changed and demanded that everything should be resolved as it should be. Personally, I'd pick the second guess HA HA HA.But I do not know what exactly went on. OpaQue was aware of your situation but couldn't get to it until few days ago. Sorry for the delay. He said he will take care of it, the last time I spoke to him, and now he did. Looks like another mystery solved. Great job, Scooby. Topic closed :lol:

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.
Sign in to follow this  

×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.