Portal Home > Knowledgebase > Industry Announcements > Web Hosting Main Forums > Providers and Network Outages and Updates > Again- My Innohosting Dedicated Ip Clients Have Been Down for over 24 Hour
Again- My Innohosting Dedicated Ip Clients Have Been Down for over 24 Hour
| Posted by Louis Prima, 12-13-2011, 05:23 PM |
I posted here a few days ago that my Innohosting reseller account had been down 11 hours. Well, now, again, all of my clients with dedicated IPS have been down for over 24 hours.
Inno said that due to the previous server failure, everything was being moved to a new server and all of the dedicated IPs would have to be reassigned. Well my dedicated IP clients, as well as my own site has been down for over 24 hours, with the default Cpanel install page showing.
I filed a support ticket 10 hours ago and never received a response about potential downtime, or when the sites would be back up.
So, I'm not a server admin. Is this considered acceptable, guys? 24 hours downtime for ALL of my sites with dedicated IPs? Opinions? |
| Posted by jcarney1987, 12-13-2011, 05:47 PM |
|
This is why I would use custom built servers. Not saying that they don't but when you normally run a host you at least have raid 1 giving redundancy keeping your data intact. So if the server started to fail swap out what is needed and have you back online in a timely manner. But if the problem was at the harddrives and 1 harddrive become corrupted this would cause more downtime since the raid will record corrupted data. Still imo 12 hours complete downtime is to much. |
| Posted by PremiumHost, 12-13-2011, 08:47 PM |
If you use Innohosting dns, ip change should be updated automatically.
DNS change may take 12-24 hours to propagate on the internet.
If you use third party dns, you need to confirm new ip address and configure domain pointing to the new ip. |
| Posted by Louis Prima, 12-14-2011, 12:52 AM |
Ah, Premium is right. The first thing I should have done is perform a check of what IP the site is being sent to through another DNS look-up. Apparently my ISP is a bit slow to accept and update IP address changes.
The longer you do this stuff, the more you forget, I guess  . Thanks for the reminder Premium.
Unfortunately, it seems that many of my clients ISPs are just as slow to update their servers. |
| Posted by Yujin, 12-14-2011, 01:07 AM |
Quote:
|
Originally Posted by PremiumHost
If you use Innohosting dns, ip change should be updated automatically.
DNS change may take 12-24 hours to propagate on the internet.
If you use third party dns, you need to confirm new ip address and configure domain pointing to the new ip.
|
This is a myth nowadays my friend. I can change any kind of IP and in 5-15 minutes this is propagated. Do not forget that you can always use a different proxy website if you suspect that the only problem is propagation. |
| Posted by Yujin, 12-14-2011, 01:10 AM |
|
In my opinion 24 hours of downtime is too much and worse you have no feedback for 10 hours with your support ticket. InnoHosting price is not a cheap price but they might give you some SLA credit. |
| Posted by Steven, 12-14-2011, 01:10 AM |
Quote:
|
Originally Posted by Yujin
This is a myth nowadays my friend. I can change any kind of IP and in 5-15 minutes this is propagated. Do not forget that you can always use a different proxy website if you suspect that the only problem is propagation.
|
Not fully a myth. I have not really encounter a USA isp that took more than 5-15 minutes, but we regularly experience issues with isps in other parts of the world taking 12 to 48 hours in some cases. |
| Posted by Yujin, 12-14-2011, 01:20 AM |
Quote:
|
Originally Posted by Steven
Not fully a myth. I have not really encounter a USA isp that took more than 5-15 minutes, but we regularly experience issues with isps in other parts of the world taking 12 to 48 hours in some cases.
|
If your concern is verifying if your site is up and running then propagation is not a concern so 12 to 48 hours is a myth. However, if you are expecting your site to be immediately available in your ISP server then yes you might wait some hours. Unless, you can request in your ISP to flush their DNS (aside from your dekstop ipconfig /flushdns) or you are in a dynamic IP where you can simply turn-off your modem and get a new one. |
| Posted by Louis Prima, 12-14-2011, 02:20 AM |
as Steven mentioned, I don't really think this is quite a "myth" Yujin. I checked one of the sites through an online site checker and it came up fine. It just doesn't come up when viewed using my ISP's nameservers. I'm in Norway, btw.
The bad thing is- that it's also not showing up for some of my clients in the US. So I think some ISPs are not on the ball about keeping their DNS updated.
So yeah, the site is up and is pointed at the correct IP. However, this doesn't really help if my clients ISP is routing the site to an IP from 24-48 hours ago, which in this case, they seem to be. I think when most of us refer to propagation, we are referring to the amount of time it takes for the various ISPs around the world to update their DNS. |
| Posted by Yujin, 12-14-2011, 02:29 AM |
Quote:
|
Originally Posted by Louis Prima
as Steven mentioned, I don't really think this is quite a "myth" Yujin. I checked one of the sites through an online site checker and it came up fine. It just doesn't come up when viewed using my ISP's nameservers. I'm in Norway, btw.
The bad thing is- that it's also not showing up for some of my clients in the US. So I think some ISPs are on the ball about keeping their DNS updated.
So yeah, the site is up and is pointed at the correct IP. However, this doesn't really help if my clients ISP is routing the site to an IP from 24-48 hours ago, which in this case, they seem to be. I think when most of us refer to propagation, we are referring to the amount of time it takes for the various ISPs around the world to update their DNS.
|
Unfortunate, to both of your places as your client has limited option or workaround on this type of incident. |
| Posted by Louis Prima, 12-14-2011, 02:37 AM |
Very true. And I'd hate to try to instruct some of my clients with very rudimentary knowledge of router settings how to change their DNS servers to a new, public set like Verizon's(which I believe are still open to the public) or Google's new DNS service.
And as for the Google service, I just don't like the idea of Google handling DNS. Maybe I'm just being paranoid, but Google seems intent on knowing absolutely EVERY site that people visit. |
| Posted by IH-Rameen, 12-14-2011, 07:22 PM |
Quote:
|
Originally Posted by Louis Prima
I posted here a few days ago that my Innohosting reseller account had been down 11 hours. Well, now, again, all of my clients with dedicated IPS have been down for over 24 hours.
Inno said that due to the previous server failure, everything was being moved to a new server and all of the dedicated IPs would have to be reassigned. Well my dedicated IP clients, as well as my own site has been down for over 24 hours, with the default Cpanel install page showing.
I filed a support ticket 10 hours ago and never received a response about potential downtime, or when the sites would be back up.
So, I'm not a server admin. Is this considered acceptable, guys? 24 hours downtime for ALL of my sites with dedicated IPs? Opinions?
|
Hi Louis,
As others mentioned, it wasn't a server downtime or anything of that sort. It was just IP propagation which can take some time depending on your ISP. Usually, sites propagate really quickly, but some ISP's take longer than others. This was in follow up to a server migration and we did make an announcement regarding the migration.
If you're ever unhappy with something, you can just send an email to me or PM me here, I'd be happy to look into it. I don't think many here will be able to assist you with any issues you have, but we're more than happy to look into any problems you encounter. |
| Posted by IH-Rameen, 12-14-2011, 09:57 PM |
Quote:
|
Originally Posted by Louis Prima
I filed a support ticket 10 hours ago and never received a response about potential downtime, or when the sites would be back up.
|
I checked your support ticket:
Ticket Opened: 13 Dec 2011 10:32 AM
First Response: 13 Dec 2011 11:01 AM
Additional Response/Conclusion: 13 Dec 2011 11:16 AM
So I'm not sure why you have said we didn't respond in over 10hrs? We answered you and got you back on track in less than 1 hour? That was 10 hrs prior to you making this post? |
Add to Favourites 
Print this Article
Also Read
gnax.net down? (Views: 1005)
Shared Hosting
Shared Hosting
