---
title: Nameserver
description: Authoritative DNS servers that answer where your domain points. Wrong nameservers mean A/MX edits elsewhere never go public.
canonical: https://penasihathosting.com/en/hosting-wiki/nameserver
type: wiki
locale: en
updated: 2026-07-15
author: Willya Randika
---

# Nameserver

## Overview

- **Summary:** Authoritative DNS servers that answer where your domain points. Wrong nameservers mean A/MX edits elsewhere never go public.
- **Author:** Willya Randika ([profile](/penulis/willya-randika))

## Article

**Nameservers** answer [DNS](/en/hosting-wiki/dns-domain-name-system) 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](/en/hosting-wiki/cloudflare) or external DNS  
- Registrar DNS is limited, slow, or missing features you need  

After a change, wait for [propagation](/en/hosting-wiki/domain-propagation). Early mixed results across networks are normal.

## Practical Steps

1. Export important records (A, MX, SPF/DKIM TXT, CNAME) from the old zone  
2. Recreate them in the new DNS panel  
3. At the registrar, switch NS to the values the new provider lists (usually at least two)  
4. Verify with [DNS Lookup](/en/tools/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](/en/hosting-wiki/dns-ttl) a day ahead so changes show up faster  

## FAQ

<Accordion>
  <AccordionItem title="Does changing nameservers move my website files?">
    No. It only changes DNS authority. Files stay on the current host until you migrate them separately.
  </AccordionItem>
  <AccordionItem title="How long until new nameservers work?">
    Often hours; sometimes up to 24–48 hours depending on TTL and ISP caches.
  </AccordionItem>
  <AccordionItem title="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.
  </AccordionItem>
  <AccordionItem title="NS changed but email broke?">
    MX/TXT were probably not copied to the new zone. Diff old vs new records and fix them.
  </AccordionItem>
</Accordion>