What Is a Nameserver?
A nameserver is a specialized server that stores and answers requests about a domain's DNS records, telling the internet where to find a website, email, and other services for that domain. When you register a domain, you point it at nameservers, and those nameservers hold the authoritative records, such as which IP address the site lives at. Nameservers are the directory system that translates human-friendly domain names into the technical addresses computers use.
- Also called
- DNS server / authoritative name server
- Typical format
- ns1.example.com, ns2.example.com
- Minimum recommended
- At least two for redundancy
- Standard
- Domain Name System (IETF RFC 1034/1035)
What is a nameserver? #
A nameserver is a computer on the internet whose job is to answer questions about a domain's DNS records. Think of the Domain Name System as the internet's phone book, and nameservers as the specific directories that hold the entries for particular domains. When someone types your domain into a browser, their device eventually asks your domain's authoritative nameservers, which respond with the records that say where your website, email, and other services actually live. Every registered domain must point to at least one nameserver, and in practice you use two or more for reliability. Nameservers are typically written like ns1.yourhost.com and ns2.yourhost.com. Understanding them matters because they are the control point for your domain, whoever manages your nameservers controls where your traffic and email go. For the bigger picture of how domain lookups work, see /wiki/what-is-dns, and for how we manage domains, DNS, and email together, see /services/domains-dns-email.
How do nameservers fit into DNS? #
The Domain Name System is a hierarchy, and nameservers are the machines that make it work at each level. At the top sit root nameservers, which know where to find the servers for each top-level domain like .com or .org. Those TLD nameservers know which authoritative nameservers hold the records for a specific domain. Your domain's authoritative nameservers, usually run by your host or DNS provider, hold the actual records: the A record for your website's IP address, the MX records for email, and so on. When a visitor's device resolves your domain, it walks down this chain, root, then TLD, then your authoritative nameservers, caching answers along the way to speed up future lookups. This delegation is why changing your nameservers effectively hands over control of all your DNS records at once. The individual record types are covered on /wiki/what-is-an-a-record, /wiki/what-is-an-mx-record, and /wiki/what-is-a-cname-record.
What is the difference between nameservers and DNS records? #
This trips up many business owners. Nameservers are the servers that store your records; DNS records are the individual entries those servers hold. Pointing your domain to a set of nameservers decides which provider is authoritative for your domain, in other words, which system holds your records. Once your domain uses a given provider's nameservers, you edit individual records, the A record, CNAME, MX, TXT, and others, within that provider's control panel. So there are two levels of control: at the registrar you set the nameservers, and at whichever provider those nameservers belong to you manage the actual records. Changing nameservers moves all your records to a new provider at once, while editing a record changes just one setting. Confusing the two is a common cause of downtime, someone updates records at the old provider while the domain points to a new one. We keep this straight for clients through /services/domains-dns-email, and you can inspect a domain's records with /tools/schema-validator and related diagnostics.
Why do you need at least two nameservers? #
Redundancy is the reason. If your domain relied on a single nameserver and that machine went offline, nobody could resolve your domain, meaning your website and email would effectively vanish even though the servers hosting them were fine. To prevent this single point of failure, best practice, and most registrars' requirements, is to list at least two nameservers, ideally in different locations or networks. If one is unreachable, resolvers automatically try the other, keeping your domain resolvable. This is why you always see pairs like ns1 and ns2, and larger providers use four or more spread across the globe. Reliable nameservers are foundational to uptime, if resolution fails, no amount of fast hosting helps, because visitors never reach your server, see /wiki/what-is-website-uptime. When we manage a client's domain, we ensure redundant, well-distributed nameservers and monitor resolution, and /tools/website-down-checker helps confirm a domain is reachable from multiple locations.
What happens when you change nameservers? #
Changing nameservers is one of the most consequential DNS actions you can take, because it moves authority for your entire domain to a new provider. When you update the nameservers at your registrar, you are telling the internet to start asking a different set of servers for all your records. The change does not take effect instantly, resolvers around the world cache the old information, so it can take anywhere from minutes to 48 hours for everyone to see the new nameservers, a period known as propagation, see /wiki/what-is-dns-propagation. Critically, the new nameservers must already contain correct copies of all your records before you switch, or your website, email, and other services can break during the transition. This is a common source of accidental downtime. We plan nameserver changes carefully, replicating every record on the new provider first, then switching, and monitoring until propagation completes. Our /services/website-migrations team handles exactly this during host changes.
Registrar nameservers vs host nameservers vs third-party DNS #
You have choices about whose nameservers manage your domain, and they are not the same thing as your domain registrar or your web host. Many businesses simply use their web host's nameservers, so DNS is managed in the same place as hosting, convenient but tied to that host. Others keep DNS at their registrar, managing records where they bought the domain. A third option is a dedicated DNS provider or a CDN like Cloudflare, which offers faster resolution, security features, and advanced controls independent of your host. Each approach is valid; the right one depends on your needs for speed, security, and flexibility. The key is knowing which system is authoritative so you edit records in the right place. We often recommend separating DNS from hosting so a host change does not disrupt email or other services, and we manage the whole arrangement through /services/domains-dns-email, keeping registrar, DNS, and hosting coordinated.
How do nameservers affect email and other services? #
Nameservers control far more than your website, they hold the records that route your email, verify your domain, and connect assorted services. Your MX records, which direct incoming email to the right mail servers, live on your nameservers, so a botched nameserver change can silently break email even while your website works, see /wiki/what-is-an-mx-record. TXT records used for email authentication like SPF, DKIM, and DMARC also live there, and losing them can send your outgoing mail to spam, see /wiki/what-is-a-txt-record. Subdomains, verification records for tools like Google and Microsoft, and CNAME entries pointing at third-party services all depend on the same nameservers. This is why nameserver management deserves care, one change touches everything tied to your domain. We coordinate website, email, and service records so nothing is lost during changes, and you can check whether email is likely to deliver with /tools/email-deliverability-checker.
How do you check or update your nameservers? #
You view and change nameservers at your domain registrar, the company where you registered the domain, in the domain's DNS or nameserver settings. There you will see the current nameserver hostnames, typically two or more, and an option to replace them. Before changing anything, confirm that the destination provider already holds correct copies of all your records, otherwise services will break during propagation. To check what nameservers a domain currently uses, you can run a WHOIS lookup or a DNS query tool, which reveals the authoritative nameservers and helps diagnose problems. If your site or email is misbehaving after a change, comparing the live nameservers against what you intended is an early troubleshooting step. Because a mistake here can take a business offline, we handle nameserver checks and changes for clients as part of /services/domains-dns-email and during any host move via /services/website-migrations, always verifying records first and monitoring propagation afterward.
Common nameserver mistakes to avoid #
Several avoidable errors cause outages. The most common is switching nameservers before copying records to the new provider, which instantly breaks anything not yet replicated. Another is editing records at the old provider after the domain already points elsewhere, so changes appear to do nothing because that provider is no longer authoritative. Removing or forgetting email and authentication records during a move is a frequent culprit behind vanished mail and spam-filtered outgoing messages. Using only one nameserver removes redundancy and risks total resolution failure if it goes down. Finally, ignoring propagation and expecting instant results leads to panic when changes seem not to work, when in reality caches simply need time to expire, see /wiki/what-is-dns-propagation. The safeguard for all of these is careful planning: replicate every record first, keep at least two nameservers, verify the authoritative provider, and allow for propagation. We build this discipline into every domain and migration project through /services/domains-dns-email.
FAQ
What is the difference between a nameserver and DNS?
DNS is the whole system that translates domain names into IP addresses. A nameserver is a specific server within that system that stores and answers requests for a domain's records. In short, DNS is the directory system; nameservers are the machines that hold and serve the actual entries for your domain.
How many nameservers do I need?
At least two. Using two or more nameservers provides redundancy, so if one is unreachable, another can still resolve your domain and keep your website and email available. Most registrars require a minimum of two, and larger providers use four or more spread across different networks and locations.
What happens when I change my nameservers?
Changing nameservers moves authority for your entire domain to a new provider. The change takes minutes to 48 hours to propagate worldwide. Critically, the new nameservers must already hold correct copies of all your records first, or your site and email can break during the switch, see /wiki/what-is-dns-propagation.
Where do I change my nameservers?
You change nameservers at your domain registrar, the company where you registered the domain, in its DNS or nameserver settings. This is separate from your web host. Before changing, make sure the new provider already has your records set up. We manage this for clients through /services/domains-dns-email.
Can changing nameservers break my email?
Yes. Your MX records and email authentication records (SPF, DKIM, DMARC) live on your nameservers. If you switch nameservers without recreating those records on the new provider, incoming or outgoing email can break. We coordinate all records during changes and check delivery with /tools/email-deliverability-checker.
Should I use my host's nameservers or a separate DNS provider?
Both work. Using your host's nameservers keeps everything in one place, while a separate DNS provider or CDN can offer faster resolution and security features independent of your host. Separating DNS from hosting means a host change does not disrupt email. We advise on the best setup per business.
Was this helpful?