DNS is the system that connects a domain name such as yourbusiness.ie to the internet services behind it — including your website, email and other systems.
You do not need to become a DNS expert to own a business website.
But understanding the basic idea is useful because DNS is one of the places where websites, domains and email can become accidentally tangled together.
A careless DNS change can take a website or business email offline even though neither service itself is broken.
The domain is the name; DNS contains the directions
Suppose you own:
yourbusiness.ie
The domain itself does not contain your website.
DNS records tell internet systems where different services associated with that domain should go.
One record might direct website traffic.
Another may help direct email.
Other records can verify ownership or configure specialist services.
That is why your domain, DNS and website hosting are related but separate things.
Why do we need DNS?
Computers ultimately communicate using network addresses and technical service locations.
Humans prefer memorable names.
DNS provides the layer that lets us use:
builtbygavin.com
instead of remembering whatever underlying infrastructure currently serves the site.
That separation is extremely useful.
It means the domain name can stay the same even when the website moves to a different hosting platform.
You update the DNS directions rather than changing the business's public address.
What is a DNS record?
A DNS record is an instruction associated with the domain.
You may see record types such as:
A
AAAA
CNAME
MX
TXT
Those names look technical, but the business owner does not need to memorise all of them.
The important idea is that different records have different jobs.
An A or CNAME record might be involved in directing website traffic.
MX records are associated with email delivery.
TXT records are often used for verification and email/security configuration.
The danger comes from treating every record as though it belongs only to the website.
It does not.
Why can changing a website break email?
Because DNS may be controlling both.
Imagine a new web developer takes over the domain and replaces the DNS configuration without preserving the email records.
The new website might work perfectly.
The email might stop.
This is why I think DNS changes should be treated carefully rather than as a routine "point the domain at the site" step.
Before changing nameservers or replacing a DNS zone, understand what services are already using the domain.
Worth knowing
This is one of the reasons I am cautious about developers taking over a domain and immediately changing everything. DNS may be quietly running the website, email and other business services at the same time. Before changing nameservers or records, I would first understand what is already there. A shiny new website is not much consolation if the company's email stops working.
What are nameservers?
Nameservers tell the wider internet which DNS provider is authoritative for your domain.
In a common Cloudflare setup, for example, you add the domain to Cloudflare and then update the domain's nameservers so Cloudflare becomes the authoritative DNS provider.
After that, the DNS records are managed in Cloudflare.
Changing nameservers is therefore a significant step.
It is not just changing one website setting.
You are changing which system is responsible for answering DNS queries for the domain.
What does Cloudflare DNS do?
Cloudflare provides authoritative DNS across its plans.
Its DNS service stores and answers the records that direct traffic for your domain.
For a Built by Gavin project using Cloudflare, this can put the website's DNS, SSL/TLS and Pages deployment inside a coherent infrastructure setup.
That can be convenient.
But I still want the client to understand that the domain itself is an asset they should control.
The platform is there to serve the business.
The business should not become dependent on somebody else's personal account without understanding why.
Is DNS the same thing as hosting?
No.
Hosting is the infrastructure serving the website.
DNS tells visitors where to find that infrastructure.
You could move a website from one host to another and update the DNS to point toward the new location.
The public domain can remain exactly the same.
That is why separating the concepts matters when you are changing web designers.
Is DNS the same thing as the domain registrar?
Not necessarily.
Your registrar is the company through which the domain is registered.
Your DNS provider may be the same company.
Or it may be different.
You might register a domain with one provider, use Cloudflare for DNS and host the website elsewhere.
That is completely normal.
Again, these services are connected without being identical.
What is DNS propagation?
When DNS records change, the new information may not appear everywhere at precisely the same instant because DNS information is cached for periods of time.
People often refer to the time it takes for changes to become visible across networks as "DNS propagation".
In practice, many changes appear quickly, but the exact timing can vary based on caching and the record's TTL settings.
This is why a website move can occasionally appear correct for one person while another still reaches the old destination for a period.
What is TTL?
TTL means "time to live".
It tells DNS resolvers how long they may cache a record before checking again.
A shorter TTL can make changes refresh more quickly, but it is not something most business owners need to manage day to day.
It becomes relevant during migrations and infrastructure changes.
Can DNS improve website speed?
DNS performance is one small part of the overall website experience.
A fast resilient DNS provider can respond quickly when users need to resolve the domain.
Cloudflare describes its authoritative DNS service as operating across its global network with a focus on performance and reliability.
But DNS alone will not rescue a slow, badly built website.
It is one layer of the infrastructure.
What about DNSSEC?
DNSSEC adds cryptographic signatures to DNS data to help protect against certain forms of DNS manipulation.
Cloudflare supports DNSSEC.
For an ordinary business owner, the main point is that DNS itself has security features beyond simply mapping names to services.
Whether and how it is enabled depends on the registrar/DNS setup.
This is another area where good configuration matters more than the client memorising terminology.
Who should control the DNS?
Ideally, the business should have clear ownership or administrative control of the account that matters.
A developer may manage DNS on the client's behalf.
That is normal.
What I dislike is a setup where the business does not know where its domain is registered, cannot access the account and is frightened that changing supplier will break everything.
That is an ownership problem, not a technical necessity.
The planned guide on who should own your business domain goes deeper into that.
Gavin's take
My preference is simple: the business should never feel trapped because only the web designer understands or controls the domain setup. I am happy to manage the technical side, but ownership and access should be clear enough that another competent person could take over later without holding the website or email hostage.
Gavin’s perspective
Built by Gavin's approach
I want domain and DNS arrangements to be understandable.
The client does not need to know how to configure an MX record.
But they should know:
who owns the domain;
which account controls DNS;
where the website is hosted;
and which services must be preserved if something changes.
That makes future maintenance and handover much less painful.
Good technical work should reduce dependency, not manufacture it.
The bottom line
DNS is the routing layer between your domain name and the services that use it.
It helps visitors find your website.
It helps mail systems find your email provider.
It can verify and secure other services.
You do not need to manage the technical details yourself.
But knowing that DNS is separate from the website and the domain registrar can save a business a lot of confusion.
Need the domain and website setup handled cleanly?
See my website options or tell me what you already own.
If you already have a domain and business email, I can work around what exists rather than replacing things blindly.
---