Hi AstaHost hosting members.

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

Xistosupport.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 AstaHost 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:



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

for Windows 2000

for Windows ME or 98


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:



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.

 

 

 

Reply

Thanks for the info.
Anothen way of reaching the cpanel was with the link http://astahost.com/manage/, 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.

Reply

Do the following nameservers work for Astahost?

ns1.Astahost.com
ns2.Astahost.com

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

Reply

ns1.astahost.com and ns2.astahost.com are not working for me. =[ I'm slightly confused about this...for Astahost, 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 computinghost.com was for the paid hosting version of Astahost...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.

Reply

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.

Reply

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

Reply

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

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

Reply

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

Reply

New name servers for all AstaHost 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 xistosupport.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?

Reply

Alright, BuffaloHELP proved me wrong.

xboxrulz

Reply