Nameservers, zones and records: the difference

Reviewed on September 8, 2026 2 min read dns zonas dns

Nameservers (DNS servers) tell the world where to look up a domain's configuration. The DNS zone holds that configuration, and each record does a specific job: the website's address, where email goes or a verification.

Element	Example	Where you change it
Nameservers	`ns1.theservercluster.com`	With the domain's registrar
DNS zone	Set of records for `ejemplo.com`	With the authoritative DNS provider
A or AAAA record	The website's IP address	Inside the zone
MX record	Server that receives email	Inside the zone
TXT record	SPF or a service verification	Inside the zone
CNAME record	Alias that points to another name	Inside the zone

Example: website at Hostsuar and email with another provider

You can keep your website here and use Google Workspace or Microsoft 365 for email. The website records and the MX records do different jobs. You don't need to transfer the domain or change the nameservers just to change your email: edit the records you need in the zone that is queried publicly.

If you use Cloudflare as your DNS provider, creating a TXT record only in cPanel doesn't publish it in Cloudflare, even though the panel saves the change.

Which option you need

To have another provider manage the whole zone, change the nameservers, setting up its records first.
To point a website, verify a domain or set up email, edit the records wherever the authoritative DNS is.
If a provider gives you several records, the DNS assistant helps you review their impact.

DNS returns data; on its own it doesn't redirect a page to another URL or copy content. Caching can keep an old answer: saving a change and seeing it from every connection happen at different times.