Back to blog
DNS Basics7 min read2026-05-22

Nameservers, DNS, and Hosting Explained in Plain English

A practical explanation of nameservers, DNS records, hosting accounts, SSL, and email records for domain owners.

The domain is the name, hosting is the place

A domain is the address people type. Hosting is where the website files or application live. DNS is the set of instructions that connects the domain to the correct services. Nameservers tell the internet where those DNS instructions are managed.

This distinction matters because moving a website does not always mean moving the domain. You can keep a domain registered with one company, manage DNS with another, host the website with a third, and use a separate provider for email.

  • Registrar: company where the domain is registered.
  • Nameservers: pointers to the DNS management location.
  • DNS records: instructions for web, email, verification, and subdomains.
  • Hosting: server or platform where the website runs.

Common records have specific jobs

A records usually point a root domain to an IP address. CNAME records point one name to another name, often for www or platform services. MX records route email. TXT records verify ownership and support email authentication. Changing the wrong record can break a service that seemed unrelated.

Before changing DNS, record the current setup. If something breaks, the old values help restore service quickly. This is especially important for business email because mail records are easy to overlook during a website launch.

  • A records and CNAME records usually affect website routing.
  • MX records affect where email is delivered.
  • SPF, DKIM, and DMARC help email authentication.
  • TXT records are often used by Google, Microsoft, CRMs, and ad platforms.

Propagation is real, but it is not a magic fix

DNS changes can take time to appear everywhere. That delay is called propagation. Waiting is normal, but waiting will not fix an incorrect record. If the wrong value was entered, the domain will eventually point to the wrong place consistently.

A good DNS workflow is simple: capture the old values, enter the new values carefully, verify with lookup tools, test the website and email, then document the final state.

  • Make fewer changes at once when working on an active business domain.
  • Use DNS lookup tools to confirm what the public internet sees.
  • Do not repeatedly flip records while waiting for propagation.
  • Keep a final DNS note after the launch is complete.