“Do I change my nameservers or my DNS records?” It is one of the most common — and most confusing — questions for anyone managing a domain. The two sound similar, they are found in the same corners of your control panel, and getting them mixed up leads to changes that mysteriously do nothing. But the distinction is actually simple once you see it clearly, and understanding it removes a huge amount of DNS confusion.

This guide draws a clean line between nameservers and DNS records: what each one is, a simple analogy that makes it stick, where each is set, and the practical rule for knowing which to change in any situation. You will leave able to answer that opening question instantly for your own domain, and confident about which lever to pull for any change you need to make.

The core difference in one line

Here is the whole distinction in a sentence: nameservers are the servers that store your domain’s settings, while DNS records are the individual lines of data inside those servers that direct your web and email traffic. Nameservers are the container; records are the contents.

A nameserver is a specialised server that answers the question “where does this website live?” and acts as the authoritative source for your domain. DNS records are the specific instructions written inside that nameserver — the ones holding data like IP addresses, mail servers, and verification codes that route different kinds of traffic.

So they operate at different levels. Nameservers are the higher-level setting that determines who holds and serves your domain’s records; the records themselves are the lower-level details of what points where. Change the nameservers and you change who is in charge; change a record and you change one specific destination.

What a nameserver is

A nameserver is the authoritative server for your domain — the place the internet goes to ask where your domain’s traffic should be directed. It is set at your registrar, and it points to your hosting provider or DNS service, effectively saying “for this domain, this server has the answers.”

Think of it as naming the authority. When you set your domain’s nameservers to a particular provider, you are declaring that provider the keeper of your domain’s records. Every lookup for your domain ultimately consults those nameservers to find the current settings.

This is why nameservers are the big-picture control. They do not, by themselves, say what your website’s address is or where email goes — they say who holds that information. The actual addresses and routing live in the records stored on them.

What DNS records are

DNS records are the specific entries written inside a nameserver, each carrying a piece of routing information for your domain. They are the details: the data like IP addresses, mail-server locations, aliases, and text verifications that tell traffic exactly where to go.

The common types make this concrete. An A record connects your domain to an IP address for your website; an MX record sends email to the correct mail server; a CNAME creates an alias pointing one name to another; and a TXT record holds verification codes and security settings for services. Each record governs one aspect of your domain’s behaviour.

So while the nameserver is the authority, the records are the instructions that authority carries out. Editing a record changes one specific thing — where your site points, where your email goes — without changing who manages your DNS overall.

An analogy that makes it stick

Picture a filing cabinet. The nameserver is the cabinet itself — the container that holds all your domain’s information and is located in a particular office (your host or DNS provider). The DNS records are the individual files inside it, each one an instruction for a specific kind of traffic.

If you want to move all your files to a different office, you change which cabinet is in charge — that is changing your nameservers. If you just want to update the contents of one file — say, change the address your website points to — you edit that record inside the existing cabinet.

Or, in the phone-book framing: the nameserver is the publisher who produces and holds the directory, while the records are the individual listings within it. Change the publisher (nameservers) and you move where the whole directory is kept; change a listing (record) and you update one specific entry.

Where each is set

The two are managed in different places, which is another key to keeping them straight. Here is how they line up:

Notice the second row: nameservers are set at your registrar, but records are edited at whoever your nameservers currently point to. That is why editing records in the wrong place fails — the records only count on your active nameservers.

The practical rule: which do you change?

Here is the rule that answers the opening question every time. If you want to move where your DNS is managed — for example, hand DNS control to a new host or a specialised DNS service — you change your nameservers, at your registrar. That is a big-picture change of authority.

If you want to change what something points to — update your website’s server, set up or change email, verify a service, add a subdomain — you edit a DNS record, at whatever provider currently holds your nameservers. That is a fine-grained change of a specific destination.

So ask yourself: am I changing who controls my DNS, or what a specific thing points to? “Who” means nameservers; “what” means records. This single question resolves nearly every case of confusion between the two.

Why editing in the wrong place fails

A classic frustration is editing DNS records and seeing no effect. The reason is almost always that the records were changed in a place that is not the domain’s active nameserver. Records only take effect on the nameservers your domain currently uses, so editing them anywhere else is like updating files in the wrong cabinet.

For example, if your domain’s nameservers point to your host, but you edit records in your registrar’s DNS panel, nothing changes, because the registrar’s records are not the ones being consulted. The fix is to make record edits at whichever provider your nameservers point to.

This is exactly why understanding the nameserver-versus-record distinction is so practical. Knowing that nameservers decide where records live tells you precisely where to go to make any given change — and stops you editing settings that will never take effect.

A quick decision guide

To make it effortless, here is the decision boiled down. Moving your whole site’s DNS to a new host or DNS service? That is a nameserver change, made at your registrar — and remember to set up your records at the new provider first.

Adding email, verifying a service with a TXT record, pointing your website at a new server IP, or connecting a subdomain to a service? Those are all record edits, made at whoever holds your active nameservers. You are adjusting a specific destination, not the overall authority.

Keep the container-versus-contents image in mind and the decision becomes automatic. Nameservers are the where; records are the what. Once that clicks, managing your domain — and knowing exactly which setting to touch — becomes genuinely simple.

FAQs

What is the difference between nameservers and DNS records?

Nameservers are the servers that store your domain’s settings and decide where your DNS is managed; DNS records are the individual entries inside them that direct specific traffic like your website and email. In short, nameservers are the container that decides WHERE your DNS lives, and records are the contents that decide WHAT your domain points to.

Do I change nameservers or DNS records?

Change nameservers (at your registrar) when you want to move where your DNS is managed — for example, handing control to a new host or DNS service. Edit DNS records (at whoever holds your active nameservers) when you want to change what something points to, such as your website’s server, email, or a verification. Ask: who controls DNS, or what points where?

Which comes first, nameservers or DNS records?

Nameservers come first conceptually: they decide where your DNS is managed, and your records live on whichever nameservers your domain uses. So you set nameservers to choose the authority, then manage records there. When moving to a new provider, set up your records at that provider before switching nameservers so nothing breaks in the transition.

Why don’t my DNS record changes take effect?

Almost always because you edited them somewhere other than your domain’s active nameserver. Records only count on the nameservers your domain currently points to, so editing them elsewhere — like your registrar’s panel when your nameservers point to your host — does nothing. Make record changes at whichever provider holds your active nameservers.

Can I edit DNS records without changing nameservers?

Yes — that is the normal case. As long as your nameservers already point where you want your DNS managed, you simply edit records there to change what your domain points to, with no nameserver change needed. You only change nameservers when you want to move DNS management to a different provider entirely.

Is a nameserver a DNS record?

Not quite. A nameserver is the server that holds your DNS records, while your domain’s use of specific nameservers is recorded as NS records at the registry level. In everyday terms, treat nameservers as the container that decides where DNS is managed, and DNS records (A, MX, CNAME, TXT) as the entries inside that direct your traffic.

The bottom line

The difference between nameservers and DNS records comes down to container versus contents. Nameservers are the servers that hold your domain’s settings and decide where your DNS is managed; DNS records are the individual entries inside them — A, MX, CNAME, TXT — that direct your website, email, and other traffic. Nameservers answer “where does this domain’s information live?” and are set at your registrar; records answer “what does this specific thing point to?” and are edited at whoever your active nameservers point to.

That distinction yields a simple, reliable rule: if you are changing who controls your DNS, you change nameservers; if you are changing what something points to, you edit a record. It also explains the most common frustration in DNS — editing records in the wrong place and seeing no effect — because records only take effect on your active nameservers. Picture the filing cabinet and its files, ask whether you are moving the cabinet or updating a file, and you will always know which setting to touch.

When you are ready, you can start with Hostinger and use code PROTIPS for the reader discount. Nameservers decide WHERE your DNS is managed (set at your registrar); DNS records decide WHAT your domain points to (edited at your active nameservers). Container vs contents — change nameservers to move control, edit records to change a destination.