Shared Hosting Account Server Update - Known Issues And Solutions

[BuffaloHelp 24]

Hi Xisto hosting members.

First of all I would like to thank you hosting members for staying patient during these difficult times.

Xisto - Support.com announced Data Center (DC) migration to bigger facility for the growing demand. This is to provide much more reliable service to all free web hosting members. However it did not go smoothly as server technicians hoped. Even with their relentless efforts to bring the service back online there are some known issues which I'd like to address.

The first issue is that those with TLD (top level domain) will notice that pining their domain names shows old hosting IP (64.69.46.210). There's nothing at your end can be done since I believe it's at the hosting server's end. I am only guessing this because I have not received any official answer from the support team. But you will notice that hosting members with Xisto sub-domain gained full access to their hostings.

You can access your cpanel (for those with TLD) by 208.87.243.146/cpanel Use your cpanel username and password and you will be able to access your cpanel. gamma.xisto.com/~cpanelUSERNAME will also show your site up and running. And thus, I believe the problem is with DNS resolution at the server end. And since I do not have the official answer I will state this unless I am corrected, otherwise.

The second issue is changing of name server IPs. If you are using the current and correct name servers you do not need to worry. For those who are using IP address rather than name server alias please double check your setting.

ns.computinghost.com retaining IP 67.19.253.52
ns2.computinghost.com retaining IP 208.87.241.124

The third is try to flush your DNS. If you open your command window and ping your domain name and shows old IP please flush DNS by:

CONSOLE

ipconfig /flushdns

And ping your domain again. It should reply back with 208.87.243.146

I was requested by our fellow hosting members to just give some information to go by, instead of left out in the dark. I will update as more information is available.

The hindsight is 20/20. Yes, they acknowledge that the forum should also carried this important announcement. They also ask for your understanding and continuing support.

Thank you.

PS You can bypass propagation or resolution period by editing HOSTS file. For more information on bypassing DNS propagation or resolution period please try the following:

Amend the following to your HOSTS file (there are two under Windows XP. HOSTS file does not have any extension where as hosts.ics is NOT to be touched. You can see the full extension by Tools>>Folder Options>>View>>unchecking "Hide extensions for known file types")

HOSTS file is located under

for Windows Vista
method 1
method 2

for Windows XP

CONSOLE

windows\system32\drivers\etc

for Windows 2000

CONSOLE

winnt\system32\drivers\etc

for Windows ME or 98

CONSOLE

windows\

Open HOSTS with your Notepad and add the following under 127.0.0.1 (this is NOT to be touched) So you should see before saving and closing as such:

CONSOLE

127.0.0.1 ???? ???? localhost
208.87.243.146 ????http://www.yourdomain.com/
208.87.243.146 ????yourdomain.com

Save it, close all your browsers and reopen them to your site. It should work now.

PPS!!! Don't forget to remove the appended change once DNS is resolved fully. vujsa just pointed out that if we happen to change our IP address again, you don't want to be stuck with the old IP.

 

[yordan 10]

Thanks for the info.
Anothen way of reaching the cpanel was with the link https://support.xisto.com/, the cpanel link in the rightmost colum worked.
Fortunately, the DNS propagation is finished and my own site is visible again.
The problem I see with editing my own hostfile is, that it works only for myself.
The persons who used to visit my site cannot know that they have to edit their host file, so this workaround is useless for public sites as mine.
Nevertheless, thanks for the workaround host trick, it will be useful next time surch a problem will occur.
And thanks to all the technical staff, they did a good job.

[Atomic0 0]

Do the following nameservers work for Xisto?ns1.Astahost.comns2.Astahost.comThey were the ones supplied with the Web Hosting Account Application approval email.

[Arbitrary 0]

Do the following nameservers work for Xisto?
ns1.Astahost.com
ns2.Astahost.com

They were the ones supplied with the Web Hosting Account Application approval email.

ns1.astahost.com and ns2.astahost.com are not working for me. =[ I'm slightly confused about this...for Xisto, do we have to change the nameservers as well? And if so, what do we change it to?

EDIT:
Oh, I think I get it. We change it to ns.computinghost.com now? I thought that Xisto - Web Hosting.com was for the paid hosting version of Xisto...Well, anyways, I've changed it, but so far the domain still doesn't seem to be working. I'll wait a while and check back tomorrow morning.
Edited May 4, 2008 by Arbitrary (see edit history)

[Miles 0]

It's been days and my site is still down, the domain pointing to the old IP address. Due to the nature of my site, which is still working to gain more viewers, I doubt it'll be visited much anymore unless this is resolved soon.

[xboxrulz1405241485 0]

ns1.astahost.com and ns2.astahost.com are not working for me. =[ I'm slightly confused about this...for Xisto, do we have to change the nameservers as well? And if so, what do we change it to?
EDIT:
Oh, I think I get it. We change it to ns.computinghost.com now? I thought that Xisto - Web Hosting.com was for the paid hosting version of Xisto...Well, anyways, I've changed it, but so far the domain still doesn't seem to be working. I'll wait a while and check back tomorrow morning.

no, keep your old ns1.computinghost.com and ns2.computinghost.com intact.

The new change to ns.computinghost.com is for paid customers only.

xboxrulz

[Arbitrary 0]

no, keep your old ns1.computinghost.com and ns2.computinghost.com intact.
The new change to ns.computinghost.com is for paid customers only.

xboxrulz

Well, prior to this I had ns1.astahost.com and ns2.astahost.com, not the Xisto - Web Hosting.com ones. Am I supposed to keep the Xisto nameservers or do I change it to ns1.computinghost.com?

I've tried both combinations and neither seems to be working. =/

[Miles 0]

no, keep your old ns1.computinghost.com and ns2.computinghost.com intact.
The new change to ns.computinghost.com is for paid customers only.

xboxrulz

Now I'm extremely confused. Last time I checked, we had to use Xisto - Web Hosting nameservers no matter whether we were paid or free.

[BuffaloHelp 24]

New name servers for all Xisto members are:

ns.computinghost.com
ns2.computinghost.com

(ns.computinghost.com is not a typo)

OpaQue has decided to consolidate name servers. I believe this announcement was made while back.

***UPDATE*** I hope people read this

If you have add-on domain and still cannot resolve or pings to old IP please submit using Xisto - Support.com support ticket. Live chat can sometimes resolve your issue although there are reports that Live Support team can't so much at this time.

Please read OpaQue Updates About The Server Migration, why and who?

[xboxrulz1405241485 0]

Alright, BuffaloHELP proved me wrong.xboxrulz

[levimage 0]

Hey, my web site has been down for like... I don't really remember. I was just wondering if you can pro rate your credit system. I am also a bit confused about the domain name system.

I am originally setup with Network Solutions for a .com. When I created an account some time back it was on a different credit system. And I believe i used ns.astahost.com for the name server, then I had to change it to ns1.trap17.com. I'm not sure if I was doing it correctly cause the registration and the sign up process had different instructions.

Now I'm reading above about everyone is suppose to be on ns.computinghost.com and ns2.computinghost.com so I made the changes yesterday. So far nothing has happened. When I get in using the https://support.xisto.com/ I see a new cpanel and I guess I can update by page but I can't pull it up -- http://forums.xisto.com/no_longer_exists/

I've tried pinging the following:

64.5.44.113 okay
209.152.167.59 requested time out
ns1.trap17.com (64.69.35.170) requested time out
ns2.trap17.com (208.87.241.124) okay
ns.computinghost.com (67.19.253.52) okay
ns2.computinghost.com (208.87.241.124) okay
ns1.computinghost.com (208.87.241.118) okay

So what do I do? I can call network solutions if I need to make any changes but I don't know what to make. Doe IPv6 have anything to do with it?

[tansqrx 0]

Any update on TLD hosting? My website, ycoderscookbook.com, is still resolving to the old IP.

[BuffaloHelp 24]

If you have PARK or ADD-ON domain with Xisto hosting account please try the following:Disconnect or detach from your hosting accout (unpark or unadd) and then re park or add-on your domain. Be sure that the domain name has proper name servers.You will notice that your www.(yourdomain_name).ext works almost about immediately. But just (yourdomain_name).ext will not. Give it about 24 hours and it should work without a problem.Trap17 moderators and members have been trying this method and it seems to solve the old IP lockdown issue. This is not an official answer from OpaQue and his tech teams but it worked for me.I hope this helps.

[xboxrulz1405241485 0]

According to my website, my configuration file is missing, but it's clearly there! It's in my public_html folder but after the switch it just doesn't work!!

http://forums.xisto.com/no_longer_exists/

xboxrulz

[turbopowerdmaxsteel 0]

I was able to get my TLD working by purchasing managed DNS service and manually setting the IP of the domain to that of the new Gamma server. It stared working in about an hour or so. I had to change the nameservers to from ns.computinghost.com and ns2.computinghost.com to 4 of them provided by my domain registrant. I thought it might cause some problems and I wouldn't be able to get some things working in the CPanel. But its all working fine.