Skip to main content

Walkthrough · Beginner · 10 minutes plus propagation

How to Point a Domain to Your Hosting

How to connect a domain registered anywhere to the hosting account built to serve it, without the guessing — the steps in order, the snag ahead of time, and the tip our support team repeats daily.

The short answer

One line covers it: connect a domain registered anywhere to the hosting account built to serve it — a beginner-level job of roughly 10 minutes plus propagation.

Below is the full run of steps, the error most people trip over, and the short cut worth remembering. On Hosting & Domains plans several steps are already automated away — the guide marks each one.

By the Hosting & Domains team · Reviewed 18 August 2026

Beginner

Skill rating

Quick

Time budget

5

Steps in total

24/7

Support on call

No prior knowledge assumed — a hosting account, a browser and 10 minutes plus propagation of attention is the whole entry requirement. Every instruction runs on our platform exactly as printed, and carries over to any standard cPanel host.

First rule: read the snag section before you start, not afterwards. It was distilled from the tickets of everyone who tried the other order.

How the work divides up

Set out end to end, the route is: copy the nameserver pair, sign in wherever the name is registered, replace the whole pair, save it and let it spread and load the site and check the certificate.

No part of this needs code or a terminal unless the guide says so plainly — and where it does, the exact commands are printed. The step-by-step is below, with the surrounding sections supplying the context that makes it hold.

Where it comes off, and how to stay on

Editing A records at the old provider while delegation still points at it. Nameservers decide who is even asked the question, so they move first; otherwise the records you carefully edited never get queried.

It earns a section of its own because it is no obscure edge case — it is the single commonest reason this task reaches a support queue. Knowing it in advance turns the whole job from risky into routine.

The support desk's own short cut

Lower the domain's TTL the day before a planned switch. Everything after that takes minutes instead of hours, which turns migration night from a vigil into a short job.

A minute spent now repays itself every time this job comes round again — and like almost every hosting job, come round it will.

What a Hosting & Domains plan spares you

Some steps in this guide exist only because hosting traditionally forced them on you. Here the SSL issues itself, the copy is taken daily without being asked, and one-click installers remove the manual setup. What is left is the part that was always genuinely yours.

Should a step still misfire, support answers at any hour with an actual fix rather than a knowledge-base link and a shrug. Half the guides on this site began as repeat patterns in our ticket queue.

Checking whether the name is still free before somebody else asks

The hosting these steps were tested on

Tutorials written against imaginary hosting go stale fast. Ours are written against the real thing: the same panel, installer and defaults waiting in your account.

A copy is taken daily on every plan, and putting a file or a database back is one click in the panel rather than a support ticket.

  • Every step checked exactly as published
  • The snag named before it arrives
  • The dull steps taken out of your way
  • People reachable at any hour you stall

Why Hosting & Domains

Standard on every plan

Works exactly as printed

Every step is proven on the platform we run — none of the 'your host may vary' hedging.

The snag, flagged up front

The classic error for this particular task is named before step one, which is how 10 minutes plus propagation stays 10 minutes plus propagation.

Help that keeps your hours, not ours

Stuck on step three at midnight? Support answers at any hour, mid-walkthrough included.

Taken from real tickets

These guides came out of the support queue, so every snag flagged is one people genuinely hit.

Honest about how big it is

Connect a domain registered anywhere to the hosting account built to serve it is a beginner-level job — set aside 10 minutes plus propagation, with the platform-absorbed steps marked.

The dull parts automated

SSL, backups and installs look after themselves here, leaving the guide to cover only what is genuinely yours.

Quick Start

Order placed to site online

  1. 1

    Copy the nameserver pair

    They appear in the welcome email and again in the client area, written as ns1 and ns2 addresses. Paste them rather than typing them out, because retyping from memory is where a stray character gets in.

  2. 2

    Sign in wherever the name is registered

    Open the management page for the name at whichever registrar holds it. The section you want may be called nameservers, DNS settings or delegation, depending on the panel.

  3. 3

    Replace the whole pair

    Put your hosting's pair in and take every leftover entry out. A half-and-half set, part old provider and part new, gives you DNS that answers correctly one day and fails the next.

  4. 4

    Save it and let it spread

    Most networks have the change within an hour or two, though a few stragglers take a day or longer. A propagation checker will show which parts of the world hold the new answer and which are still behind.

  5. 5

    Load the site and check the certificate

    Once the name starts resolving here, open the site and confirm the free certificate has been issued against it. Issuance happens by itself as soon as DNS arrives, so this step confirms rather than configures.

Built In

Fitted to every plan

  • Your existing site brought across by our engineers, at no charge
  • Mailboxes that answer at the name you hold
  • 99.9% uptime as the target, watched around the clock
  • No set-up charge at any point, and no joining fee
  • Free SSL on every plan, reissued before the old one lapses
  • People on the support desk every hour of every day
  • Webmail in the browser plus IMAP, POP and SMTP for any client
  • Staging copies for trying a change before it goes live
  • WordPress Toolkit, with the updates seen to for you
  • WebP image optimisation built in, at no extra charge

Frequently Asked

The questions that come up most

Nameservers, or just an A record?

Handing the nameservers over gives your hosting the entire zone, which is the simplest route and leaves certificates and mail records to look after themselves. A single A record suits the case where DNS has to stay put and only the website is moving. Doing this for the first time? Move the nameservers.

Will pointing the name here stop my email?

Only where mail lives elsewhere and its records are left behind. Write the existing MX entries down before the switch and rebuild them in the new zone, or pass the details to us and the zone will be ready before you move, so nothing goes astray.

Is the free SSL certificate genuinely free?

Entirely, on every plan. The certificate is issued as soon as the name points here and reissues itself well before it lapses. On encryption it matches any paid DV certificate — the paid options exist for wildcard coverage or organisation validation, which most sites never need.

Does hosting include mail?

Yes — every hosting plan includes mailboxes at your own name, with webmail, IMAP, POP and SMTP plus spam filtering on from the start. There is standalone email hosting too, for a name whose website lives somewhere else.

Keep reading

  • How to Secure WordPress

    Shut the doors WordPress attackers actually use — intermediate level, about an hour of setup.

  • How to Write a robots.txt

    Steer crawlers sensibly, and avoid the self-inflicted injuries this file is famous for — intermediate level, about 15 minutes.

  • TLD (Top-Level Domain) (Glossary)

    A single term without the jargon: what it means, why it counts, and where it catches people out.

  • Node.js Hosting

    Run Node.js applications beside your sites, with SSH and Git included.

  • Laravel Hosting

    Laravel-ready hosting with Composer, SSH and Git-driven deployment.

Changing hosts? Run through our checklist first.

A plain order of work for a move nobody visiting will notice: which files go over first, how to carry the mail across without losing a message, when exactly to repoint DNS, and the two mistakes behind nearly every outage we are asked to rescue.

What arrives is the checklist, and then the occasional note on keeping a site quick. Leave whenever you like; the privacy policy covers the rest.

The name is waiting.

Free SSL, a free migration, renewals billed at the original rate, and people on support around the clock. That is the whole of it.

View Node.js Hosting plans