12 October 2026
Domain, hosting and DNS, in plain English
When a website goes wrong, the first question is which of three things has failed. Most people have never had to tell them apart. They were set up together, often by the same person and sometimes years ago, so from the outside they look like one thing. They are three.
The domain
The domain is the name. brasslanternstudios.com is a domain. So is the address printed on your van and your invoices.
You do not own a domain outright. You register it for a set period, usually between one and ten years, through a company called a registrar. GoDaddy, 123 Reg, Namecheap, Cloudflare and AWS are all registrars. The registrar records the registrant, which is the person or company the name belongs to. It holds the name for them as long as the registration keeps being renewed.
A domain on its own does nothing. It is a name with no building behind it.
The hosting
Hosting is the building. It is a computer somewhere that holds the files and database that make up your website, and sends them out when someone asks for them.
Hosting can be a shared server, a dedicated machine, or a platform such as Cloudflare Pages, Netlify or Firebase. The site itself lives here. Often so does a contact form, a booking system or a shop.
Hosting can be moved. A well-built site can be copied to new hosting in an afternoon. A site made in a page builder like Wix or Squarespace is harder to move. There the hosting and the site come as one product, and the site cannot leave.
The DNS
DNS is the directory that connects the name to the building. When someone types your domain, their device asks the DNS where that name points. The DNS replies with an address, and the browser goes there.
DNS also decides where your email goes, and that is the part people forget. One DNS record decides whether mail sent to info@yourbusiness.co.uk reaches your inbox. Another set of records decides whether Gmail and Outlook trust that mail enough to deliver it, rather than filing it as spam.
By default the DNS is usually run by the registrar. It does not have to be. It can be moved to the hosting company or to a separate service such as Cloudflare, and many sites run that way.
Why they get confused
They get confused because one company often sells all three. You buy a domain, the checkout offers hosting, and the DNS is set up quietly in the background. Everything sits behind one login. A few years later a web designer moves the site to new hosting and changes the DNS. Now the three pieces sit in two or three different accounts, and only one person knows which.
That is normal. It only becomes a problem when nobody has written it down.
Who holds yours
Three questions are worth answering now, while nothing is broken.
Who is the registrant on my domain? It should be you or your company. It should not be your web designer, a former employee or whoever happened to set it up in 2014. You can check this in the registrar account. For a .co.uk, Nominet holds the record and can confirm the registrant to you.
Whose email address is on the registrar account? Renewal reminders and transfer codes go there. If nobody reads that address, a renewal can lapse without anyone noticing.
Who has the logins for the hosting and the DNS? Ideally you do, with your developer added as a user. It should not be the other way round.
If the answer to any of these is "I'm not sure", that is the thing to fix first.
Why losing the domain is worse than losing the hosting
If you lose the hosting, the site goes offline. That is serious, but you can recover from it. The site can be restored from a backup or rebuilt, then put on new hosting. Point the DNS at it and you are back. At worst it takes days.
If you lose the domain, you lose the name itself. Every link to your site stops working. Every printed card, van and Google listing points at something you no longer control. Your email stops arriving, because your email address was built on the domain. Password resets for your other accounts go to that email address. Customers who write to you get messages bounced back. If someone else registers the name, their messages go to a stranger instead.
People watch for expired domains. When a registration lapses there is a grace period, and after that the name is released. Names that already have traffic and links pointing at them are picked up quickly, by people who resell them or use them for spam. Getting one back is slow, and it is not guaranteed.
The domain is the one piece you cannot rebuild. Everything else can be replaced.
What we do with clients' domains
When we build a site, the domain stays in the client's name. If a client asks us to manage the DNS or the hosting, they are added as an owner on those accounts too, so nothing depends on being able to reach us. At handover we write down where each of the three pieces lives, which account holds it, and when the domain next renews. It is one page, and it is the page people most often wish they had.
That is how we approach web development in general. The work is not finished when the site looks right. It is finished when the owner knows what they have.
A second pair of eyes
If you are unsure where your domain, hosting and DNS sit, we are glad to take a look. We work with businesses in Sutton Coldfield, Great Barr and well beyond, and the answer usually takes about ten minutes to find.