[Solved] Dns Issues

[Shinryuu]

Could an admin check on Charlie/Cody, Heliohost.org's been down for about an hour or so.

[maryadavies]

I've noticed that. Also Johnny's control panel is down. And I just am working on moving here since I'm losing my old host (a friend was hosting my page).

[Piotr GRD]

Actually the server is fine.

But the ns1./ns2.heliohost.org nameservers doesn't work properly and doesn't return any records for the heliohost.org domain name (maybe for some other domain names, too).

[Shinryuu]

Oh, hmm..

 

I assumed it was Cody and maybe Charlie being down at first, after marya's post I was sure it was Charlie since my site on Stevie was still up, thanks for the heads up Piotr.

[maryadavies]

Main page is back up but I still can't log in..My page is up, I can get into it via ftp, but I can't login to it via web panel. (My page never went down though.)

[Krydos]

I still can't log in.

Have you read the latest news?

Heliohost is currently experiencing a DNS issue on our main domain http://heliohost.org/ and http://johnny.heliohost.org/ Attempting to access these domains by name will most likely result in a server not found error for most people. We are aware of this issue and are working to resolve it. All user DNS data seems to be intact, and our forums http://helionet.org/ are working fine.

 

If your account is located on johnny you can reach your cPanel by using this link http://64.62.211.131:2082/ since the server is online and fully functional. We apologize for any inconvenience this unexpected downtime has caused you.

[maryadavies]

Thank you Krydos and glad to know what's wrong. Hopefully it'll be fixed soon.

[GLaDOS]

Hey my friend's ip is being blocked by heliohost I decided to try and get his ip unblocked by asking nicely is ip is 90.206.199.127 thank you.

[Shinryuu]

Might want to edit out the actual IP and send that via PM to one of the admins, not sure your friend would like every nosy fellow on the internet doing a port scan on his IP.

[Krydos]

That IP address is not blocked on any of the servers. What makes you think it is?

[Ice IT Support]

Your A record is set to the IP 64.62.211.113 (ns2.heliohost.org). We recommend setting your NS records to ns1.heliohost.org and ns2.heliohost.org. If you prefer to use A records, set it to the IP of your server, which can be found in the left-hand column of cPanel.

[Ice IT Support]

Moved gourav's post to new topic, it is not related to this thread.

http://www.helionet.org/index/topic/14211-solved-able-to-login-cpanel-but-website-is-in-accessable/

[Shinryuu]

I've gone ahead and closed it since the mystery's been solved.

[stgeorge]

Cannot access cPanel

Sites are Down

FTP Down

 

Account

xxxxx.heliohost.org

(removed, encourages defacing)

 

Monitor Shows no Interruption to service over last 24 hours.

 

Google Reports:

Googlebot can't access your site

 

Over the last 24 hours, Googlebot encountered 4 errors while attempting to retrieve DNS information for your site. The overall error rate for DNS queries for your site is 57.1%.

 

You can see more details about these errors in Webmaster Tools.

Recommended action

If the site error rate is 100%:

Use a WHOIS tool to verify that http://xxxxxxxxxxxxx.co.uk/ has a proper whois record and that nameservers are configured for the site. If not, contact your domain registrar to update your whois records.

Using a DNS lookup tool, verify that the nameserver's name can be resolved to an IP address. If not, either update your whois record to contain an IP address for your nameserver, or update the DNS records for nameserver.

Using a DNS lookup tool, verify that http://xxxxxxxxxxxxx.co.uk/ can be resolved to an IP address. If it can't, update the DNS record for http://xxxxxxxxxxxxx.co.uk/ on your nameserver.

If the site error rate is less than 100%:

The most likely explanation is that your nameserver is overloaded. Contact your hosting provider and discuss the configuration of your DNS server and the possibility of allocating more resources to your DNS service.

If your site redirects to another hostname, another possible explanation is that a URL on your site is redirecting to a hostname that has a DNS problem. Consider checking the links to which your site redirects and make sure that the sites in your redirect links don't have any DNS issues.

 

After you think you've fixed the problem, use Fetch as Google to verify that Googlebot can properly access your site.

 

Learn more in our Help Center.

 

Also HostTracker has not reported the sites back up since the last downtime notification, (below), which means if they do come back up it is not for long.

HostTracker Notifier &--#60;noreply-www@host-tracker.com&--#62; 4 December 2012 19:53

 

Sites are down

 

Error was detected at 2012-12-04 20:03:23:

 

Amsterdam, Netherlands - HostNotFound (11001)

Noida, India - HostNotFound (11001)

Istanbul, Turkey - NoData (11004)

Amsterdam, Netherlands - Fail

San Jose, CA, USA - Fail

Orlando, FL, USA - Fail

 

All in all the Sites have been as good as down for over 24 hours.

 

If this cannot be fixed can someone let us know so Sites can be moved to other Servers as there seems to be false reports as to Status and the Problem marked as Solved on other Threads and Posts when this is obviously not the Case.

 

EDIT

At the moment the service has resumed, but I would not mark this as solved as it seems that over the last 24 hours the service has been as good as down on Stevie.

 

My Stats show just 40% of the normal hits expected, which implies that this is an ongoing problem.

 

Anyone have any concrete information as to what is going on?

 

I ask, as I have been getting info that stevie is spending about 1 hour a day down over the past 2 weeks, normally in bursts of about 5 to 10 minutes every hour or two.

 

EDIT

Down Again

[toxicious]

I can confirm this problem aswell, haven't been able to access my site today. I've never trusted the uptime check here on Heliohost anyway.

But yeah, hoping that this problem can be solved so we can enjoy this wonderful hosting again