Tony

The server host names do not say hawk host anywhere. It's the IP addresses that could potentially say our name because we are the ones who control them.

All hosting orders are manually verified by sales which works during our business hours. There was a backlog of orders at the start of the day as well which would delay things slightly more.

Well the big thing is if someone knew you were hosting with us then why not just go with us directly? There are still ways to find out we're doing the hosting by checking IP ownership and things like that. It's far more difficult though then giving a user our name servers.

The raid array is once again optimal. As far as other issues we have fixed a few things but other than that everything should be back to normal so we're considering this resolved at this point. If you run into any issues though do not hesitate to make a support ticket.

Innodb databases are now fixed as well. Now we're just waiting on the raid to rebuild then hopefully should be no more issues.

Still working on the innodb databases but we ended up replacing one of the drives in the raid which was reporting medium errors which typically is a sign it's having issues.

mySQL is up besides Innodb databases we're working on getting backups for those.

The one issue we know of that still exists is interment mysql connection issues. We're working hard on figuring out why but we have no ETA at this time.

There appears to be some lingering issues. We're still working on solving them.

We have been unable to recover this partition. We're going to use R1Soft to restore it from a previous restore point. We're going to do this as fast as we can but we estimate it may take several hours for us to complete all of this then hope the machine comes back online.

There are problems with the superblock on the /usr partition. We were attempting to find an alternative via console which is not exactly easy. We've switched over to the recovery operating system which is much more responsive when we're not directly at the machine. So the machine is actually responding to pings but we're still working on finding a suitable superblock to recover the file system.

At this time PHP 5.3 is not even supported by cPanel which means lots of portions for it would not even work properly. So until they support it we cannot really properly support it. Sure we could compile it in but it would not work like our PHP 5.2 installs thus confusing users. It's really not meant for prime time yet. Lots of small issues and most systems do not support it. That's PHP scripts themselves as well as control panels, installers, various modules within php as well as some sapi's not even being tested well on it yet.

Well these scripts have costs of like $24/yr. So we're talking about such a small amount it's like saying each customer costs an extra $0.01/yr. For not having it installed it's more work for us and more costly to not have all the same software on all machines. As far as the other suggestion about discounts for less technical help. The problem with that concept is people who require less help are who partly pay for the support for others. We could not offer the prices if suddenly clients opted to pay less and get no support. It's the same idea about space and bandwidth where users using only 100MB of space help pay for people using a full allocation. Plus I imagine most users who would opt for such a service would end up asking for support anyways. Most users say they do not need help then make tickets anyways.

You'd need to run your own DNS then run your own round robin DNS. This would just essentially send random users to random server. You'd be responsible for syncing the data and syncing the database. This is really not something you can do in a shared hosting environment. People who load balance or do things like this have their own servers. So they can setup mysql replication use load balancers, use anycast ip's and such.

Our discounts are already really deep for long term commitments and at our prices it's not something we can reasonably do while making money. A $5.95/month plan people would expect a 3 year version to be for say $2/month. It's just not something we could afford to do. The reason some hosts offer it are the cost of entry. $9.95/month for them vs $5.95/month for us. We already offer a plan lower than their 3 year commit level.

Using a dedicated IP for SEO to begin with is silly. But having the IP when you do http://ip/ go to a add-on domain is not going to make any difference. Does anyone view the site via ip? The obvious answer is no it's indexed by it's actual domain so you should be fine.

It's based off of the httpd.conf file and it's going to break every time you add a domain. So it's typically not something we're going to change as anytime you manipulate domains on your account it'll break what you desire anyways.

This has been completed.

This has been completed.

This has been completed.

This has been completed.

This has been completed.

This has been completed.

This has been completed.

This has been completed.