Business Tech & Tools
How do domains, DNS, and web hosting fit together when I set up a website?
The short answer
The domain is the name a visitor types, such as example.com. DNS is the set of directions that tells the internet where that name’s website, email, and other services live. Web hosting is the server service that stores and delivers the website.
They can all come from one company, but they are separate jobs. Understanding that separation makes setup and troubleshooting much safer.
See the three jobs clearly
| Part | Its job | Typical account that controls it |
|---|---|---|
| Domain registration | Records who holds the right to use the domain | Domain registrar |
| DNS hosting | Publishes records that direct website and email traffic | Registrar, web host, DNS provider, or another service |
| Web hosting | Stores the website files and database and serves the pages | Web-hosting provider |
ICANN calls the person or organization holding the rights to a registered domain the registrant. See ICANN’s explanation of the domain-registration process.
The most important ownership detail is this: the business owner should control the domain account and recovery information, even if a designer or employee helps configure it. Losing a contractor should not mean losing the business name online.
Follow one visit from name to website
When someone enters www.example.com:
- Her device asks DNS where that hostname should go.
- DNS returns the destination described by the current record.
- The browser connects to the server or platform at that destination.
- The host recognizes the domain and serves the correct website.
- HTTPS protects the connection when the certificate and server are configured correctly.
That is why changing a record at the registrar does not upload a website, and uploading a website does not automatically point the domain to it. Both ends must know about the connection.
Nameservers decide where the DNS records are managed
Nameservers are the delegation that tells the internet which DNS provider is authoritative for the domain. If your registrar shows Cloudflare nameservers, you normally manage active DNS records in Cloudflare, not in the registrar’s old DNS editor.
This distinction prevents a common mistake: editing a correct-looking record in an account that is no longer authoritative. Before changing anything, identify the current nameservers and log in to the provider they indicate.
Website and email can point to different places
The website might use an A, AAAA, or CNAME record. Email may use MX records plus TXT or CNAME records for verification and authentication. A domain can send its website to one company and its email to another.
That flexibility is useful, but it means a careless nameserver change can break working email. Before replacing nameservers, copy every existing record and understand which service owns it.
Make an ownership and connection sheet
Keep this information in a password-protected business record:
- domain name and registrar.
- registrant name or business.
- renewal date and payment owner.
- recovery email and two-factor authentication method.
- current nameservers.
- DNS provider.
- web host and website-platform login.
- email provider.
- person authorized to make changes.
- date and reason for each important DNS change.
Do not store passwords in the sheet. Keep those in a password manager and record only where the credentials are held.
ICANN provides separate guidance on securely managing a domain-name account. Domain renewal and account recovery deserve the same attention as the website itself.
Diagnose problems by layer
| Symptom | Check first |
|---|---|
| Domain does not resolve anywhere | Registration status, nameservers, authoritative DNS records |
| Domain reaches the wrong website | Website record and host’s domain assignment |
| Website works but email fails | MX and email-authentication records, not the website files |
| Host preview works but domain does not | DNS connection and host domain mapping |
| HTTPS fails on one hostname | Certificate coverage and host configuration for that exact hostname |
Change one layer at a time. Take screenshots or export records first, note the original value, and define how you will know the change worked. Randomly replacing several records makes the original problem harder to identify.
Sources and further reading
A free next step
You don't have to build this alone
Bring your questions, share what you're working on, and meet other women building businesses from home. It is free to join.
Related Questions
- What should a Contact page include so customers know exactly what happens next?
- Which website mistakes make a small business look untrustworthy or unfinished?
- Where should I buy my domain, and should the registrar be separate from my web host?
- How do I connect a domain to a website using DNS records or nameservers?
Related WAHMN resource
If you want to turn this website task into a service or build a stronger process for your own site, this system walks through the work in more depth. See Website & Landing Page Build System.