Skip to main content
.com domains from $2.99 — free WHOIS privacy on every name

DNS runbook · Beginner · 10 min at the keyboard

How to register a domain name — Buy the Name, and Keep Control of the Record

You want the name today and the ability to repoint a record in five minutes at midnight, not a registrar that queues zone edits behind a support ticket.

The short answer

Registering takes about ten minutes, and then the only thing that matters is whether you can edit the zone yourself and set your own TTLs. That single piece of control decides how fast a launch, a migration or a 3am incident can be fixed.

The mechanics are a search, an extension decision, payment, the registry verification email and auto-renew. None of that is hard. The costs land months later, in the things nobody checks on the day: whether the panel exposes a TTL field, whether DNSSEC can be toggled without a ticket, and whether the notification address is a mailbox anyone still reads.

By the HostingFast team · Reviewed 24 August 2026

Beginner

Skill floor

5

Steps to a live name

Free

Support, every tier

Proven

Run on the live stack

Assumed knowledge: you know what an A record is and you have run dig at least once. Ten minutes of attention, a card and a mailbox you genuinely monitor is the whole entry requirement.

Every screen named below is the cPanel and client area we run from London, so the field names match rather than approximate. Nothing here is one-way, and where a step has a reverse gear it is printed alongside.

What the registrar quietly decides for you

A registration is a lease on a delegation, not the purchase of a server. What you are really buying is write access to a zone: the ability to change an A record, add a TXT token, or drop a TTL to 300 seconds an hour before a cutover. Registrars differ enormously on that and none of it appears on the price page.

Before you pay, look for four things in the DNS editor: an editable TTL field, a record set that runs past A and CNAME to SRV and CAA, a DNSSEC switch you can operate yourself, and either an API or a bulk editor. If TTL is pinned at 14400 you have just accepted a four-hour recovery window on every mistake you have not made yet.

Hyphens, near-misses and the redirect tax

A name you have to spell out on the phone tends to become two names and a redirect. Every redirect hop is another DNS lookup, another TCP and TLS handshake and another request before the real page starts. Count them with curl -sIL -o /dev/null -w '%{num_redirects} %{time_starttransfer}\n' and you will see the cost on a mobile connection immediately.

That is an argument for a short, unambiguous name rather than for buying twelve variants. Register the defensive spellings if the brand is going on a van or an invoice, then send each one to the canonical host with a single 301 and never let a second hop creep into the chain.

The verification clock, and why it lands mid-launch

Registries email every new registrant a verification link. Leave it for roughly a fortnight and the registry suspends the domain: it stops resolving, and it stops resolving in the week you had blocked out for going live. This is not an obscure edge case, it is the commonest reason a brand new name goes dark.

Clear it the day it arrives, and check the contact address sits on a different domain from the one you have just bought. A verification message sent to admin@ the new domain, before any MX record exists, is a loop with no way in from the outside.

What the platform has already taken off you

Once the name resolves, several jobs simply vanish. SSL is issued and reissued without anyone asking for it. Softaculous handles the application install. Backups run daily on every plan, and per-site PHP versions and cache settings live in cPanel rather than in a file you edit over SSH.

What is left is the work that is actually yours: the records, the redirects and the measurements. Support is staffed round the clock when a delegation refuses to take, and a good number of the pages in this library started life as a repeating pattern in that queue.

Hunting down the right domain name before someone else takes it

The stack these steps were measured on

Every walkthrough here is run against the platform we operate — cPanel, LiteSpeed in front of NVMe, Softaculous, WP-CLI over SSH — so the field names in the instructions are the field names on your screen.

The rate you sign up at is the rate you renew at, so year two costs what year one did. There is no introductory price to unwind later.

  • Commands and field names quoted as they appear
  • The failure mode named before you meet it
  • Anything automatable already automated
  • Engineers on support at any hour

Why HostingFast

Standard on every plan

Reads like the panel

Buttons, fields and commands are quoted as cPanel and the client area present them, not paraphrased from a screenshot.

Scoped honestly

Registering a name is a beginner job of roughly ten minutes, and the steps the platform absorbs are marked as absorbed rather than padded out.

The failure named early

The registry verification clock appears on this page before step one, which is how ten minutes stays ten minutes.

5 steps, no padding

Each step is one discrete action with an observable result, and the fiddly ones are labelled fiddly.

Only measurable claims

Where a number matters — TTL, redirect hops, which resolver answered — the page names the command that produces it.

Engineers on call

Stuck on a delegation at 2am? Support answers at any hour, mid-walkthrough included.

Quick Start

From order to online

  1. 1

    Fix the ending and the term before you search

    Decide on .com for a global audience or a country code such as .co.uk when every visitor sits in one market, and decide how many years you are paying for. Settling this first stops the search box talking you into a name you never wanted.

  2. 2

    Check availability, then check the delegation

    Run the availability search — it queries the registries live, so an available result genuinely is available at that instant. For anything you are inheriting rather than creating, follow up with dig NS thename.com +trace to see who answers for it today.

  3. 3

    Register, then audit the zone editor immediately

    Complete the order; ownership starts the moment payment clears. Open the DNS editor straight away and confirm you can set a TTL, add a TXT record and see a CAA row. Finding a gap now beats finding it during a cutover.

  4. 4

    Switch auto-renew on before you close the tab

    One control stops a busy month returning your name to the open pool. Enable it in the client area at once, and put the card expiry date in the same calendar as the domain renewal so the two cannot drift apart.

  5. 5

    Clear the registry verification the same day

    Open the confirmation email and click the link. Ignore it and the domain stops resolving after about a fortnight regardless of what you paid. Then confirm with dig A thename.com @1.1.1.1 that a resolver you do not control can see the name.

Built In

Loaded onto every plan

  • No setup fee on any plan, at any tier
  • DDoS filtering absorbed at the network edge
  • SSH with Git and Composer on the developer plans
  • Free migration: our engineers move the existing site
  • WebP conversion built in, at no extra cost
  • Softaculous for one-click application installs
  • WordPress Toolkit, with updates applied for you
  • Daily backups and self-service restores from the panel
  • Support staffed by humans, every hour of the day
  • Money back: 30 days on hosting, 7 on reseller

Frequently Asked

What people ask us most often

Does the TLD I pick change DNS lookup time?

Not by anything you will measure. Resolution time is dominated by the authoritative nameservers you delegate to and by whether the answer is already sitting in a resolver cache, not by the letters after the dot. Choose the ending on audience and credibility; if you want a faster first lookup, work on TTLs and on keeping the delegation chain short instead.

Should I lower the TTL before I move the site?

Yes. Drop the records you intend to change to 300 seconds at least one full old TTL period before the cutover, so resolvers are already holding a short-lived answer when you make the switch. Put it back to something sensible such as 3600 once the move has settled, because a permanently low TTL makes every visitor pay for a fresh lookup.

Can I keep the domain here and serve the site elsewhere?

Yes. Delegation and hosting are separate decisions: point the nameservers at whoever holds the zone and set the A record at whatever origin serves the site. Keeping both in one account means one login and one team when a record has to change quickly, and annual hosting plans include the first year of the domain.

Do I get SSH and Git on the entry plan?

Yes. Full SSH access with Git and Composer is on the shared cPanel plans rather than being held back for the top tier, so you can clone a repository and run composer install on the same account you registered the domain from. WP-CLI runs over that same session.

Keep reading

Changing hosts? Run through our checklist first.

A straightforward sequence for a switch your visitors never feel: which files move first, how to shift email across without losing a single message, the right moment to repoint DNS, and the two mistakes behind almost all the downtime we get asked to rescue.

You'll get the checklist email, then occasional pointers on keeping a site running fast. Unsubscribe the moment you want out — the privacy policy covers the rest.

Put the name on quicker hardware.

NVMe behind a LiteSpeed cache, free SSL, free migration, and a renewal price identical to the one you signed up at.

View Domain Names plans