When a company launches a website, it is common to purchase the domain, web hosting, email, SSL certificate and maintenance as part of the same service.
This is convenient, but it can also create an important misunderstanding: all these elements are connected, but they are not the same thing and do not necessarily have to be managed by the same company.
The domain is the name that identifies the project on the Internet. DNS indicates where that name should direct each service. Hosting is the infrastructure where the website, its files and its databases are stored or executed. Maintenance ensures that the whole system continues to work correctly over time.
Understanding these differences is particularly important when:
- launching a new website,
- changing hosting providers or servers,
- transferring a domain,
- changing the corporate email service,
- implementing redirects,
- dealing with a website outage,
- or changing agency or technical team.
In this guide, we explain the purpose of each layer, where it is managed and what can happen when a change is carried out incorrectly.
Quick Summary: Domain, DNS and Hosting Are Not the Same Thing
| Element | What it does | Example | What happens if it fails |
|---|---|---|---|
| Domain | The registered name that identifies the project on the Internet. | company.com | The website, email and other services may become inaccessible. |
| Nameservers | They indicate which servers hold the domain’s official DNS configuration. | ns1.example.net | The domain may stop resolving correctly if they point to an incomplete DNS zone. |
| DNS | It connects the domain to the website, email and other services. | company.com → 192.0.2.20 | The website may point to the wrong server or email may stop working. |
| Hosting | It hosts the files, databases and applications used by the website. | WordPress server | The website may display errors, respond slowly or become unavailable. |
| Maintenance | It keeps the website updated, secure, monitored and optimized. | Updates, backups and technical reviews | The website may become outdated, vulnerable or progressively deteriorate. |
| It manages mailboxes and the sending and receiving of messages. | [email protected] | Emails may stop being sent or received even though the website still works. |
A Simple Analogy: Address, Map and Building
We can imagine a company’s digital infrastructure as a physical business:
- The domain is the postal address.
- DNS is the system that indicates how to reach each part of the business.
- Hosting is the building where the business operates.
- The website is what exists inside the building.
- Maintenance ensures that the facilities remain operational.
A company can keep the same address while moving to another building. In the same way, it can keep its domain while changing its hosting.
It can also keep the same hosting while changing only the company that manages the domain. It may even host the website on one server, manage email through another service and control DNS from a third infrastructure.
The analogy is not perfect, but it helps explain a fundamental idea:
having access to the domain does not necessarily mean having access to the hosting, and having access to the hosting does not mean controlling the domain.
What Is a Domain?
A domain is a unique name registered within the global Internet naming system.
For example:
- company.com
- company.es
- shop.company.com
Strictly speaking, the first two are registered domains. The third is a subdomain created within the DNS configuration of company.com.
Registering a domain does not mean purchasing it permanently. What the registrant obtains is the right to use it for a specific period, which can normally be renewed.
Who Is the Domain Registrant?
The registrant is the individual or organization listed as responsible for the domain.
For a business project, we recommend that:
- the company itself is listed as the registrant,
- the recovery email address is controlled by the company,
- the administrative details are kept up to date,
- automatic renewal is configured correctly,
- and more than one authorized person knows where the domain is managed.
An agency or technical team may manage the domain on behalf of the company, but the company should retain ownership and be able to recover access.
What Is Managed Through the Domain Registration Account?
The panel where the domain is registered usually allows the following elements to be managed:
- registrant details,
- the renewal date,
- domain locking and unlocking for transfers,
- the transfer authorization code,
- administrative and technical contacts,
- and the assigned nameservers.
In some cases, the same control panel also allows users to edit DNS records, configure redirects or purchase email and hosting services. However, the fact that these functions appear together in the same interface does not mean that they are technically the same service.
What Happens If the Domain Expires?
When a domain expires, it may stop resolving correctly. As a result:
- the website may become inaccessible,
- corporate email may stop working,
- subdomains may become unavailable,
- and domain-based verification systems may fail.
The hosting may still be active and continue to store all the files. The problem is that the name used to reach that infrastructure is no longer working correctly.
What Is DNS?
DNS stands for Domain Name System.
Its main purpose is to translate names that are easy for people to understand, such as company.com, into addresses and destinations that computer systems can use.
When someone enters company.com into a browser, DNS helps determine which server the browser should connect to.
DNS is not used only for websites. It can also indicate:
- where email is managed,
- which subdomains exist,
- which systems may send email on behalf of the domain,
- how ownership of the domain can be verified,
- or which external services are connected.
What Are Nameservers?
Nameservers indicate where the authoritative DNS zone for a domain is located.
In simple terms:
the domain may be registered in one place, while its nameservers indicate where its DNS configuration must be consulted.
For example, the domain company.com could use the following nameservers:
- ns1.dns-infrastructure.com
- ns2.dns-infrastructure.com
This means that the official DNS records for company.com are managed through the infrastructure associated with those servers.
Why Changing Nameservers Is a Sensitive Operation
Changing nameservers is not the same as simply changing the address of the website.
When the nameservers are changed, the DNS zone answering queries for the domain is replaced. The new zone must therefore contain every required record:
- website records,
- email records,
- subdomains,
- verification records,
- email security policies,
- and any external integrations.
If only the website record is copied and the email records are forgotten, the website may continue to work while emails stop being received.
For this reason, the complete current DNS zone should be copied and verified before changing the nameservers.
The Main Types of DNS Records
| Record | Common purpose | Simplified example |
|---|---|---|
| A | Links a name to an IPv4 address. | company.com → 192.0.2.20 |
| AAAA | Links a name to an IPv6 address. | company.com → IPv6 address |
| CNAME | Makes one name work as an alias of another. | www.company.com → company.com |
| MX | Indicates which servers receive email for the domain. | company.com → mail server |
| TXT | Publishes verification, security or configuration information. | SPF, DKIM, DMARC or verification records |
| NS | Identifies the authoritative nameservers. | company.com → ns1 and ns2 |
| CAA | Indicates which certificate authorities may issue certificates for the domain. | Authorized certificate authority |
A Practical Example
A company may have the following configuration:
- company.com points to the website server through an A record,
- www.company.com points to the main domain through a CNAME,
- the MX records point to the email service,
- a TXT record verifies the domain in an analytics platform,
- another TXT record contains the SPF policy,
- and shop.company.com points to a different ecommerce platform.
All these services use the same domain, but they do not have to be located on the same server.
What DNS Propagation Really Means
After changing a DNS record, it is common to hear that the change “needs to propagate”.
This expression is useful, but it may give the impression that a central system actively sends the new configuration from server to server.
In reality, many resolvers and systems temporarily store DNS responses in a cache. Each record has a value known as TTL, which determines how long that response may be retained before the authoritative source is queried again.
This is why, after a change:
- some users may receive the new response immediately,
- others may temporarily continue using the previous response,
- and different networks may show different results for a period of time.
Reducing the TTL before a migration can help shorten this transition period, but it must be done early enough for the previous TTL value to expire as well.
What Is Web Hosting?
Web hosting is the infrastructure where a website is stored or executed.
Depending on the project, it may include:
- HTML, CSS and JavaScript files,
- images and documents,
- a WordPress installation or another content management system,
- databases,
- applications and server processes,
- activity logs,
- backups,
- and security configurations.
The server receives requests from users and returns the corresponding page or resource.
Which Characteristics Determine Hosting Capacity?
Disk space is only one of the characteristics that should be considered. Other important factors include:
- CPU: the capacity to process operations.
- RAM: the memory available to run processes and applications.
- Storage: the capacity and speed of the storage system.
- Data transfer: the capacity to send data to visitors.
- Database performance: the speed and capacity of queries and connections.
- Software versions: compatibility with PHP, databases and other technologies.
- Scalability: the ability to increase resources as the project grows.
- Security: isolation, protection, updates and monitoring.
- Backups: frequency, retention period and restoration capacity.
- Location and network infrastructure: latency, availability and connectivity.
Two hosting services with the same amount of disk space may provide very different levels of performance.
What Happens When the Hosting Changes?
Changing hosting does not require changing the domain.
A typical migration involves:
- copying the files,
- migrating the database,
- replicating the server configuration,
- testing the website in the new environment,
- updating DNS so that it points to the new server,
- and temporarily keeping the previous hosting active as a precaution.
From the user’s perspective, the website address can remain exactly the same.
Hosting and Website Maintenance Are Not the Same Thing Either
Purchasing hosting means having access to infrastructure where the website can operate. It does not necessarily mean that someone will review, update and maintain the application.
A WordPress installation, for example, may require:
- core updates,
- plugin and theme updates,
- compatibility testing,
- vulnerability reviews,
- database cleanup and optimization,
- uptime monitoring,
- performance reviews,
- backups,
- restoration when a problem occurs,
- and technical support.
These tasks belong to website maintenance, even when they are included within a combined hosting and maintenance plan.
A website may be hosted on a technically operational server and still:
- have outdated plugins,
- display functional errors,
- be vulnerable to attacks,
- load slowly,
- or accumulate problems that nobody is monitoring.
Hosting keeps the infrastructure available. Maintenance looks after the health of the website operating within that infrastructure.
Email Can Be Separate from the Website
Another common misunderstanding is assuming that email must be hosted on the same server as the website.
This does not have to be the case.
A company may have:
- the domain registered on one platform,
- DNS managed through another infrastructure,
- the website hosted on a specialized server,
- and corporate email managed by an independent service.
MX records indicate where email for the domain must be delivered. Other records, normally TXT records, help authenticate messages and reduce domain spoofing:
- SPF: identifies which systems may send email on behalf of the domain.
- DKIM: makes it possible to cryptographically verify the authenticity of messages.
- DMARC: defines how messages that fail certain checks should be handled.
A change of web hosting should not affect email if the corresponding records are preserved correctly.
However, changing nameservers without copying the MX and TXT records may cause email to stop working.
Where Does the SSL Certificate Fit In?
An SSL certificate, or more accurately a TLS certificate, allows a website to operate through HTTPS and encrypts communication between the browser and the server.
The certificate is neither the domain nor the hosting, although it is related to both:
- it is issued for one or more domains or subdomains,
- control over those names must be demonstrated,
- and it must be installed or managed at the point handling the HTTPS connection.
That point may be:
- the web server itself,
- a reverse proxy,
- a load balancer,
- or a content delivery network.
Renewing the domain does not automatically renew the certificate, and renewing the certificate does not renew the domain.
Redirects Are Not DNS Records
This is one of the most important technical distinctions.
DNS connects names to technical destinations, but it does not interpret pages, URL paths or query parameters.
DNS can help old-company.com reach a web infrastructure, but it cannot decide by itself that:
- old-company.com/blue-products
- should send the user to new-company.com/catalogue/blue-products.
To do this, an HTTP redirect response must be generated by:
- the web server,
- the content management system,
- an application,
- a proxy,
- a CDN,
- or a dedicated redirect service.
Permanent and Temporary Redirects
- 301 and 308: normally indicate a permanent change.
- 302 and 307: normally indicate a temporary change.
For a permanent domain or URL migration, permanent redirects are generally configured at server level whenever possible.
Some domain management panels offer a function called “domain forwarding” or “domain redirection”. Although it is configured from the same panel, there is normally a small web service behind it that receives the request and returns an HTTP redirect. It is not performed exclusively through DNS.
Five Common Scenarios
Scenario 1: We Change Hosting but Keep the Domain
The company migrates its website to a new server.
The corresponding A or CNAME record is normally changed so that the website points to the new infrastructure. The domain remains registered in the same place and the nameservers may remain unchanged.
The email records should not be modified if the email service remains the same.
Scenario 2: We Transfer the Domain but Do Not Change the Website
The domain moves from one registrar to another while keeping its current nameservers.
Under normal circumstances, the website and email can continue operating without changes because the DNS zone remains the same.
Transferring a domain and changing its nameservers are two different operations.
Scenario 3: We Change the Nameservers
The new DNS infrastructure must reproduce every existing record before the change is carried out.
It is not enough to copy the main website record. Email, subdomains, verification records and authentication policies must also be preserved.
Scenario 4: We Want an Old Domain to Redirect to a New One
First, the old domain must remain registered and resolve to infrastructure capable of responding to web requests.
That infrastructure must then return a permanent redirect to the equivalent URL on the new domain.
For a correct SEO migration, redirecting every old page to the homepage is usually not sufficient. The recommended approach is to map each old URL to its most relevant new equivalent.
Scenario 5: The Website Works but Email Does Not
If the website loads correctly but messages are not being received, the problem is probably not related to the website’s DNS record.
The following elements should be reviewed:
- MX records,
- mailbox configuration,
- SPF, DKIM and DMARC policies,
- renewal of the email service,
- and mail server logs.
How to Identify Where the Problem Is
| Symptom | Possible affected layers |
|---|---|
| The domain does not respond at all | Domain expiry, nameservers or DNS |
| The website points to an old server | A, AAAA or CNAME record and DNS cache |
| The website returns a 500 error | Server, application, PHP, database or CMS |
| The website loads very slowly | Hosting, application, database, images, cache or external services |
| The browser displays a certificate error | TLS certificate, server, proxy or CDN |
| The website works but email does not | MX/TXT records or the email service |
| An old URL does not redirect to the new one | HTTP redirect configuration |
| Only some users see the old website | DNS cache, TTL, CDN or browser cache |
Who Should Have Access to Each Element?
Professional management is not only about knowing where each service is located. It also requires protecting ownership, access and operational continuity.
The company should maintain an up-to-date inventory indicating:
- where each domain is registered,
- who is listed as the registrant,
- when it is renewed,
- which nameservers it uses,
- where the DNS zone is managed,
- where the website is hosted,
- where email is managed,
- who manages the certificate,
- where backups are stored,
- and which people have administrative access.
We also recommend:
- using corporate accounts instead of employees’ personal email addresses,
- enabling two-factor authentication,
- avoiding the unprotected sharing of passwords by email or messaging apps,
- limiting access according to each person’s responsibilities,
- removing access from former employees and suppliers,
- and documenting every relevant change.
Checklist Before a Migration or Technical Change
- Confirm who the domain registrant is.
- Check the renewal date.
- Identify the current nameservers.
- Export or document the complete DNS zone.
- Locate the website, email and subdomain records.
- Reduce the TTL in advance when appropriate.
- Create a complete backup of files and databases.
- Confirm that the backup can be restored.
- Prepare and test the new hosting before making the change.
- Configure the HTTPS certificate.
- Test forms, payments, integrations and transactional emails.
- Prepare redirects if URLs or domains are changing.
- Temporarily keep the previous infrastructure active.
- Monitor DNS, website availability, email, analytics and organic visibility after the change.
The Importance of Managing the Whole System Without Confusing Its Layers
Domains, DNS, hosting, email, certificates and maintenance can be distributed across several systems.
This is not necessarily a problem. Separating services can provide flexibility, specialization and greater control. However, it also increases the need for coordination and documentation.
Problems arise when:
- nobody knows where each element is managed,
- the domain is registered in the name of a former supplier,
- renewals depend on an expired payment card,
- nameservers are changed without reviewing email records,
- hosting is cancelled before the migration has been completed,
- or a backup is trusted even though it has never been tested.
Good technical management must combine two principles:
- separate each layer conceptually,
- and coordinate them operationally as a single system.
Frequently Asked Questions About Domains, DNS and Hosting
Do I Need a Domain to Have a Website?
Technically, a server can be accessed through an IP address or a temporary URL. However, a public and professional website will normally require a stable, recognizable domain controlled by the company.
Can the Domain and Hosting Be Managed in Different Places?
Yes. This is a completely normal configuration. DNS connects the domain to the server where the website is hosted.
Does Changing Hosting Mean Losing the Domain?
No. The domain and hosting are separate services. The hosting can be changed while keeping the same domain.
Does Transferring the Domain Automatically Change the Hosting?
No. A transfer changes the registrar responsible for maintaining the domain registration. The hosting changes only if the website infrastructure or its DNS configuration is also modified.
Can Changing Nameservers Affect Email?
Yes. Nameservers determine where the complete DNS zone is consulted. If the new zone does not contain the correct MX and TXT records, email may stop working.
Can a DNS Record Create a 301 Redirect?
Not by itself. DNS can direct the domain to a server or service, but the 301 response must be generated at the HTTP layer.
Are Hosting and Website Maintenance the Same Thing?
No. Hosting provides the infrastructure. Maintenance includes the work required to keep the website updated, secure, monitored and operational. Both services may be purchased together.
Does the SSL Certificate Belong to the Domain or the Hosting?
The certificate is issued for a domain, but it must be installed or managed on the server, CDN or system handling the HTTPS connection. It is therefore related to both layers, although it is not the same as either of them.
How Long Does a DNS Change Take?
It depends on the previous TTL, resolver caches and the type of change. Some users may receive the new configuration immediately, while others may temporarily continue receiving the previous response.
Who Should Own a Company’s Domain?
The company itself should be listed as the registrant and retain access to the domain. Technical management can be delegated to an agency or specialist, but ownership and recovery capacity should remain under the company’s control.
We Manage Hosting Without Losing Sight of the Rest of the System
At Mindset Digital, we provide web hosting and maintenance plans that may include domain management, DNS adjustments, hosting, SSL certificates, updates, backups, optimization and technical support.
The aim is not simply to provide server space, but to ensure that the different layers of a company’s digital presence are coordinated, documented and adapted to the real needs of the project.
A stable website does not depend on a single component. It depends on the domain, DNS, hosting, security, application and maintenance working correctly as a whole.
