
You’ve been told to “update your DNS.” But your registrar offers two options: change the nameservers, or edit the DNS records. Pick the wrong one and your site — or worse, your email — can go offline. The two are closely related but do very different jobs.
This guide explains nameservers vs DNS records in plain words, when to change each, and the mistakes that break sites.
When someone visits yourdomain.com, a lookup happens in steps:
.com registry): “Who is responsible for this domain?”ns1.provider.com.Think of nameservers as the phone book you’re sent to, and DNS records as the entries inside that phone book.
Nameservers decide which company answers DNS questions for your domain. You set them at your registrar. Common choices:
The active delegation identifies authoritative nameservers. A supported multi-provider design is possible, but it requires coordinated, consistent zone data rather than unrelated records scattered across accounts. For help choosing, see Cloudflare DNS vs Registrar DNS: Which Should You Use?.
DNS records are the actual answers: where the website lives (A, AAAA), aliases (CNAME), where email goes (MX), and verification and email security (TXT). You edit them inside the DNS zone at whichever provider your nameservers point to.
Here’s the key point: editing records at a provider that isn’t your active nameserver does nothing. The world never asks that provider. A full breakdown of each type is in DNS Record Types Explained: A, AAAA, CNAME, MX and TXT.
Change DNS records when:
Change nameservers when:
Pointing a domain to hosting for the first time? Follow How to Point a Domain to Your Hosting.
The Cloudflare nameserver documentation explains the authoritative role, while its DNS record overview introduces the data published there. Use your own provider’s instructions for the controls in your account.
A business may buy its domain from one company, host its website with another and use a third company for mail. A fourth service may operate authoritative DNS. These roles can also belong to the same provider, but do not assume they do. Write each role beside the account and support contact that manages it.
The registrar manages the registration and the interface for the domain’s delegation. The active DNS service publishes the relevant zone data. The web host serves the application, and the mail provider handles its supported messaging workflow. Nameservers connect the public lookup process to the authoritative data; they do not automatically move application files or mail history.
Keep this account map with the domain documentation. If an agency manages the services, confirm that the business knows how ownership and support are handled. A technical problem is harder to resolve when nobody can identify which provider actually controls the setting that needs attention.
Review the domain’s delegation in the registrar account and compare it with public DNS observations. Tools such as dig and nslookup can help inspect the relevant records. Record the exact domain and the answering service, especially if a recent change is still being investigated.
A web-hosting panel can display a DNS zone even when that provider is not authoritative for the domain. Editing that inactive copy will not necessarily change public answers. Before saving a record, confirm that you are using the active service rather than an old or automatically created zone.
If public observations differ from the expected delegation, preserve the result and review recent changes with the registrar or DNS provider. Do not repeatedly replace nameservers simply because one lookup looks unfamiliar. Establish the current state before deciding what the desired state should be.
Moving a website to a new server can often be handled through the required address or alias records while the DNS provider remains the same. The host should supply the appropriate destination information. The change should match the actual application setup, including any proxy or CDN involved.
Moving authoritative DNS changes where the zone is served. That requires preparation of the relevant record data at the new service and coordination of the delegation. The new website may be only one of several services depending on the zone. Keep mail, verification and other application records in the inventory.
Nameservers should therefore not be changed as a reflex whenever someone says the site is moving. Ask what is actually changing and which provider requires the operation. A clear description of the move prevents an unnecessary DNS-provider migration from being added to a straightforward hosting project.

Prepare a list of the hostnames and record types used by the business. Include the main website, important subdomains, mail routing, authentication and verification entries. Record the purpose of each entry where known. An unexplained value should be investigated rather than discarded because it does not resemble a website address.
Automatic import can be useful, but review the result. It may not capture every record or the provider-specific behavior needed by a service. Compare the destination zone with your inventory and the instructions from each relevant platform. Keep the original configuration available through the transition.
When changing nameservers, assign someone to check each important service. One person can verify the website while another checks the mail workflow. The business should not declare the whole domain healthy because only the home page loads.
The website and mail service can use different providers without a problem when DNS is configured correctly. A website address does not identify the correct MX destination. Use the mail provider’s exact organization-specific settings and preserve the associated authentication records as required.
If the site still works but incoming mail fails after a delegation change, compare the active zone with the mail inventory. Check whether the expected records were copied and whether the record names are correct. Do not point mail routing at the website host unless the mail setup actually requires it.
Nameservers affect where the public DNS data is obtained, but they do not transfer mailboxes. A mail migration needs its own account, data and cutover plan. Keep that work distinct from the zone change so a missing historical message is not confused with a routing error.

If the domain uses DNSSEC, include it in the transition plan. The parent delegation and signing information must remain consistent with the authoritative service. Use the documented process for the providers involved rather than copying a generic sequence without checking its assumptions.
Some migration approaches involve a temporary change to the parent DS information, while supported coordinated designs can follow a different path. Get the procedure from the responsible providers and schedule the validation checks. A short website-record TTL is not a substitute for a DNSSEC migration plan.
After the new nameservers are active, verify the intended validation state as well as the ordinary records. A resolving address and a valid chain of trust are different checks. Preserve diagnostic results if the provider needs to investigate an unexpected failure.
A registration transfer changes the company managing the domain registration. It does not necessarily require a change in authoritative DNS. Confirm whether the existing nameservers and related settings will be preserved before starting. Ask where those settings will be managed after the transfer.
Keep renewal arrangements, contact ownership and account recovery in the transfer checklist. These organizational details matter even if the website remains online. A successful transfer should leave the business able to manage the domain and contact the correct support team.
If registration, DNS and hosting all change together, document each component and its order. Avoid treating them as one invisible operation. Nameservers are one part of that project, and keeping the responsibilities clear makes troubleshooting much easier.

Different resolvers can hold information obtained at different times. A public lookup may therefore show a different stage of a change from another network. Record the answering service and the time instead of assuming all visitors use one global countdown.
A record’s previous TTL matters for data already cached. Delegation caching also needs consideration when the authoritative provider changes. Follow the provider’s migration instructions and verify the actual outcome. Do not promise that every service will switch within a fixed number of minutes.
Keep old services available for the planned overlap where practical. Coordinate the final data synchronization for applications that accept writes, such as stores or membership systems. Nameservers do not synchronize databases, and a functioning DNS transition does not prevent application data from diverging.
Start with the exact affected hostname and record type. Compare the active answer with the intended destination, taking proxies and managed services into account. Then test the real application. A correct DNS response does not prove that the destination has the right virtual host, certificate or database.
For the website, check important pages and a controlled form submission. For mail, use accounts you control and inspect the relevant sending or receiving evidence. For verification records, use the requesting service’s own check. Keep these results in the migration log.
If a test fails, identify which layer is responsible before editing more records. Preserve the original symptom and the change timeline. A narrow correction followed by the same test gives clearer evidence than several speculative edits across different accounts.
Give the provider the public domain, the service affected and the exact time of the problem. Include the expected result and the observation that differs. State whether nameservers, hosting or mail settings recently changed. This helps support start at the appropriate component.
Share relevant public lookup results where appropriate, but review internal details and credentials before sending logs. Account passwords and private recovery information are not needed in a public discussion of DNS records. Use the provider’s approved support channel for account-specific investigation.
Ask support to explain which account or interface should hold the correction. Record that explanation with the account map so the next administrator does not repeat the same search through several inactive zones.
Imagine a business with a domain at its registrar, DNS at a managed provider, a website on shared hosting and mail in a separate service. The website moves to a new host. The team identifies the website records supplied by the new host and updates those at the active DNS provider. The nameservers can remain unchanged if the chosen design supports it.
Later, the business chooses another authoritative DNS service. This time the team prepares the full zone, reviews the signing setup and plans the delegation change. It checks both website and mail afterward. The two projects involve the same domain but different operations.
This example shows why instructions should identify the task, not merely say to update DNS. A precise request explains whether you are changing nameservers or editing record data, which account is responsible and how the result will be tested.
Promotional recommendation: If you need a domain, hosting or business email service, consider KAWEDMA to review the available options. For mailboxes on your own domain, compare KAWEDMA’s professional email service with your storage, client and migration requirements. Ask which nameservers or record changes the chosen setup requires and who will maintain the zone. Confirm the service scope and support responsibilities before moving an existing domain.
No. It changes the authoritative DNS arrangement. The website application and its data need their own hosting or migration process.
Yes. Identify each role and manage records at the service that is authoritative for the relevant zone.
Do not assume an arbitrary mixture is a supported design. Multi-provider DNS requires coordination and consistent data. Use the documented architecture for the services involved.
A record edit does not migrate mailbox contents. Preserve the mail configuration and plan any mail-service move separately.
Record the old and new configuration, the purpose, the time, the owner and the verification results. That gives another administrator enough context to investigate without guessing.
Before a planned change, use our TTL planning guide to understand caching, then follow the dig and nslookup checks to record the answers you actually observe.
After the change, review the documentation with the person responsible for the business website. They should know which provider controls registration, which nameservers serve the zone and which services handle website and mail traffic. Update old notes that point to an inactive DNS panel.
Keep a review date and the support route beside each role. When a contractor or employee leaves, follow the approved handover process so the organization retains access. Clear account ownership does not replace technical checks, but it makes those checks much easier to act on when a service fails or another move is planned.
Review the account map again before a future domain or hosting migration.
We may earn a commission on purchases made through these links, at no extra cost to you.
Don’t miss the chance to participate in the biggest giveaway of this year.