DNS explained for business owners: records, TTL and nameservers

DNS is the directory that sends visitors to your website and email to your inbox. What each record does, who controls it, and how to change it safely.

By Sohail Hussain21 November 20265 min read

DNS, the Domain Name System, is the internet's directory. When someone types your domain or sends you an email, DNS tells their computer which server to go to. You control your domain's entries in that directory, called DNS records, through an account at your DNS host. Get those records right and your website and email work; delete or mistype one and something stops, often silently.

Business owners rarely need to edit DNS. They do need to know who holds it, what the records do, and why a change made for the website so often breaks email. That is what this guide covers.

Who controls your DNS: the registrar, the DNS host or the web host?

Three companies can be involved, and they are often different:

  • The registrar is where the domain is registered and renewed. It records which nameservers the domain uses.
  • The DNS host runs those nameservers and holds your records. It might be the registrar, Cloudflare, your web host, or a cloud provider.
  • The web host runs the server your website lives on. It needs a DNS record pointing at it, but it does not necessarily hold your DNS.

A lookup at lookup.icann.org shows the registrar and the nameservers for most domains. If the nameservers end in cloudflare.com, your records are at Cloudflare, whatever the registrar is. Edit records there, not at the registrar.

The DNS host login is as sensitive as the registrar login. Whoever has it can send your website and email anywhere. Keep it in the company's name, protect it with two-factor authentication and a unique password from the password generator, and make sure two people at the company can get in. Checking these accounts is the first thing we do when a site comes to us for website care and maintenance.

What do the common records do?

RecordWhat it doesExample valueUsually set by
APoints a name to an IPv4 address203.0.113.10Your web host
AAAAPoints a name to an IPv6 address2001:db8::10Your web host
CNAMEPoints a name to another nameyoursite.netlify.app for wwwYour web host
MXSays which servers receive email for the domainsmtp.google.com, priority 1Your email provider
TXTHolds text: SPF, DKIM, DMARC and verification codesv=spf1 include:_spf.google.com ~allEmail provider, Google, other services
NSNames the DNS host's serversns1.example-dns.comThe registrar, from your DNS host
CAALists which certificate authorities may issue SSL for the domain0 issue "letsencrypt.org"You or your developer, optionally

Two details trip people up.

A CNAME cannot sit on the bare domain. The DNS standard does not allow a CNAME at the root, example.com, alongside the other records that must live there. Hosts work around this with an A record, or with an ALIAS, ANAME or "flattened" CNAME that behaves the same way. If your host's instructions say "add a CNAME for the root", check which of these your DNS host supports.

TXT records pile up. Every service that verifies your domain adds one: Google Search Console, Microsoft 365, Facebook, a newsletter tool. Most are harmless, but deleting one can quietly unverify a service. Do not tidy TXT records without knowing what each one is for.

What is TTL, and why does "propagation" take so long?

Every record has a TTL, or time to live, in seconds. It tells other servers how long they may remember the answer before asking again. A TTL of 3600 means an hour.

"Propagation" is the wait for those remembered answers to expire. Nothing is spreading; caches around the world are simply allowed to keep the old answer until the TTL runs out. So the fix is to lower the TTL to 300 seconds at least a day before a planned change. Then the change itself takes effect in about five minutes. Raise it again afterwards.

Nameserver changes are the exception. They are cached by the registry for the domain's extension, with TTLs you cannot lower, so moving your DNS to a new host can take up to 48 hours to settle everywhere. Run both the old and new DNS hosts with identical records during that time.

What breaks most often when DNS is changed?

Most often, email. The patterns repeat:

  • Moving DNS hosts without copying every record. Someone moves nameservers to Cloudflare or a new web host, the import misses the MX or DKIM records, and mail stops arriving or starts landing in spam.
  • A web host "helpfully" replacing the zone. Some hosts overwrite all records with their defaults when you point the domain at them, including the MX records.
  • Two SPF records. Adding a second SPF record for a new service, instead of editing the existing one, makes SPF fail for all of them. SPF, DKIM and DMARC explains how to combine them.
  • A CAA record left behind. A host changes certificate authority, and a CAA record naming the old one blocks renewal. SSL certificates explained covers how that failure looks.
  • Forgetting www. The root domain points to the new site and www still points to the old one.

How do you change DNS safely?

  1. Export or screenshot every record before you start. Most DNS hosts can export a zone file.
  2. Lower the TTL on the records you will change to 300 seconds, a day ahead.
  3. Make the change, changing one thing at a time where you can.
  4. Check the result from outside your network.
  5. Keep the old server or DNS host running for at least 48 hours.

To check records yourself, dig works on macOS and Linux:

bash
dig +short NS example.com
dig +short A example.com
dig +short MX example.com
dig +short TXT example.com
dig +short TXT _dmarc.example.com

On Windows, nslookup -type=MX example.com does the same job for each record type. Compare the answers with your export, and send a test email to an outside address once the change is live.

Should you move your DNS to Cloudflare?

Only if someone will look after it. Cloudflare's free plan is a good DNS host, and its proxy can add caching and attack protection in front of your site. It also adds a layer between visitors and your server that someone has to understand when things go wrong, such as a firewall rule blocking a payment callback.

For most small company sites, the registrar's DNS is fine. Move when you have a reason, such as the registrar's DNS being slow to update or lacking record types you need, and copy every record when you do.

The technical definition of all of this is in RFC 1034, the standard DNS still runs on. For the practical side, how to set up business email with your domain walks through the records email needs, how to get control of your domain back covers the registrar side, and the website maintenance guide puts a yearly DNS check into the routine.

Was this guide useful?

Questions

Frequently asked.

How long does DNS propagation take?

For a normal record change, as long as the record's TTL, which is often an hour and can be set to five minutes. A nameserver change can take up to 48 hours, because the registry's records have long TTLs you cannot lower. Lowering the TTL a day before any planned change is the single most useful habit.

Can changing DNS hurt my search rankings?

Not by itself. Google follows the domain, not the server. Rankings suffer when a DNS change takes the site offline for hours, breaks HTTPS, or points the domain at a new site with different URLs and no redirects. Plan the change, keep the old server running until traffic has moved, and the switch is invisible to search engines.

What is DNSSEC and do I need it?

DNSSEC adds signatures to DNS records so resolvers can detect forged answers. It protects against a specific kind of attack and is worth turning on if your registrar and DNS host both support it with one click. It also adds a way to break the domain: moving DNS hosts without turning it off first can take the site and email offline.

Sohail Hussain

Founder, MSH Technologies

Sohail has designed and built websites, web apps and AI products for over 12 years, for clients from Singapore-based industrial groups to early-stage SaaS startups. He writes about what actually worked.

Keep reading

Related guides.

All posts

Your next move

Like what you see? Tell us about it.

A process that takes too long, a website that undersells you, or an idea ready to take shape. Tell us where you are and we will suggest a useful next step.

India · Working with clients worldwide

Sohail, Founder, replies within 1 working day (Mon–Sat, IST). Free and no obligation.