1. Home
  2. Learn
  3. Registering a domain and setting up hosting

Domains, hosting & DNS

Registering a domain and setting up hosting

The whole process end to end, the order to do it in, and the traps — nearly all of which are commercial and not technical.

In short

Buy the domain from a registrar, buy hosting separately, then point one at the other with DNS. The technical part takes about twenty minutes. What actually costs people money is everything around it: first-year teaser pricing that quadruples on renewal, auto-renew left off, domains registered in somebody else’s name, and transfer locks that stop you leaving for sixty days. Register the domain yourself, in your own name, on an account only you control — everything else can be undone later, and that can't.

The order to do it in

Five steps. The whole thing is an evening's work, and steps two and five are where the money is lost.

  1. Check the name is actually available and usable — not just as a domain.
  2. Register it at a registrar, in your own name, on your own account.
  3. Buy hosting somewhere, separately, once you know what you are building.
  4. Point the domain at the host with DNS.
  5. Lock it down — auto-renew, two-factor, transfer lock, and a renewal address you'll still be reading in three years.

If you only take one thing from this page, take step two. The difference between a registrar and a host is the companion piece if the distinction isn't yet obvious.

Before you buy the name

Four checks, in this order, before you spend anything:

  • Say it out loud on a phone call. If you have to spell it, or explain whether it's hyphenated, you'll do that every day for years. This eliminates more candidate names than anything else on the list.
  • Search the name as a business, not as a domain. An existing company with the same name in your sector is a trademark problem, not a naming coincidence, and it is far cheaper to discover now.
  • Check the handles you care about at the same time. Getting the domain and losing every social account to a squatter is a poor trade.
  • Check what the name did before. A previously-registered domain can carry a history — search it, and look it up on the Internet Archive to see what used to be published there.

On the extension: .com still wins for most businesses, because people type it by reflex regardless of what's on your card. The newer extensions are fine and no longer look strange, but if a customer will ever say your address out loud to someone else, the reflex costs you traffic you never see. Regional and sector extensions are a reasonable second choice; free extensions aren't.

Registering it, and what to decline

Registration itself takes five minutes. The checkout is where registrars make their margin, so it's worth knowing what each add-on actually is before you're looking at it.

Offered at checkoutVerdict
WHOIS / domain privacyTake it, and don't pay much. Several registrars include it free. Without it your name, address, email and phone can be published in a public database.
Auto-renewTake it. This is the single most important checkbox on the page.
Multi-year registrationReasonable. It removes a lapse risk. It does not help your rankings, whatever the upsell copy implies.
Bundled email hostingUsually decline. Buy email where it suits you; it's not tied to the domain.
SSL certificateDecline. Your host almost certainly provides one free through Let's Encrypt.
Site builder / hosting bundleDecline — see the next section.
"Domain protection" tiersDecline the paid ones. The useful protections — transfer lock and two-factor — are free.

Check the renewal price, not the first-year price. A domain advertised at $1 commonly renews at $20 or more, and the renewal is the price you'll actually pay every year for the rest of the business's life. Registrars aren't hiding this, but they're not putting it in the large type either.

Register it in your own name. Yours.

The one that costs people their business

Whoever is listed as the registrant owns the domain. Not whoever paid, not whoever built the site, not whoever the business belongs to. The registrant.

The common version of this goes: a developer, agency or nephew sets everything up as a favor, registers the domain on their own account, and everything is fine for four years. Then the relationship ends, or they move on, or they simply stop replying to email — and the business discovers it doesn't control its own address.

Recovering a domain from an uncooperative registrant is slow, sometimes expensive, and occasionally impossible. It's one of the few genuinely unrecoverable mistakes in this whole subject.

This applies to me too. If I build your site, register the domain yourself, on your own account, with your own card and your own email. I'll happily walk you through it or take delegated access afterwards. Any developer who resists that arrangement is telling you something useful about how the relationship ends.

Choosing a host

Buy hosting after you know what you're building, because the answer differs. A WordPress site, a static site and a shop have genuinely different requirements, and the cheapest plan that fits is usually correct.

What actually matters, roughly in order:

  • Server response time. This sets the floor for how fast every page can possibly be. Nothing you do in the front end recovers a slow server. More on that here.
  • Backups you can restore yourself, without opening a ticket, ideally daily and retained for a month.
  • Free SSL, renewed automatically. This is standard now; a host charging for it's telling you what kind of host it is.
  • Staging, if the site will be changed regularly. Testing a plugin update on the live site is how sites break on a Friday.
  • Support that answers. Worth more than a slightly faster benchmark, and harder to evaluate before you need it.

Buy hosting and the domain from different companies. Not because bundles are a scam, but because the domain is the irreplaceable half. If a dispute with your host ever gets bad, you want to be able to move the site somewhere else that afternoon without asking their permission to take your address with you.

Pointing the domain at the host

Two ways to do this, and it's worth understanding which one you've chosen because it determines where you go to change things later.

  • Change the nameservers at the registrar to the ones your host gives you. The host then runs your whole DNS table. Simplest, and the right default for most people.
  • Keep DNS at the registrar and add an A record pointing at the host's IP address. More control, and necessary if other services already depend on records in that table.

The mistake is doing half of each and then being unable to work out why a change has no effect. Whichever table your nameservers point at is the only one that's live; every other control panel is a decoration. How to read a DNS table covers each record type.

On propagation: the “24 to 48 hours” figure is folklore. What actually governs it's the TTL on the records, often an hour. If you know a change is coming, lower the TTL a day beforehand and the switch takes minutes. If you've already made the change, you're waiting out the old TTL and nothing will speed that up.

The day-one lockdown

Ten minutes now, once, and you'll not think about it again:

  1. Turn on two-factor authentication at the registrar. That account controls your domain, your website and usually your email. It deserves better protection than your streaming subscriptions have.
  2. Confirm auto-renew is on and that the card on file is one that will not expire quietly.
  3. Set the contact email to something durable — not an address at the domain itself, which becomes unreachable in exactly the emergency where you need it, and not an employee's personal inbox.
  4. Enable the registrar transfer lock. On by default at most registrars; confirm it rather than assume.
  5. Write down where everything lives. Registrar, host, DNS, email, and who has access. One page. This is the document every business wishes it had at the worst possible moment.

The traps, ranked by how much they cost

  • Letting it expire. After expiry there's roughly a month of grace where you can renew normally, then a redemption period where recovery typically costs somewhere between eighty and a couple of hundred dollars, then the name goes back on the open market. Expired domains in active use are watched and bought quickly.
  • The sixty-day transfer lock. ICANN policy prevents transferring a domain to another registrar for sixty days after registration — and again for sixty days after a change of registrant. If you plan to move a domain to a client or a company account, do it knowing the clock starts then.
  • The free domain that came with hosting. Genuinely free for a year, then renewed at the host's price, and often awkward to move away from. Fine if you've read the terms; unpleasant if you assumed you owned it outright.
  • Assuming email comes with it. A domain gives you the right to use addresses at that name. Somewhere still has to run the mailboxes, and that's a separate purchase and a separate set of DNS records.
  • Losing the account, not the domain. The person who set it up left. Nobody knows which registrar it's at, let alone the login. This is more common than expiry and far more embarrassing. A lookup on the domain will at least tell you the registrar.

None of these are technical problems. That's the pattern worth noticing: the hard part of owning a domain is administrative, and it stays quiet for years before it matters all at once.

Rather someone just handled it?

Knowing how this works and wanting to spend your week on it are different things. Tell me what you're dealing with and you'll get a straight answer — within one business day.