Nameservers vs DNS records: what's the difference?

Two support teams, two instructions, both apparently correct. Your web host asks you to “point the nameservers to us”. Your email provider asks you to “add these MX records”. You do one, then the other, and something stops working. The confusion behind almost every such incident is the difference between nameservers vs DNS records, and the idea that ties them together is authority: at any moment, exactly one set of servers is in charge of answering questions about your domain.

The three companies involved in one domain

Most small businesses assume the company that sold them the website controls everything. In practice up to three separate roles exist, sometimes filled by one provider and sometimes by three.

The registrar

Where the domain is registered and renewed. The registrar holds the ownership record and, crucially, the list of nameservers for your domain. It may not host anything at all.

The DNS host

Whoever runs the nameservers that actually answer lookups. This could be your registrar, your web host, or a third party such as a CDN. This is where the individual records live.

The web host

The server where your site's files and database sit. It has an IP address, which is what a record needs to point at, but it has no say in your domain unless it is also the DNS host.

Write down which company plays each role for your domain. That single list resolves most support confusion before it starts.

What nameservers do

Nameservers are addresses like ns1.provider.com and ns2.provider.com, usually two to four of them. They are set at the registrar, not inside your DNS panel, and their job is to say which organisation's servers hold the authoritative answers for your domain.

When a visitor's resolver looks up your website, it asks the domain system who is authoritative for your name. The answer is your nameservers. Only then does it ask those servers for the specific record it needs.

So nameservers are the pointer to the filing cabinet. They contain no A records, no MX records and no site content. Changing them does not edit any record; it changes which set of records the world will read.

What DNS records do

Records are the contents of that cabinet: the individual answers for each name and service. A record for the website, MX records for mail, TXT records for verification, and so on.

They live in a zone hosted by whichever provider your nameservers point to. This is the heart of the confusion: you might have records defined in three different panels, but only the panel whose nameservers are currently selected is being used. The others are ignored, sitting there looking convincing.

The mistakes this misunderstanding causes

• Editing the wrong panel. You update the A record at your registrar for an hour with no effect, because the nameservers point at your web host and the live zone is there.
• Changing nameservers to fix one service. Moving nameservers swaps the entire zone at once, so a change intended for the website also replaces your mail records.
• Expecting nameservers to move the site. They do not copy files. If the new host has no copy of your site, pointing nameservers at it produces a placeholder page.
• Partial CDN setups. Services such as Cloudflare become your DNS host when you use their nameservers, so from then on records must be edited there, not at the registrar.
• Two providers each convinced they control the domain. Both are describing their own panel honestly; only one is authoritative.

How to find out which panel is actually in charge

1. Log in to your registrar and look at the domain's nameserver setting. Note the hostnames exactly.
2. Match those hostnames to a company. If they end in your web host's domain, records live at the web host. If they belong to a CDN or DNS service, they live there.
3. Confirm from outside with a public DNS lookup tool, asking for the NS records of your domain. What the internet returns is the truth, whatever a panel shows you.
4. Open the matching panel and check that the records you expect are present, particularly A and MX.
5. Write it in your documentation: registrar name, nameserver values, DNS host, web host, and who holds each login.

If the returned nameservers belong to a company nobody in the business recognises, stop and investigate before editing anything. That is often an old agency's account.

Which one should you change, and when?

Use this as a rule of thumb.

• Change a record when you are moving one service while the rest stays: a new web server, a new mail provider, a verification string for a marketing tool, a new subdomain.
• Change nameservers only when you want a different company to manage the whole zone, such as adopting a CDN or consolidating everything with one provider.
• Never change nameservers casually. Because it swaps the entire zone, it is the single riskiest edit available in a domain panel, and it affects email as much as the website.

There is also a middle path many people miss: you can keep your nameservers where they are and simply edit the records to point at a new host. Moving a website does not require moving DNS at all.

Map your domain this week

Take ten minutes to produce the four-line map: registrar, nameservers, DNS host, web host. Keep it with your recovery documentation and share it with whoever manages your site. Next time a provider asks you to change something, you will know immediately which panel they mean and what else that change will touch. If you would like a second opinion before a migration, you can ask our team to look at your current setup first.

Frequently asked questions

Can I use one company's nameservers and another's hosting?

Yes, and it is very common. Keep DNS wherever it is, and simply point the A record at the new host's IP address. Only the records need to change.

How many nameservers should a domain have?

At least two, for redundancy. Your provider gives you the exact list; enter all of them and do not mix nameservers from two different providers.

Do I lose my DNS records when I change nameservers?

The old records are not deleted, but they stop being used. The new nameservers serve their own zone, so anything not recreated there effectively disappears from the internet.

Why does my provider say the domain is not pointing to them?

Usually because the nameservers still point elsewhere, or because the record was edited in a panel that is not authoritative. Check the live NS records from outside before troubleshooting further.