Domain and DNS explained for business owners

en 2026-09-16 6 min read

Your domain should be registered to your business, in a registrar account you can open without asking anyone for the password. DNS is the list of records that tells browsers and mail servers where that name points, and setting those records is part of launching every site we build, from a EUR 600-900 single-page landing to a custom SaaS platform from EUR 7.500.

A domain problem does not show while a site is being built. It shows at launch or at handover, when a record has to change and nobody can find the login.

Three things people mean by "the domain"

Registrars sell them together, but each can sit with a different company.

• The registration is your right to use the name. You renew it with a registrar, and the registrant named on it is the legal holder. For a .nl domain the registry behind the registrar is SIDN.
• DNS is the set of records for that name, kept on nameservers. Those nameservers can be run by your registrar, by a DNS provider such as Cloudflare, or by your hosting platform.
• Hosting is where the website runs. The DNS records point at it, and it can move without the registration moving.

How DNS works

When someone types yourcompany.nl, their device asks a resolver for the address. The resolver asks the .nl registry which nameservers are in charge, then asks those nameservers for the record. The answer comes back and the browser connects to your host.

Resolvers cache that answer for as long as the record's TTL, its time to live, allows. That caching is all that people mean by propagation: some visitors keep the old answer until their cached copy runs out. Lower the TTL well before a planned change and the switch reaches everyone sooner.

A website launch changes one or two of these. Email depends on several, and the TXT records are the easy ones to lose because nothing looks broken when they go missing. Without SPF, DKIM and DMARC, mail from your domain is more likely to land in spam, including the message your contact form sends you.

Who should own the domain

Your business should. Everything points at the name: your email, your history in Google, the links other sites have published, the address on your invoices. Whoever is the registrant controls all of it. If that is a former agency, a freelancer or an employee's personal account, every change and every renewal needs their cooperation.

• Register the domain in the legal name of the business, with a contact address the business controls rather than one person's inbox.
• Turn on two-factor authentication and automatic renewal, and keep the card on the account current. An expired card can quietly become an expired domain.
• When a developer needs to change records, give them DNS access, through a user invite where the registrar offers one, and keep the registration in your account.

Why it matters at handover

A handover is complete when someone else could pick the site up and find everything. For the site that means the code, the repository and the database, which are yours. For the domain it means these checks, done and written down.

1. Confirm the registrant is your business. Public lookup services can hide the holder for privacy, so check inside the registrar account itself.
2. Note where DNS is managed by looking up which nameservers the domain uses.
3. Export the full record list before anything changes, MX and TXT records included.
4. Lower the TTL ahead of the cutover.
5. Point the website records at the new host and leave the mail records alone unless mail is moving too.
6. Check the HTTPS certificate, that www and the bare domain both load, and that old addresses redirect.
7. Record the registrar, the DNS provider, the final records and everyone who has access.

The first check is the part that waits on you. If nobody can find the registrar login, launch waits on the registrar's recovery process, and no work on our side shortens that. Look for the login before the project starts.

Where DNS work sits in each step

DNS is part of launching at every step on packages. What changes from step to step is how many records are involved.

Hosting is agreed per project. Wherever the site runs, the records on your domain are what send visitors to it, which is why the domain deserves more care than the hosting plan.

One DNS task belongs to search rather than launch: verifying the domain in Google Search Console with a TXT record. That sits inside the SEO foundation, a one-off EUR 450-750 that also covers analytics, indexation, technical hygiene, titles, internal links and a 3-6 month plan. How the build side works is on design and engineering.

When to spend less

• You do not need a new registrar to launch a new site. The registration stays where it is and a few records change.
• Skip buying every extension out of worry. Register the ones you will use, plus any someone could plausibly use to impersonate your brand.
• Check what your registrar already includes, such as DNS hosting or privacy on the public record, before paying for add-ons. The DNS that comes with the registrar or host is enough for a business website.
• Do not buy a second, keyword-filled domain in the hope of ranking. Google ranks pages on their content and the links pointing at them, and a second domain splits your name in two.

Questions buyers ask

Should my web designer register the domain for me?

It is safer to register it yourself, because the registrant is the legal holder. If someone does it on your behalf, check that the registrant is your business and the contact email is one you control before anything is built on it. Fixing it later means a formal registrant change.

Will changing DNS break my email?

Only if the mail records change or get lost. Website records and mail records are separate, so the site can move while the MX and email TXT records stay exactly as they are. The risk comes when nameservers move to a new provider and the record list is not copied across in full, which is why the export happens before any change.

How do I get my domain back from a previous agency?

Ask in writing for two things: the registrant changed to your business, and the transfer code for moving the domain to your own registrar account. For a .nl domain that code is called a transfer token. If the agency no longer responds, contact the registrar with proof that your business is the rightful holder and ask how their recovery process works.

What does DNS propagation mean?

It means caching. Resolvers keep the old answer until the record's TTL runs out, so for a while some visitors reach the old site and some reach the new one. Lowering the TTL well before the cutover keeps that overlap short.

If you are not sure who holds your domain or where its records live, include the domain name when you describe your project and we will check it during scoping. Get in touch.