Nameserver
Nameservers answer DNS questions for your domain: “where does this name point?” If nameservers are wrong, A/MX/CNAME edits in a random panel never reach the public internet.
They usually look like ns1.provider.com and ns2.provider.com. You set them at the registrar (where you bought the domain), not inside site files on the host. Moving hosting does not magically change nameservers — that is a separate step when you want DNS managed elsewhere.
A Simple Analogy
Nameservers are the branch post office that holds the address book for a neighborhood (your domain). Change the branch, and the public starts using a different book — even if the house (hosting files) has not moved. Filling a new address into an inactive branch leaves mail following the old book.
Nameservers vs DNS Records
| Layer | What it controls | Where you set it |
|---|---|---|
| Nameservers | Who is authoritative for the DNS zone | Domain registrar |
| Records (A, MX, TXT, …) | Exact targets (IP, mail, verification) | The DNS panel those nameservers point to |
Common mistake: adding an A record on a new host while nameservers still point at the old provider. The world still reads the old zone, so the site “never moved” even though files already live on the new server.
When You Change Nameservers
- Moving hosts and managing DNS in the new panel
- Using Cloudflare or external DNS
- Registrar DNS is limited, slow, or missing features you need
After a change, wait for propagation. Early mixed results across networks are normal.
Practical Steps
- Export important records (A, MX, SPF/DKIM TXT, CNAME) from the old zone
- Recreate them in the new DNS panel
- At the registrar, switch NS to the values the new provider lists (usually at least two)
- Verify with DNS Lookup after caches cool down
What to Watch For
- Use at least two nameservers exactly as documented
- Export mail records before switching — MX and TXT are easy to forget
- Do not split records across two systems without a cutover plan
- Lower TTL a day ahead so changes show up faster
FAQ
Does changing nameservers move my website files?
No. It only changes DNS authority. Files stay on the current host until you migrate them separately.
How long until new nameservers work?
Often hours; sometimes up to 24–48 hours depending on TTL and ISP caches.
Can registrar, DNS, and hosting be three companies?
Yes — that is common. Keep one DNS zone as the source of truth so records do not fight each other.
NS changed but email broke?
MX/TXT were probably not copied to the new zone. Diff old vs new records and fix them.
Disclaimer: Hosting Wiki articles are prepared for educational and reference purposes. Hosting technology keeps evolving, so some technical details may change over time.