Nameservers

Nameservers decide who is in charge of your DNS. Your registrar lists two or more nameserver addresses for the domain; whichever company runs those servers is where the records actually live and where you edit them. Records entered anywhere else have no effect. That is the usual cause of confusion when a host's panel shows one set of records and nothing changes: the domain's nameservers point at a different provider.

There are three common setups: nameservers at the registrar, at the web host, or at a CDN or specialist DNS provider. None is wrong. What matters is that everyone working on the site knows which one is in use, because that is the only place where DNS edits take effect, and the wrong panel will happily accept changes that do nothing.

How it works

Nameservers usually have names like ns1.provider.com and ns2.provider.com. The registry for your domain ending stores which nameservers are authoritative for your domain. When a resolver looks up your domain, it is sent to those nameservers, which return the records in the zone they hold.

Registries normally require at least two, often on separate networks, so the domain still resolves if one goes down. Switching nameservers moves the whole DNS zone to a new provider at once, which is why it is a bigger change than editing a single record.

DNS servers come in two kinds. Authoritative nameservers hold the real records for a domain; recursive resolvers, run by internet providers and public services, ask them and cache the answers. If your nameservers sit under your own domain, such as ns1.example.com, the registry also needs their IP addresses, called glue records, or nobody could find the nameservers in the first place.

Example

A clinic's domain is registered at one company, its site is hosted at another and the team wants to put a CDN in front. The CDN provides two nameserver addresses; the owner enters them at the registrar. From then on all DNS edits, for the website, email and verification records alike, happen in the CDN's dashboard and nowhere else.

In practice the switch goes in a fixed order. The team exports or copies the existing zone, recreates every record at the CDN, compares the two lists line by line, lowers the TTL on key records a day ahead, then changes the nameservers at the registrar. Afterwards they use a lookup tool to confirm the new nameservers are being returned and that the website, the MX records and a test email all work. One record is easy to miss: the TXT records that verify the domain with Google Search Console and authorise email senders. If they are not copied, nothing breaks visibly on day one, but email starts landing in spam and Search Console loses access weeks later.

Why it matters for your business

Pointing nameservers at the wrong provider can take down a website and email at the same time, and the effect may not appear for hours. Before switching, copy every existing record into the new provider's zone, especially MX and TXT records for email. Done carefully, choosing a good DNS provider can make changes faster and add protection; done carelessly, it is the single change most likely to cause a full outage.

Common mistakes

• Switching nameservers before recreating the existing records at the new provider.
• Editing DNS records at the host when the nameservers point to the registrar or a CDN.
• Forgetting that a new host's default zone does not include your email records.
• Mixing nameservers from two different providers on the same domain.

Questions people ask

How do I check which nameservers my domain uses?

Use any public DNS or WHOIS lookup tool and search your domain; the nameservers are listed in the result. You can also see them in your registrar's control panel under the domain's settings. The company named in those addresses is where your DNS records are managed.

What is the difference between nameservers and DNS records?

Nameservers are the servers that hold your DNS records. The records themselves are the individual instructions, such as where the website or email lives. Changing nameservers moves the whole set of records to another provider; changing a record adjusts one instruction.

How long do nameserver changes take?

Nameserver changes often take longer than ordinary record edits, because the information is cached at several levels. Many changes are visible within a few hours, but it can take up to a day or two to reach every resolver, so plan the switch for a quiet period.