You buy a domain in one place, build your website in another, and somehow they connect — but the piece that makes that happen often goes unexplained. That piece is nameservers. They are the behind-the-scenes signposts that tell the internet where your domain’s settings live and where its traffic should go. Understand nameservers, and one of the most confusing parts of owning a domain suddenly makes sense.
This guide explains what nameservers are in plain language, how they work, the crucial difference between nameservers and DNS records, why they usually come in pairs, how to find and change yours, and when you would need to. Whether you are connecting a domain to hosting for the first time or just curious about the machinery behind your website, this will give you a clear, confident grasp.
Did you know?
Nameservers are often called the phone book of the internet: humans remember names like example.com, but computers need numbers like 192.0.2.1, and nameservers are what hold the directory that connects the two for your domain.
What a nameserver is
A nameserver is a specialised server that translates human-readable domain names into the numeric IP addresses computers use to connect. When someone tries to reach your website, a nameserver is consulted to find out where your domain actually lives, then directs the request to the correct hosting server.
The phone book analogy captures it well. You know a business’s name but need its number to call; the phone book connects the two. Nameservers do the same for websites — you know the domain, and the nameserver provides the address, guiding your browser to the right place.
Crucially, nameservers are also where your domain’s DNS records are stored. They hold the A, CNAME, MX, and other records that point your domain to your website, your email, and your subdomains. So a nameserver is both a signpost and a filing cabinet for your domain’s settings.
How nameservers work
When you type a web address, your device asks the domain’s nameservers for the correct coordinates. The nameserver looks up the relevant DNS record — for example, the A record that maps your domain to a server’s IP address — and returns that information, so your browser can connect to the right hosting server and load the site.
This lookup is part of the wider DNS resolution process, but the nameserver is the authoritative source for your specific domain. It is the server that actually holds and serves the answers about where your domain points, which is why it is called the domain’s authoritative nameserver.
Because nameservers store and serve your records, whichever nameservers your domain uses is where your DNS is genuinely controlled. Change the records on those nameservers, and you change how your domain behaves; that is the practical power nameservers hold.
Nameservers store your DNS records
A key point that clears up much confusion: nameservers are the containers that hold your DNS records. The records themselves — A for your website, MX for email, CNAME for aliases, TXT for verification — all live on the nameservers your domain is set to use.
This means the nameservers determine where your DNS is managed. If your domain points to your registrar’s nameservers, your records live and are edited there; if it points to your host’s nameservers, they live and are edited in the host’s panel. The active nameservers are the single source of truth.
Understanding this saves a classic mistake: editing DNS records in a place that is not your active nameserver, and wondering why nothing changes. Records only take effect on the nameservers your domain actually uses, so knowing which those are is essential.
The registrar and host relationship
Nameservers are what connect your domain (bought at a registrar) to your website (built at a host). By default, a newly registered domain uses the registrar’s nameservers. To connect it to a separate hosting company, you typically update the domain’s nameservers to point at the host’s nameservers instead.
Once you do that, your host’s nameservers become authoritative for your domain, and you manage your DNS records there. This is the standard way to link a domain and hosting that live at different companies — you are essentially telling the internet, “for this domain, ask my host’s servers for directions.”
Alternatively, you can keep your registrar’s nameservers and just point your records (like the A record) at your host’s IP. Both approaches work; the nameserver-based method hands full DNS control to your host, which many people find simpler when everything is in one place.
Why nameservers come in pairs
You will almost always see nameservers listed as at least two — commonly ns1.host.com and ns2.host.com. This is deliberate: having multiple nameservers provides redundancy, so if one is unavailable, the other can still answer requests and keep your domain reachable.
Relying on a single nameserver would be risky; if it went down, your domain would become unresolvable and your site and email could go dark. By spreading the responsibility across two or more nameservers, providers ensure your domain stays reliably accessible even if one server has a problem.
So when a host or registrar gives you a set of nameservers to enter, enter all of them. The pair (or more) is a resilience feature, not a formality, and using the complete set is what keeps your domain dependable.
How to find and change your nameservers
Your current nameservers are visible in your domain’s settings at your registrar, and can also be seen via a public WHOIS or nameserver lookup. Checking them tells you exactly where your DNS is managed — the essential first step before making any DNS or hosting change.
To change them, you log in to your registrar (where the domain is managed), find the nameserver or DNS settings, choose custom nameservers, and enter the new ones your host or DNS provider gives you. Saving the change repoints your domain to the new nameservers, transferring DNS control to them.
This is exactly what you do when connecting a domain to a new host that manages DNS: replace the existing nameservers with the host’s. After the change, allow time for propagation, and remember to set up your DNS records at the new nameservers so nothing breaks in the transition.
Pro Tip
Before switching nameservers to a new host, make sure your website and email records are ready at the new provider. Changing nameservers hands over DNS control entirely, so having the records in place first prevents any gap in your site or email.
When you would change nameservers
The most common reason to change nameservers is moving your domain’s DNS management to a new host — for instance, when you register a domain at one company and want a different company to host your site and control your DNS. Repointing the nameservers to the host is the clean way to do this.
You might also change nameservers to use a service like a content delivery network or a specialised DNS provider that manages your records and adds performance or security features. In that case, you point your nameservers at that service, which then becomes authoritative for your domain.
If everything is already with one provider — domain and hosting in the same place — you usually never need to touch nameservers at all, since the defaults already point correctly. So nameserver changes are mainly for connecting separate services, and once set, they rarely need revisiting.
Nameservers vs DNS records
It is worth being clear on the distinction, because the two are easy to confuse. Nameservers are the servers that hold your domain’s settings and decide where DNS is managed; DNS records are the individual entries inside those nameservers that direct specific traffic, like your website or email.
Put simply, you change nameservers to decide who controls your DNS, and you edit DNS records to change what specific things point to. Moving to a new host that manages DNS is a nameserver change; adding email or verifying a service is a record edit at whatever nameservers you currently use.
Keeping this straight resolves most beginner confusion. Nameservers are the big-picture control (where your DNS lives), and records are the fine-grained settings (what points where) that live within it.
Connecting a domain to your hosting?
Hostinger provides clear nameservers and an easy DNS panel, so pointing your domain and managing your records is simple whether your domain is with Hostinger or elsewhere — with a free domain included on its hosting plans.
FAQs
What are nameservers in simple terms?
Nameservers are specialised servers that act as the phone book for your domain: they translate your domain name into the IP address computers use and hold your DNS records that point your domain to your website, email, and subdomains. Whichever nameservers your domain uses is where its DNS is actually controlled.
What do nameservers do?
They store your domain’s DNS records and answer lookups about where your domain points. When someone visits your site, the nameservers are consulted to find the right server address and direct the request there. They are the authoritative source for your domain’s settings, so they determine where your DNS is managed and edited.
What is the difference between nameservers and DNS?
Nameservers are the servers that hold your domain’s settings and decide where DNS is managed; DNS records are the individual entries inside them that route specific traffic like your website or email. You change nameservers to choose who controls your DNS, and you edit records to change what points where.
Why do nameservers come in pairs?
For redundancy. Having at least two nameservers (like ns1 and ns2) means that if one is unavailable, the other can still answer requests and keep your domain reachable. Relying on a single nameserver would risk your site and email going dark if it failed, so providers always supply a set — enter all of them.
How do I find my nameservers?
Check your domain’s settings at your registrar, where the current nameservers are listed, or use a public WHOIS or nameserver lookup. This tells you exactly where your DNS is managed — the essential first step before changing DNS or connecting hosting, since records only take effect on the nameservers your domain actually uses.
When should I change my nameservers?
Mainly when moving your domain’s DNS management to a new host, or to a service like a CDN or specialised DNS provider. You change them at your registrar by entering the new provider’s nameservers. If your domain and hosting are already with one provider, you usually never need to change nameservers at all.
The bottom line
Nameservers are the phone book of the internet for your domain: specialised servers that translate your domain name into the IP address computers use, and that hold the DNS records pointing your domain to your website, email, and subdomains. Because they store and serve those records, the nameservers your domain uses are where your DNS is genuinely controlled — which is why editing records anywhere else has no effect. They usually come in pairs for redundancy, keeping your domain reachable even if one server fails.
In practice, nameservers are what connect a domain bought at a registrar to a website built at a host: you point the domain’s nameservers at the host to hand it DNS control, or keep the registrar’s and point individual records instead. You find your nameservers in your registrar’s settings, change them there when moving DNS management to a new host or service, and otherwise rarely touch them. Keep the big distinction clear — nameservers decide where your DNS lives, while DNS records decide what points where — and the machinery behind your domain becomes easy to reason about.
When you are ready, you can start with Hostinger and use code PROTIPS for the reader discount. Nameservers are the internet’s phone book for your domain — they hold your DNS records and decide where your DNS is controlled. They come in pairs for redundancy; change them at your registrar to point a domain to a new host.