What Are Nameservers and What Do They Do?

Nameservers identify the DNS servers authorised to provide official answers for a domain. When a resolver needs information about example.com, the DNS hierarchy directs it to the nameservers assigned to that domain.

Why a domain needs nameservers

Internet services need an authoritative source for website addresses, mail routes, and verification records. Domains usually list at least two nameservers for resilience. Those servers may belong to the registrar, a dedicated DNS platform, or the hosting provider.

Nameservers are not DNS records

Nameservers answer who manages the DNS zone? Records such as A, AAAA, CNAME, MX, and TXT answer where is each service? Editing a record inside the current zone does not require a nameserver change. See the complete DNS overview for the whole lookup path.

Registrar, DNS provider, and hosting provider

The registrar maintains the domain registration and delegation. The DNS provider hosts the authoritative zone. The hosting provider supplies web or application resources. These may be the same business or separate businesses, so first determine which control panel is authoritative.

When a nameserver change makes sense

• You are moving the entire DNS zone to another provider.
• The new provider will manage all website, email, and verification records.
• A service explicitly requires its authoritative nameservers and the implications have been reviewed.

Recreate every required record in the new zone before changing delegation.

When it is not required

Moving only a website normally needs an A, AAAA, or CNAME change. Moving email normally changes MX and related TXT records. Replacing nameservers unnecessarily can remove working records that were never copied to the new zone.

What happens after a change

The registrar updates the delegation, and resolvers gradually begin querying the new authoritative set. Cached information can cause some users to reach the old service for a while. This behaviour is explained in the DNS propagation guide.

A pre-change checklist

• Export or document the current zone.
• Create required A/AAAA, CNAME, MX, and TXT records at the destination.
• Validate website, SSL, email, and verification requirements.
• Choose a low-risk change window and keep a rollback plan.

Changing delegation is a broad infrastructure action. If the goal is simply to point a website elsewhere, preserve the existing nameservers and change the relevant website record instead.

A decision example

Suppose the registrar is Company A, DNS is hosted by Company B, and a new website runs at Company C. The nameservers can remain at B while only the A record changes. They need to move to C only if the authoritative zone is also being transferred.

Delegation and authoritative DNS

Delegation is the information that connects a registered domain to its authoritative nameserver set. The registry for the TLD publishes which servers are responsible, allowing recursive resolvers to reach the correct zone. Those nameservers do not need to run on the web server and commonly belong to a separate, globally distributed DNS platform.

Domains normally list at least two nameservers so DNS answers remain available if a server or network path fails. Two hostnames alone do not provide real resilience: each server must answer authoritatively for the domain and publish a consistent zone.

Changing delegation versus changing a record

If only the website moves, editing A, AAAA, or CNAME within the current zone is usually sufficient. If only mail moves, the relevant MX and TXT records change. Replacing nameservers transfers control of the whole zone and can affect every service, so it is a broader action rather than a shortcut for routine hosting changes.

What must be ready in the new zone

Before updating delegation, compare the apex and www records, IPv4 and IPv6, MX priorities, SPF, DKIM, DMARC, verification records, and important subdomains. Confirm that the new nameservers return the expected authoritative answers and that the destination hosting recognises every hostname. Keep an export or reliable record of the previous zone for recovery.

When keeping the current nameservers is safer

If the present DNS provider is reliable and only one destination needs to change, leaving delegation untouched reduces the scope of the operation. The same principle applies to a registrar transfer: moving registration does not by itself require moving DNS or hosting.

What a delegation check actually proves

Looking up a domain’s nameservers tells you which DNS provider is authoritative; it does not prove that every record inside the zone is correct. A successful delegation can still contain a wrong web IP, missing MX records, or incomplete verification records. Conversely, a hosting change may require only an A or CNAME update while delegation stays untouched. This distinction helps teams avoid changing nameservers merely because a website moved, and it narrows troubleshooting to either the delegation layer or the records within the active zone.

Frequently asked questions

Does a registrar transfer change nameservers?

Not necessarily. A planned transfer can preserve delegation and hosting.

Do nameservers host the website?

No. They publish DNS answers; the web server hosts content.

Which dashboard should I use?

Identify the active authoritative nameservers and their provider. The effective zone must be managed there.