DNS, CDN, and Origin Hosting: Who Controls What?

November 5, 2026 | Business Growth Strategies

A website goes down. The owner calls the web designer, who says it is a hosting issue. The host says the server is fine and it must be DNS. Nobody knows who has the Cloudflare login, and the domain registrar account is in the name of an employee who left two years ago.

This scenario is common because websites run on several connected but separate layers. DNS and CDN explained simply: each layer does a different job, often sits with a different provider, and needs a clear owner. When ownership is undocumented, small problems become long outages.

The Request Path

When someone types your domain into a browser, the request travels through several layers:

Visitor → Domain registrar → DNS → CDN / proxy → Origin hosting → Website application → Database

Each step has its own provider, settings, and credentials.

The Layers Explained

Domain registrar. The company where the domain is registered and renewed. Whoever controls this account ultimately controls the domain. Losing access here is the most serious risk.

DNS (Domain Name System). The directory that points the domain to the right servers for the website, email, and other services. DNS may be hosted at the registrar, at the hosting company, or at a separate provider such as Cloudflare.

CDN and proxy. A content delivery network caches content at locations close to visitors and can filter malicious traffic. Services such as Cloudflare often act as both DNS provider and CDN, sitting in front of the origin server.

Origin hosting. The server where the website files and database actually live. This is the hosting company, whether shared, VPS, or managed WordPress hosting.

SSL/TLS certificates. The certificates that enable HTTPS. They may be issued by the host, the CDN, or both, and each must renew.

Email. Business email is often hosted separately, by Google Workspace, Microsoft 365, or another provider, and depends on DNS records being correct.

Why Separation Causes Confusion

Because these layers are separate, a single change can have broad effects. Changing nameservers at the registrar moves DNS control elsewhere. A DNS edit can break email. A CDN setting can serve stale content. Migrating hosting requires DNS changes, and a migration completed without updating every record can leave email or subdomains pointing to the old server.

What to Document

Create a one-page infrastructure map and keep it updated. For each layer, record:

  • Provider and account name.
  • Account owner, ideally a company-controlled email address, not a personal one.
  • Who has access, with multifactor authentication enabled.
  • Where credentials are stored, such as a company password manager.
  • Renewal dates for domains, hosting, certificates, and subscriptions.
  • Auto-renew status and the payment method on file.
  • Key DNS records, including website, email (MX, SPF, DKIM, DMARC), and verification records.

Common Ownership Risks

  • The domain is registered under a former employee or agency’s personal account.
  • No one has the CDN login, but it controls DNS.
  • Domain auto-renew uses an expired credit card.
  • An old hosting account remains active and still receives some traffic.

Each of these is simple to fix before an emergency and stressful to fix during one.

Review After Every Migration

Hosting migrations are the moment documentation most often breaks. After any migration, confirm where DNS lives, verify that all records point correctly, check certificate renewal, and update the map. SETN Consultants builds this infrastructure map as a standard part of migration and website care work, and SETN Consultants keeps it current as providers change.

Questions to Answer Today

Even without a full map, a business owner can check the most important risks in a few minutes. Who is the registrant on the domain, and can you log in to the registrar account? When does the domain expire, and is auto-renew turned on with a valid payment method? Where are the nameservers pointed, and who can log in there? Who has administrator access to the hosting account? If any answer is “I’m not sure,” that layer is the place to start. These questions take minutes to answer now and can save days of downtime later.

Frequently Asked Questions

What is the difference between DNS and hosting?

DNS points your domain to servers. Hosting is the server that stores and runs your website.

Is Cloudflare a host?

Cloudflare commonly provides DNS, CDN, and security services in front of a host, but the website usually still runs on a separate origin server.

Who should own the domain registration?

The business itself, through a company-controlled account with multifactor authentication.

Why did my email break after a website migration?

Usually because DNS changes did not preserve email records such as MX, SPF, or DKIM.

Request an infrastructure map and know exactly who controls every layer of your website: setnconsultants.com/services/website-design-development/

Originally published at setnconsultants.com

About SETN Consultants

SETN Consultants helps business owners grow through strategic marketing, AI-ready websites, and results-driven digital programs.

Share this post

Is Your Business AI Ready?

Get a free digital visibility report that analyzes your website, local search presence, reputation, listings, SEO, and AI discoverability opportunities.