How DNS works
People remember names; machines need numbers. When someone types your domain, their device asks the domain name system where that name currently lives, receives a server address, and connects to it. The whole exchange happens before your site does anything at all, which is why a domain problem looks like a dead website even when the server is perfectly healthy.
Your domain points at a set of nameservers, and those nameservers hold the records that answer each type of question. A handful do most of the work:
- A record — the server address the website itself is served from.
- CNAME — an alias that says one name should follow another, often used for subdomains and third-party services.
- MX — where email for the domain should be delivered.
- TXT — free text used to prove ownership and to publish email authentication rules.
Each record carries a time to live, which tells everyone else how long they may remember the answer before asking again. That is why a change is not instant: the old answer is still cached in places you do not control until it expires.
Why DNS matters
Three things you depend on run through it and can be broken independently of each other: your website, your email and your verifications. Moving a site to new hosting without touching mail records is routine; changing nameservers carelessly and taking the company email down with the site is equally routine, and far more painful.
It is also where ownership lives. Whoever controls the domain registration controls where the name points, regardless of who built the site or who pays the hosting bill. Businesses discover this at the worst possible moment, when a former agency or a departed staff member holds the only login.
Common mistakes with DNS
The first is not knowing where the records are edited. A domain can be registered in one place, have its nameservers hosted in a second, and serve the website from a third; changes made in the wrong dashboard have no effect and people conclude the change did not work.
The second is deleting text records that look like clutter. Those strings are often what verify your domain with Search Console, an ad platform or your email provider, and removing them quietly withdraws access or damages email delivery. The third is letting the registration lapse. A domain that expires does not politely wait for you; the site, the email and the search visibility built on it all stop at once.
How to act on it
Keep the domain registered in the business’s own account, with auto-renewal on, the transfer lock enabled and recovery details someone still working there can reach. Before any migration, export or screenshot the current records so you can restore them exactly, and lower the time to live in advance so the switch takes effect quickly when you make it.
Change one thing at a time and check email as well as the website afterwards, including a test message from outside the company. If a site move is involved, plan it as a proper hosting migration with the new server tested before the name is pointed at it, and keep the old one running until traffic has settled. Treat email authentication records as part of the same job rather than something to fix afterwards.