What is a nameserver?
A nameserver is the authoritative DNS server that holds a domain's records and answers queries for that zone. The registrar publishes at least two nameserver hostnames so resolvers know where to ask. Record edits in any other panel never reach the public internet until the nameservers point to that DNS host.
For site owners moving hosting, adding Cloudflare or fixing email, who need to know which nameservers are live and how to change them safely.
knowledge
- Read time
- 6 min
- Sections
- 8
- Updated
- 14 Nov 2026
- Written by
- WebJi® team
Last editorial update: 14 November 2026.
What does a nameserver actually answer?
A nameserver is the authoritative DNS server for a domain's zone: when a resolver asks about that domain, it replies with the records stored there, such as the website's IP address, the mail host and verification text. It answers only for the zones it hosts, not for the whole internet.
Every domain lists at least two nameserver hostnames, often called ns1 and ns2, so a second server can answer if the first is down. Both must serve the same zone. Most registrars refuse to save a single hostname.
How is a nameserver different from DNS and a resolver?
DNS is the whole lookup system, a recursive resolver asks questions on behalf of a device, and the authoritative nameserver holds the zone and gives the final answer for one domain. People call all of them "DNS servers", which causes most of the confusion.
| Piece | What it does | Where you change it |
|---|---|---|
| Authoritative nameserver | Holds the zone and answers for that domain | At the registrar, as a hostname pair |
| DNS record | One row in the zone, such as the site address or mail host | At the DNS host the nameservers point to |
| Recursive resolver | Asks on behalf of a device and caches replies | On the device or network, not on the domain |
Setting your laptop to 1.1.1.1 changes only your laptop's resolver; it does not change any domain's nameservers. The full lookup chain is in what is DNS, and each record type in DNS records explained.
Where is a domain's nameserver pair stored?
The nameserver pair is stored at the registry, and you edit it through the registrar — the company you renew the domain with. Editing records in a hosting panel changes nothing the public sees if the live nameservers point at a different DNS host.
Replacing the pair is not a domain transfer; the name stays at the same registrar. On a WebJi® registration the fields sit in the client area for domain registration, and the clicks are in how to change nameservers. If the fields are locked, email support@webji.services, answered 24/7 in Hindi and English.
What is the difference between default, custom and private nameservers?
Default nameservers are the pair already filled in by the registrar or host, custom nameservers are hostnames you paste from the DNS host you chose, and private nameservers are hostnames on your own domain.
- Default: a domain bought at any registrar starts on that registrar's own pair until you replace it. A free hosting account has its own pair too; read it in the account rather than guessing from the brand name.
- Custom: for example, the two hostnames Cloudflare assigns, or your hosting provider's pair from its welcome email. On WebJi® hosting, use the pair stated in your welcome email or client area.
- Private (vanity): such as ns1.yourbrand.in, used by resellers who want their brand on the pair; see how to create private nameservers.
How do you see which nameservers a domain uses?
Compare the registrar's nameserver field with a public NS lookup; when both list the same hostnames, that pair is live.
- Open the domain at the registrar and read the nameserver field — that is what the registry was told to publish.
- Run a public lookup or a WHOIS lookup and read the Name Server lines.
- From a terminal:
dig NS example.in +short, or on Windowsnslookup -type=NS example.in. To ask one public resolver:dig @1.1.1.1 NS example.in +short. - Match the hostnames to your hosting welcome email. If they differ, the zone in your hosting panel is not the public one.
What happens when the nameservers are wrong?
A wrong pair sends visitors and mail to a DNS host that does not hold your zone, so the site can fail, email can bounce, and edits in the panel you trust stay invisible.
A typo, a single hostname or a new DNS host with an empty zone all look like a down site. If you still have the previous pair, put it back, build the zone properly, then switch again. Many networks show a new pair within a few hours; some keep the old answer for up to 48 hours. New hostnames on one lookup and old ones on another means the change is published and caches are catching up.
How do you change nameservers without breaking email?
Rebuild every record in the new zone first, lower TTLs a day ahead, then replace the pair at the registrar — because switching nameservers moves the website and the mail together.
- Copy every record into the new DNS host: A, AAAA, CNAME, MX, TXT (SPF, DKIM, DMARC) and any SRV records.
- A day before the move, lower the TTL on important records to 300 seconds.
- Replace the pair at the registrar and save.
- Confirm with
dig NS example.in +short, then test the site and send a test email both ways.
Mail is the usual casualty: a new zone with no MX record bounces mail while the website still loads.
| Role | What it does | Usually |
|---|---|---|
| Primary | Holds the master copy of the zone; records are edited here and the SOA record names it | ns1 |
| Secondary | Copies the zone from the primary by zone transfer and answers queries; not where you edit | ns2 |
What are glue records and subdomain delegation?
A glue record is an A or AAAA record held at the parent registry that gives the IP of a nameserver whose hostname sits inside the domain it serves, such as ns1.yourbrand.in for yourbrand.in. Without glue, a resolver could never find the server holding the answer.
A subdomain can also carry its own NS records, handing that child zone to another provider: shop.example.in can run on a different DNS host while the main site stays where it is.
- Not SNI: Server Name Indication is the hostname a browser sends in TLS so one IP can serve many certificates; it has nothing to do with delegation.
- Not a server hostname: a name used for FTP, SSH or mail settings identifies a machine; it does not publish the zone.
- Not the registrar's brand: a domain bought at one company can point at another company's nameservers.
Frequently asked questions
Do I need to change nameservers to use new hosting?
Not always. You can either point the nameservers to the new host, which moves all DNS there, or keep your current DNS host and only change the A record for the website. The second option leaves email records untouched.
Can I use more than two nameservers?
Yes. Many DNS providers publish four or more, spread across different networks, for extra resilience. Enter all of them at the registrar; every one must serve the same zone.
Why does the registrar reject my nameserver hostname?
Usually because the hostname does not resolve, is misspelled, or is a private nameserver on your own domain with no glue record registered yet. Register the glue IPs first, then save the pair.
Does changing nameservers affect SEO?
Not if the new zone has the same records. Rankings depend on the site staying reachable; a careful switch with lowered TTLs and a complete zone causes no lasting effect, while a broken zone can cause crawl errors until fixed.
Last editorial update: 15 November 2026.
Ready to get started with WebJi®?
Join 12,000+ businesses across India and overseas. INR pricing, 18% GST shown before payment and 24/7 email support in Hindi and English — average first reply under 60 minutes.