What It Actually Means
It is worth understanding at one level of detail, because DNS problems are common, they present as several different symptoms, and they are frequently misdiagnosed as something else.
The Records That Matter To You
A records point your domain at the server hosting the website.
MX records point your email somewhere else entirely. This is the one worth internalising: your website and your email are directed independently. You can move hosting without touching email, and you can break email while doing something to the website if the records are handled carelessly.
TXT records carry verification and email authentication, including SPF, DKIM and DMARC. Those three decide whether your email reaches inboxes or spam folders, and they are among the most commonly misconfigured settings in small business IT.
CNAME records point one name at another, typically used for subdomains and third-party services.
The Two Things That Go Wrong
Changes take time to spread. Every record carries a time-to-live, and the old answer stays cached around the internet until it expires. So a change is not instant, and during the transition some people see the old destination and some the new.
The practical consequence for a migration: lower the time-to-live a day or two beforehand so the change moves quickly when you make it, then raise it afterwards. Skipping that turns a short cutover into a day of inconsistent behaviour.
Email gets broken by website work. Moving hosting and accepting a provider’s default records can replace your MX records, sending email to a server that is not expecting it. Mail bounces or silently disappears, and it is often noticed hours later by a customer rather than by you.
Recording the existing records before changing anything takes two minutes and prevents the most damaging version of this.
Where It Actually Lives
DNS can be managed at your registrar, at your hosting provider, or somewhere else entirely such as Cloudflare, and it is frequently not where people assume.
That matters when something needs changing urgently, because the first question is where the records are actually served from, and the answer is sometimes an account nobody has logged into for years.
What To Ask
- Where is our DNS managed, and who has access?
- Do we have a record of the current settings? Screenshot or export it. Free, and it is the thing you will want when something breaks.
- Are SPF, DKIM and DMARC configured? If email deliverability is poor, this is the first place to look.
- Before any hosting change: what happens to the MX records? Ask explicitly. Do not assume they will be left alone.
- What is the time-to-live, and has it been lowered ahead of the change?
Why It Is Worth Your Attention
DNS is invisible until it fails, and when it fails it takes down the website, the email, or both, in a way that looks like a much larger problem.
The failures are also disproportionately caused by ordinary maintenance rather than by anything exotic: a hosting move, a new email provider, a certificate renewal, a supplier tidying up. Knowing where the records live and having a copy of them turns most of those from an outage into an inconvenience.
More terms are in the glossary.
