What a name server is
A name server is the DNS server that holds one zone's records and answers queries about them, which makes it the authoritative source for that domain. A registrar publishes two or more, such as ns1.example.net and ns2.example.net, so a lookup still resolves when one server is down.
Your domain's delegation points at those hostnames, not at an IP address. Everything else — the A record, MX, TXT, SRV — lives inside the zone that the name servers answer from.
- The NS record type stores a name server hostname for a zone.
- Two NS hostnames are the minimum worth having; most registrars require at least two.
- Changing the pair at the registrar moves the whole zone, including mail, in one step.
Authoritative, recursive, primary and secondary
Four labels get mixed up. Two describe the role in a lookup, and two describe the role inside a zone.
| Role | What it does | Example |
|---|---|---|
| Authoritative | Answers for the zones it hosts, with the AA bit set | ns1.example.net for example.com |
| Recursive resolver | Looks answers up on behalf of a client and caches them | 1.1.1.1, your ISP's resolver |
| Primary | Holds the master copy of the zone, named in the SOA record | ns1, where records are edited |
| Secondary | Copies the zone from the primary by transfer | ns2, read-only mirror |
A recursive resolver is not the name server for your domain; it is the middleman that asks yours. That is why clearing a local cache does not change delegation, and why an authoritative server refuses queries for zones it does not host.
Find the name servers for a domain
Three places show the same pair, and they should agree. If the registrar shows one pair and the command shows another, the change has not reached the registry yet.
- Run
dig NS example.com +shorton any Linux or macOS machine. Windows users can runnslookup -type=NS example.com. - Run
whois example.comand read the Name Server lines, which come from the registry. - Open the registrar panel, whether the domain was bought at GoDaddy, Bluehost or here, and read the name server fields on the domain's DNS page.
You know it is right when the command returns two hostnames that match the panel, for example ns1.webji.services and ns2.webji.services. An empty answer or a single name means the domain is not delegated properly, and no record you add will go live.
Change name servers without taking the site down
The order matters more than the change itself. Build the new zone first, then move the delegation, so there is no window where the domain points at an empty zone.
- Create the domain as an addon or a zone at the new host and copy every record: A, CNAME, MX, TXT including SPF and verification strings, and any SRV records.
- Lower the TTL on the records you care about to 300 seconds a day before the move, so old answers expire quickly.
- Change the name server pair at the registrar to the new host's two hostnames.
- Wait. Most resolvers pick up the new delegation within a few hours, and the slow ones can take up to 48.
- Check with a public resolver:
dig @1.1.1.1 NS example.com +short.
Mail is the usual casualty. If the new zone has no MX record, mail bounces while the website still loads, and the failure looks like a mailbox problem rather than a DNS one.
Private name servers and subdomain delegation
A private name server is a branded hostname you delegate to, such as ns1.yourbrand.com, instead of the host's default pair. Resellers use them so clients see one brand, not two.
When that hostname sits inside the domain it serves, the parent zone needs a glue record: an A record in the parent that carries the name server's IP. Without glue, the resolver cannot find the server that holds the answer.
A subdomain can also have its own NS records, which hands that child zone to a different provider. A shop on shop.example.com can then run on another platform while the main site stays where it is.
What a name server is not
Three lookalikes cause most of the confusion in support tickets.
- Not SNI. Server Name Indication is the TLS field a browser sends so one IP can serve several certificates. It has nothing to do with DNS delegation.
- Not a server hostname. A value like srv12.webji.services identifies one machine and is used in FTP, SSH and mail settings.
- Not the registrar's brand. A domain bought at one company can point at another company's name servers, and often should.
If a page about name servers mentions certificates or file uploads, it has drifted into a different field. Delegation is only about which servers answer for the zone.
Where WebJi® fits in
Domains registered through domain registration point at two WebJi® name servers by default, and the panel prints the pair so it can be copied into another registrar if the site moves.
Hosting accounts on the same platform keep the website and the DNS in one panel, which removes the mismatch between a record you edited and a zone nobody is serving. If a domain still shows the old pair after a day, email support@webji.services with the domain and the dig output; the desk answers 24/7 in Hindi and English, with an average first reply under 60 minutes. The knowledgebase shows the delegation screen for each panel.
Frequently Asked Questions
What is a name server?
A name server is the DNS server that holds the records for one zone and answers queries about it. Your registrar lists two or more hostnames, such as ns1 and ns2, and those hostnames are the authoritative source for every record in the domain.
What is the difference between DNS and name servers?
DNS is the whole system, including resolvers, root servers and caches. A name server is one authoritative part of it: the server that holds your zone's records. Every domain needs at least one, and two is the practical minimum.
How do I find my name servers?
Run dig NS yourdomain.com +short, or nslookup -type=NS yourdomain.com on Windows. The registrar panel and a whois lookup show the same pair. If the command and the panel disagree, the delegation is still propagating.
How do I change name servers for my domain?
Copy every record to the new host first, including MX and TXT, lower the TTL, then replace the pair at the registrar with the new hostnames. Check from a public resolver such as 1.1.1.1 before you cancel the old account.
How long does a name server change take?
Usually a few hours, and up to 48 in the worst case, because registries and resolvers cache the old delegation for a fixed period. A lower TTL on the records shortens the second half of that wait, not the registry's own.
What happens if the name servers are wrong?
The domain stops resolving, or resolves to the wrong host. A typo in one hostname can leave the site up through the second server until it too fails. Mail bounces as soon as the zone stops answering, so check MX records first after a move.