About 3 months ago we raced into the 21st century by letting you choose your own account password.
Following on from this, you can now choose the password for each of your web hosting accounts. Previously you could only reset a hosting account password without any choice of password.
Either choose your own password:
Or have a strong password automatically chosen for you:
The option to choose your own account password was released live just a few minutes ago.
Within the next few weeks we'll roll out a similar option for choosing the passwords for your hosting accounts.
Enjoy!
You can't currently choose your own password for your Hosting Reborn account. It might sound a bit ridiculous, but we're only looking after your interests.
Your account should be safe and is only as safe as the password. We decided from day one that if we can't let you choose your own password and whilst ensuring it's suitably secure, we'll just stick to generating a secure password for you. Inconvenient but secure.
We're close to releasing the option to let you choose your own password. It's taken a long time and we've put a lot of effort into investigating what it means for a password to be secure and how to check if what you choose is going to do the trick.
Here's what the interesting part of the password reset form looks like on our development system:
You get realtime feedback on the strength of your password as you type, as well as the option of letting us generate a secure password for you.
Hopefully we'll see this go live in the next couple of weeks, along with a selection of behind-the-scenes updates to make it easier for us to make things easier for you in a way that you'll never actually notice.
Prior to the recent server move we were using ns1.webignition.net and ns2.webignition.net as DNS nameservers.
We moved to using ns1 to ns4.hostingreborn.com, which required everyone using ns1 and ns2.webignition.net to make changes to their domain names' records.
Whilst a bit of a hassle, I thought everyone could cope - afterall, if someone can manage to set their domain's nameservers to ns1 and ns2.webignition.net, they'll be able to cope with changing them to ns1 to ns4.hostingreborn.com.
Well, some people can't, some people haven't and perhaps some people will forget.
So we've now set ns1.webignition.net to be an alias of ns1.hostingreborn.com and ns2.webignition.net to be an alias of ns2.hostingreborn.com.
So if you now can't or won't change your domain's nameserver records, you no longer need to.
The server move announced toward the end of last month is now fully complete.
All hosting accounts have been moved, with email and database requests being transferred on from the old servers to the new servers to avoid anything getting lost.
We now just need everyone to ensure all domain name records are appropriately updated to prevent websites and email breaking when the old servers are finally decommissioned in about a month from now.
If your domain names' nameserver records are set to ns1.webignition.net and ns2.webignition.net these must be changed to:
If you manage your own DNS records, you must change occurrences of 78.31.104.54 to 178.63.85.207.
We'll keep an eye on traffic reaching the old servers and get in touch with anyone who may not have yet made the appropriate changes.