Love it or hate it (or possibly overwhelming indifference) it is around and here to stay. I’ve used many different services and while I am sure there are many horror stories (no matter what hosting company you go with) I’ve only had several issues with them over the past few years.
I’ve got several accounts with them, have gotten other associates of mine to use them as well, and run more than 40 different websites across the strata. Once in a while, something particularly odd or annoying happens.
I only use them for shared hosting, for more serious en-devours I use the cloud (particularly, AWS) as I’m sure I’ve expressed before.
Like many hosting services they go down sometimes. Sometimes its only for 20 minutes because some fool who ran a bad runaway script with a forever loop, sometimes its for a few hours because their daemons became unstable. Whatever, downtimes are not a big issue, they happen rarely (perhaps a few times a year, sometimes a couple times within a single week, and other times not for an 8 or 10 month stretch).
I don’t have a problem with it, in fact I fully understand how that kind of thing can happen.
What drives me crazy is when strange anomalies crop up. For example, sometimes their DNS zone files will get “reset”. You’ll notice this in particular when you have multiple domains pointing at different IP addresses.
When this happens, the wrong IP addresses get reported to some DNS servers temporarily and dish you out an IP address that, while it belongs to Bluehost, is not the correct IP address for your domain.
What happens then? Lets say your primary domain is server.com and you have an addon domain called server2.com. Your IP address for server.com is 188.8.131.52 and for server2.com its IP address is 184.108.40.206. Well one day you try going to server2.com and instead get sent to 220.127.116.11 (and when you check your DNS zone editor, you’ll see the address has been set to 18.104.22.168) then you see the infamous Bluehost message View Temporary Site for about two nanoseconds and then you get sent to server2.server.com
What do you need to do?
Well, you need to flush your DNS cache. I also recommend you stick to using Google’s public DNS server, but that’s up to you (22.214.171.124 and also 126.96.36.199 are available)