Delegation & Control
Shared vs VPS hosting — A VPS does not buy you speed. It buys you the zone.
Somebody has told you to upgrade, and the advice was all about CPU and memory — nobody mentioned that root access also makes the DNS, the mail records and the sending reputation of your name your own problem from that morning onwards.
The short answer
Stay on shared hosting until a concrete requirement announces itself — root access, a custom daemon, guaranteed resources — then move to a KVM VPS with realistic expectations about the admin work, and treat the DNS and mail records as the first task of the move rather than the last.
The rest of this page is about the handover nobody itemises: which records change owner, which ones must not, and the sixty-day rule that catches people who move host and registrar in the same week.
By the Hosting & Domains team · Reviewed 24 August 2026
Free
Transfer of the site in
24/7
People on the desk
Daily
Copies taken
$0
Set-up charge
This brief is for owners of growing sites who keep being told to buy a VPS and suspect it is not true yet. The usual comparison lists cores and gigabytes. This one lists records, because that is what actually moves.
A shared account hands you a name and quietly runs everything under it. Root access hands you the same name and stops running anything. That is the whole trade, stated once and without drama.
Who holds the zone in each arrangement
On a shared plan the name delegates to our nameservers, the zone is served for you, and the only decision left is which record to edit. Certificate reissues, mail routing and the day-to-day housekeeping happen without a ticket.
On a VPS the delegation is yours to point wherever you like — at our nameservers, at your own, or at a third-party DNS provider entirely. That freedom is real and it is also a responsibility: nothing checks your work, and a zone with one bad character in it takes the name off the internet just as thoroughly as an expired registration.
The mail records are the real migration
Files and databases copy across in an afternoon. What strands people is mail, because mail depends on four record types and a reputation, none of which travel in a tarball.
MX decides who receives. SPF decides who may send. DKIM proves the message was not altered on the way. DMARC tells the receiving side what to do when the first two disagree. Move the server and forget any one of them and you have a name that looks fine in a browser while its invoices land in spam.
There is a sequencing rule worth obeying: drop the TTL on the mail records the day before, cut over, verify from an outside network, then put the TTL back. Doing it in that order turns a nervous evening into ten minutes of work.
The sixty-day rule people meet at the worst moment
Upgrades and registrar changes tend to occur to people in the same week, and the two do not mix well. A name that was registered or transferred inside the last sixty days is frozen against another transfer, and so, at many registries, is one whose registrant details have just been rewritten.
The fix is sequencing rather than paperwork. Move the hosting first and leave the registration where it is, or move the registration first and let the freeze run down while you build the server. Attempting both at once is how a planned migration turns into a two-month wait.
Where we would send you, honestly
Staying on shared hosting until a concrete requirement announces itself — root access, a custom daemon, guaranteed resources — then moving to a KVM VPS with realistic expectations about the admin work.
In our range that means the Turbo plan — SSL, the move and mail already inside, renewal charged at the order rate, and an upgrade path so this decision never has to be made twice.
Support means a person at any hour, and the remit covers the awkward practical questions other hosts hand straight back — including the DNS ones, which is where most of them arrive.
Run these checks on us before you order. Ask who serves the zone, whether you can edit every record type yourself, what the renewal figure is in writing, and how quickly an auth code is issued if you ever want to leave. Four questions, four answers, no hedging.
The company is Azaanex Inc., federally incorporated in Canada, and on the public register where you can read it. That is deliberately checkable rather than reassuring.
Then buy the fortnight. Bring a live site in at no charge, work it properly, and let the money-back window carry the risk while ordinary use answers what no comparison table can.
Our interest here, stated plainly
We register names and we sell hosting, so read this as a supplier's argument rather than a neutral verdict. What we will not do is fake the neutrality — no paid placements, no referral cheques, no leaderboard for hire.
The rate you register at is the rate you renew at, so year two costs precisely what year one did — nothing lying in wait on the invoice.
- Delegation, zone and registrar all stated openly
- Renewal figures published, not footnoted
- An auth code issued on request, no argument
- Refund terms with no small print
Why Hosting & Domains
Standard on every plan
The delegation is yours to point
Use our nameservers, your own, or a third-party DNS provider — the choice sits with the registrant and stays there.
Upgrades without touching the zone
Shared, VPS and dedicated on one platform, so a plan change is an account setting rather than a nameserver event.
Mail records looked after on shared plans
MX, SPF and DKIM configured and maintained for you until the day you decide to take them over.
One rate, published in the open
What you order at is what you renew at — for the hosting and for the registration alike.
The verdict, turned into an order
The Turbo plan is this page's conclusion in product form — one rate, essentials inside, upgradeable in place.
A refund without an argument
If we are not the fit, leaving is one request rather than a negotiation — which is exactly why we invite the test.
Quick Start
Order placed to site online
- 1
List the records before you list the specs
Write out the zone as it stands today — website, mail, verification strings, anything a third party gave you. Half of the people who ask about upgrading discover the answer is a caching change instead.
- 2
Lower the TTLs the day before
Bring them down to minutes, make the move, confirm from an outside network, then put them back. Cache is the only reason a correct change appears to fail.
- 3
Do the host and the registrar in separate weeks
Sixty-day freezes exist and they do not negotiate. Sequencing the two jobs costs you nothing; combining them can cost two months.
Built In
Fitted to every plan
- Nameserver delegation you can repoint whenever you choose
- Upgrades applied in place, with no migration when you change plan
- A daily copy, with restores you run yourself from the panel
- Staging copies for trying a change before it goes live
- 99.9% uptime as the target, watched around the clock
- Spam and virus screening on every mailbox by default
- A renewal figure identical to the one you registered at
- Free SSL on every plan, reissued before the old one lapses
- NVMe SSD storage on every tier, not only the dear ones
- cPanel, which is what most of the industry already runs
Frequently Asked
Questions we field again and again
If I take a VPS, do I have to run my own nameservers?
No. Delegation and hosting are separate decisions. Plenty of people take root access for the application and leave the name pointed at managed nameservers, which keeps the flexibility they wanted without inheriting a zone to babysit.
What breaks first when a site changes server?
Mail, almost every time. The website is one A record and it is obvious when it is wrong. Mail is MX plus SPF plus DKIM plus DMARC, and a mistake there is silent for hours — the site loads, the invoices simply stop arriving.
Can I move the hosting and keep the name where it is?
Yes, and it is often the sensible order. Point the nameservers or the individual records at the new server and leave the registration untouched. The transfer, if you want one at all, can follow weeks later.
How long should I expect a nameserver change to take?
The registry updates within minutes. Resolvers around the world catch up over the following one to forty-eight hours depending on the TTLs set beforehand, and in practice most of your traffic is on the new answer inside a few hours.
Keep reading
VPS Hosting
KVM virtual servers with root access, DDoS filtering and delegation you point yourself.
Domain Names
Search, register and transfer names — with year one free alongside annual hosting.
Changing provider? Work through this checklist beforehand.
A straightforward running order for a migration your visitors never spot: which files travel first, how to bring the mail across without dropping a single message, the right moment to repoint DNS, and the two errors that sit behind almost every outage we get called in to fix.
Hold the name, then choose the server.
Registration, delegation and hosting on one account — and moving up the range never touches your records.
View VPS Hosting plans