Getting your domain and hosting in place

Getting your domain and hosting in place

You need three things lined up to start building: a domain name, a hosting account you can log in to, and DNS that points the domain at the hosting. With Hostworld, access to cPanel or your VPS appears after the first invoice is paid in our client area. You can start work the same afternoon by previewing the site on your computer before you change nameservers.

This picks up from you having chosen a site name and the platform you plan to use. If you have not decided between cPanel hosting and a VPS, you can still follow along. The order is the same.

Before you start

• Have your domain name chosen and access to its registrar login. You will need this to change nameservers later.
• Decide where you will build: our cPanel web hosting for a typical single site, or a VPS if you need full server control. Our UK option is sold as London VPS and runs in our Maidenhead, Berkshire data centre. See London VPS.
• Plan your email. If your mail is with Microsoft 365 or another provider, you must recreate their MX and related DNS at the new DNS host before you switch nameservers. Skipping this will interrupt mail delivery.
• Check if DNSSEC is enabled at your registrar. If there is a DS record and you move to nameservers that do not use those keys, the domain can stop resolving. You will remove or update the DS record before changing nameservers.
• Know how long each bit takes:
  • Hosting and VPS access appear after you pay the first invoice in our client area. WHMCS provisions based on the product’s settings when payment clears. If a fraud check flags the order, provisioning will wait.
  • You can build immediately using a hosts file preview. No DNS change needed.
  • Changing nameservers: the registry publishes quickly. Many registrars take hours to process, and resolvers cache. Expect up to 24 hours before everyone sees the new DNS.
  • AutoSSL: usually minutes after the domain resolves to the server. It can take longer, up to 48 hours in some cases.
• Backups and reversals:
  • Do not terminate a cPanel account to “start over”. Termination permanently deletes files, databases and DNS zones.
  • Do not rebuild a VPS to “clean it up” during setup. Virtualizor’s Re-install OS wipes all data. Only do this if you have a verified backup.

Step 1: Choose your Hostworld plan and place the order

If you are running one site for your own business, start with our cPanel hosting. If you need root access or a custom stack, choose a VPS. Our UK VPS offers London routing and sits in Maidenhead, Berkshire. See London VPS. We also host in New York for US workloads.

Order through our client area at portal.hostworld.uk. WHMCS provisions products after the initial invoice is paid, depending on the product’s module settings. That is when cPanel or your VPS becomes available.

Undo: Ordered the wrong plan? Do not terminate the account or rebuild the VPS. Open a support ticket and we will help you move to the right product without losing work.

Step 2: Pay the first invoice and log in to your control panel

Once the invoice shows as paid in our client area, your service will be created if the product is set for automatic provisioning. From the service page, use the single sign-on link to open cPanel or WHM without a separate password. For VPS customers, you will see Virtualizor controls to start, stop and access the console.

If you have not logged in to your Hostworld account before, follow our how-to: Accessing your Hostworld account for the first time.

Undo: If you cannot see the SSO button or your service is “Pending”, check the invoice is fully paid in WHMCS. If it is paid and still pending, open a support ticket.

Step 3: Start building today with a private hosts file preview

You do not have to point your domain at us to begin work. cPanel documents a safe method: add a hosts file entry on your own computer that maps your domain to your Hostworld server’s IP. Only your machine uses this mapping. The public internet is not affected.

What the hosts entry does: it overrides DNS for that domain on your computer. Your browser connects straight to the IP you specify. This lets you install and test in cPanel while customers still see the old site elsewhere.

You will need your service IP. Use the IP shown in your control panel. If you are unsure which IP to use, open a support ticket and we will confirm it.

Windows

1. Run Notepad as Administrator.
2. Open the file C:\Windows\System32\drivers\etc\hosts.
3. Add a line with your server IP followed by your domain and any subdomain you will test.

123.123.123.123 example.com www.example.com

Save the file. Your computer now resolves example.com to 123.123.123.123.

macOS

1. Open Terminal.
2. Edit /etc/hosts with your preferred editor using elevated privileges.
3. Add the same style of line as above, then save.

123.123.123.123 example.com www.example.com

Linux

1. Edit /etc/hosts as root with your preferred editor.
2. Add the same style of line and save.

123.123.123.123 example.com www.example.com

Undo: When you are ready to go live, remove the lines you added from the hosts file. If you leave them in place you will keep seeing your own server even if the rest of the world is still on the old one.

Step 4: Upload your site into public_html in cPanel

Log in to cPanel from our client area and open File Manager. The public web root for the primary domain is typically public_html. That is where the web server serves files for your domain. You can upload, extract zip archives and edit files in File Manager.

If you are installing a CMS, follow its installer in your browser using the hosts file preview. If you are migrating an existing site, upload the files into public_html and import any required databases.

Undo: Before you overwrite anything, take a copy. You can download the existing public_html as a zip first. If you need to roll back, replace the new files with your saved copy.

Step 5: Decide where DNS will live and prepare it before the switch

Decide whether you will point your domain at Hostworld’s nameservers or keep DNS elsewhere.

• Point to Hostworld nameservers. We host the DNS zone. Use these exact nameservers at your registrar:
  • ns1.serverworld.uk
  • ns2.serverworld.uk
  • ns3.serverworld.uk
  • ns4.serverworld.uk
  Before you change nameservers, make sure the DNS zone on our side contains everything you need. That includes A and AAAA records for the site and the correct MX record for your email provider.
• Keep DNS elsewhere. Leave nameservers as they are and create A and AAAA records at your DNS host that point to your Hostworld server IP. If you use this route, AutoSSL must still be able to validate over HTTP. The domain must resolve to your Hostworld server for validation to pass.

Why do this now: DNS changes do not take effect everywhere at the same moment. Resolvers cache records for their time to live. Even with a low TTL, local caching means a change can still feel slow to settle. Preparing records ahead of time avoids outages.

Email warning: MX records decide where mail is delivered. If you switch nameservers without recreating your mailbox provider’s MX and any required SPF, DKIM and DMARC at the new DNS host, mail can bounce or vanish until fixed.

Undo: If something looks wrong after the switch, you can change nameservers back to the previous set at your registrar. Caches will still exist. Expect some users to keep seeing the broken path until their cache expires.

Step 6: Change nameservers at your registrar to Hostworld

When you are ready for the public cut-over, log in to your registrar and change nameservers to:

• ns1.serverworld.uk
• ns2.serverworld.uk
• ns3.serverworld.uk
• ns4.serverworld.uk

If DNSSEC is enabled at the registrar and you have a DS record in place, remove or update it before you switch to avoid “pending” states or resolution failures. Stale DS records are a common reason domains do not delegate to new nameservers.

Timing to expect:

• The registry publishes updates quickly once the registrar submits them. The slower parts are the registrar’s processing queue and resolver caches.
• Some registrars take up to 24 hours to process a nameserver change before the update starts to appear.

Undo: If the switch exposes a misconfiguration, change back to the previous nameservers in your registrar’s control panel. Remember that resolver caches take time to expire. Use your hosts file for emergency access while you fix DNS.

Step 7: Let AutoSSL issue your HTTPS certificate

When your domain resolves to your Hostworld server and serves pages over HTTP, cPanel’s AutoSSL system will request a certificate for you. The default provider can issue in minutes, but it can take longer, up to 48 hours in some cases. AutoSSL checks in about every five minutes and will abandon a request after around a day if it cannot validate.

If HTTP validation fails, it is usually because the domain does not resolve to the server yet or the validation file cannot be reached. Fix DNS so the domain points to your hosting service and ensure nothing blocks public access to the DCV path.

Undo: There is no revert for a failed request. Keep the site reachable over HTTP, correct DNS, and allow AutoSSL to retry. If you need help interpreting a failure, open a support ticket.

Step 8: Test live resolution and remove your hosts file entries

Test your domain on a device that never had a hosts file entry. Check both the apex domain and the www host. Confirm the page you see matches what you uploaded to public_html. Then remove the hosts file lines from your workstation so you see what the public sees.

Undo: If some staff still see the old site because of caching, you can temporarily keep a hosts file entry on their machines that points at the new IP while caches expire.

Step 9: If you are using a VPS, keep rebuilds off the table during setup

VPS customers manage their server in Virtualizor from our client area. You can start, stop, reboot, reinstall the OS and open a VNC console. Do not use Re-install OS as part of troubleshooting during your build. Virtualizor’s own documentation is clear: a reinstall creates a fresh VPS without any data. You will lose the site you were building.

Undo: A rebuild cannot be undone. The only way back is a working backup you can restore into the fresh system. If you think you need to rebuild, stop and open a support ticket for advice first.

Step 10: Keep a rollback path that does not delete things

If you need to pause, do not terminate a cPanel account. Termination permanently removes files, databases and DNS zones. If you need to disable public access briefly, use maintenance modes in your application or remove the nameserver change at the registrar while you fix DNS. Keep copies of any files you replace in public_html.

Undo: To reverse a bad deployment, restore your saved files in File Manager or switch nameservers back while you correct the configuration.

What next

You now have hosting access, a way to build privately, and a cut-over plan with the timing in view. If you are building on a VPS and want to tune the OS or stack, see our VPS guides. If you need to revisit the order and login step, follow Accessing your Hostworld account for the first time.

If you want UK-located compute with root control for your project, compare plans on London VPS. If anything here does not line up with what you see in your account, open a support ticket and we will check your specific service.