What Is a Nameserver? A Simple Guide for Website Owners

Nameservers are servers running DNS server software that store and provide information about your domain. When someone types your domain into a browser, their computer asks a nameserver “where is this website?”, and the nameserver responds with the IP address of the server hosting your site.

Think of nameservers as the internet’s telephone directory. You look up a name and get back a number to dial. Without this translation service, you’d need to remember strings of numbers like 185.93.3.71 instead of typing simple domain names.

Nameservers hold various DNS records that direct different types of traffic to the right places. A records point to your web server, MX records route email to your mail server and other record types handle specific functions. Without correctly configured nameservers, your domain won’t connect to your website or email.

The DNS resolution journey happens in milliseconds every time someone visits a website. We’ll walk you through this process so you understand what happens behind the scenes when troubleshooting issues or making changes to your domain configuration.

First, you type a domain into your browser. Your computer then asks a recursive nameserver (usually your ISP’s or a public DNS like Google’s 8.8.8.8) to find the IP address. The recursive nameserver queries a root nameserver, one of 13 globally managed by ICANN. The root nameserver directs the query to the appropriate TLD (top-level domain) nameserver, such as the one handling .co.uk domains.

The TLD nameserver then points to the authoritative nameserver for your specific domain. This authoritative nameserver returns the IP address, and your browser connects to that IP to load the website. Results are cached to speed up future visits, which is why subsequent page loads often feel faster.

The authoritative nameservers are the ones you’ll actually manage or change as a website owner. They’re usually provided by your web host or domain registrar and contain the definitive information about where your website lives.

Several types of nameservers play different roles in the DNS system. Understanding which ones you control and which ones simply facilitate lookups clarifies what you’re actually managing when you work with your domain.

Authoritative nameservers are the definitive source of information for your domain. They hold the actual DNS records and provide final answers to queries. These are the nameservers you set at your domain registrar, typically addresses like ns1.yourhost.com and ns2.yourhost.com.

When you “change your nameservers”, you’re updating which authoritative nameservers control your domain’s DNS records. If your domain is registered with Namecheap but hosted with SiteGround, you’d point your domain to SiteGround’s authoritative nameservers. Most web hosting providers give you their nameserver addresses to use when you sign up.

Recursive nameservers (also called resolvers) are intermediaries that do the lookup work on behalf of your computer. Your ISP provides recursive nameservers by default, but you can use public alternatives like Google Public DNS (8.8.8.8) or Cloudflare (1.1.1.1).

You don’t manage these as a website owner. They’re used by visitors’ computers to find your site. Public DNS services can sometimes be faster or more reliable than ISP defaults, which is why some users switch to them for improved browsing performance.

Domains typically use at least two nameservers (primary and secondary, such as ns1.host.com and ns2.host.com) for redundancy. If the primary nameserver is unavailable, the secondary can still answer queries, preventing your website from becoming unreachable.

Both nameservers usually hold identical information and work together for reliability and load balancing. This redundancy is why you’ll always see multiple nameserver addresses when you check your domain settings.

The relationship between domain registration, nameservers and web hosting often confuses new website owners. We’ll explain how these three pieces connect to make managing your online presence much clearer.

You register your domain with a registrar (such as Namecheap, GoDaddy UK or 123-reg). You buy web hosting from a provider, which may or may not be the same company. To connect them, you point your domain to your host by changing the nameservers at your registrar to the ones provided by your hosting company.

The nameservers control where your domain’s DNS records are managed. Once you set them to your host’s nameservers, you manage DNS records (A, MX, CNAME and others) in your hosting control panel. If you use your registrar’s nameservers instead, you’d manage DNS records at the registrar and manually point A records to your hosting IP.

For most website owners, we recommend using the hosting provider’s nameservers because everything is managed in one place. You register example.co.uk at Namecheap, buy hosting from Krystal, then update Namecheap’s nameserver settings to ns1.krystal.uk and ns2.krystal.uk. When you switch web hosts, you’ll need to update your nameservers to the new host’s addresses.

Before making any changes to your domain configuration, you need to know which nameservers are currently controlling your DNS. We’ll show you several methods to check this information quickly.

The easiest way is to log in to your domain registrar’s control panel (where you bought the domain) and look for “Nameservers”, “DNS Settings” or “Domain Management”. You’ll see 2-4 nameserver addresses listed, such as ns1.example.com.

The exact location varies by registrar but is usually prominent in domain settings. Some registrars label this section “Name Servers” (two words) whilst others use “Nameservers” (one word), but they all refer to the same thing.

Free online tools like WHOIS Lookup, WhatsMyDNS.net or MXToolbox let you enter your domain and see which nameservers are currently authoritative. These tools query the global DNS system, so they show what’s actually live, which may differ from your registrar settings if changes are still propagating.

WHOIS lookups also show registrar information and domain expiry dates, making them useful for checking multiple aspects of your domain configuration at once. These tools are particularly helpful for verifying that nameserver changes have propagated globally.

If you’re comfortable with command-line tools, you can use nslookup (Windows) or dig (Mac/Linux) to query nameservers directly. A simple example command is `nslookup -type=NS example.co.uk`, which returns the nameserver records for that domain.

This method is optional and online tools are easier for most people. Command-line queries are useful for advanced troubleshooting or when you need to check DNS from a specific location.

Changing nameservers is one of the most common tasks involving DNS, typically performed when moving your website to a new hosting provider. We’ll guide you through the process with attention to timing and proper setup.

Sign up with your new web host and locate their nameserver addresses, usually in a welcome email or hosting control panel. You’ll typically receive two addresses like ns1.newhost.com and ns2.newhost.com. Write down or screenshot these addresses before proceeding.

Log in to your domain registrar (where you bought the domain) and find the nameserver or DNS management section. Some registrars require you to “unlock” the domain first, similar to the process needed for a full domain transfer, though changing nameservers doesn’t transfer ownership.

Replace the existing nameserver addresses with your new host’s nameservers and save the changes. Before making this change, screenshot or write down the old nameservers in case you need to revert. Once saved, the propagation process begins.

After changing nameservers, it takes time for the change to spread across the internet. This is called DNS propagation. Typical propagation time is up to 48 hours, though often faster, sometimes just a few hours.

During propagation, some visitors may see your old site and others the new one, depending on which nameservers their DNS resolver is using. We recommend that you set up your new hosting completely (upload files, configure email, test everything) before changing nameservers, so the new site is ready when propagation completes.

You can check propagation progress using tools like WhatsMyDNS.net, which shows which nameservers are being reported in different locations worldwide. Lowering TTL (Time To Live) values before making changes can speed up propagation, but this is advanced and not necessary for most users.

Website not loading after nameserver change is the most common problem. Check propagation status using online tools, wait longer (up to 48 hours) and verify nameservers saved correctly at your registrar. Clear your browser cache as it may be showing an old version.

Email stops working when MX records aren’t configured at the new host or mail client settings need updating. SSL certificate errors occur because the new host needs to issue a certificate, which can take a few minutes for Let’s Encrypt to activate.

If your old site still shows after 48 hours, check that nameservers actually changed at your registrar and that DNS records exist at the new host. Most issues resolve with patience during propagation, but incorrect nameserver addresses or missing DNS records at the new host are common culprits requiring immediate attention.

Custom (or private) nameservers let you use your own domain in nameserver addresses, such as ns1.example.co.uk instead of ns1.krystal.uk. This feature appeals to agencies, resellers and businesses wanting branded nameservers.

The benefits include professional branding for agencies offering hosting to clients, control over nameserver names if you switch underlying infrastructure and hiding which hosting provider you use. The setup process involves creating nameserver hostnames at your registrar, then assigning them IP addresses (glue records) pointing to your hosting provider’s actual nameservers.

This requires a VPS or dedicated server in most cases, or a reseller hosting plan that supports private nameservers. For most small business website owners, we find that using your host’s default nameservers is perfectly fine and simpler. Custom nameservers are mainly for those managing multiple client sites or wanting a white-label setup.

“Nameserver” and “DNS server” are often used interchangeably and refer to the same thing: a server that handles DNS queries. The subtle distinction, if any, is that “DNS server” is the broader term (any server running DNS software), whilst “nameserver” often specifically refers to authoritative nameservers that hold your domain’s records.

Nameservers are distinct from web servers. Nameservers tell browsers where to find your web server; the web server actually hosts your website files. Think of the nameserver as the address book and the web server as the actual house at that address.

Nameservers differ from domain registrars. The registrar is where you buy the domain; nameservers are what you configure to point the domain to hosting. Nameservers also differ from DNS records: nameservers are the servers themselves; DNS records are the data stored on those servers.

Public DNS services (Cloudflare 1.1.1.1, Google 8.8.8.8, Quad9 9.9.9.9) are free recursive nameservers anyone can use instead of their ISP’s defaults. These services offer several advantages over standard ISP DNS.

Benefits include often faster DNS resolution (quicker website loading), better reliability (less downtime), enhanced privacy (some don’t log queries) and security features (blocking malicious sites). These are configured on your computer or router, not at your domain registrar. They affect how you look up other websites, not how others find your website.

Some users switch to public DNS for speed or privacy, but for most people the ISP’s DNS works fine. As a website owner, you don’t control which DNS resolvers your visitors use. You only control your domain’s authoritative nameservers.

Nameserver security directly affects your website’s availability and integrity. We’ll cover several security aspects that deserve your attention when managing your domain’s DNS configuration.

If someone gains access to your domain registrar account, they can change your nameservers and redirect your website and email to servers they control. This form of domain hijacking gives attackers complete control over your online presence.

Protective measures include using strong, unique passwords for your registrar account, enabling two-factor authentication (2FA), locking your domain to prevent unauthorised transfers and using registrar security features like “domain lock” or “nameserver lock”. We strongly recommend securing your registrar account because nameserver control means control over your entire online presence.

DNSSEC (Domain Name System Security Extensions) adds cryptographic signatures to DNS records, preventing attackers from spoofing or tampering with DNS responses. DNSSEC ensures visitors reach your real website, not a fake one.

Enabling DNSSEC requires support from both your registrar and hosting provider and involves some technical setup (generating keys, adding DS records). Whilst DNSSEC is good security practice, it’s not yet universally adopted and most small business sites operate without it. For readers interested in maximum security (such as e-commerce or financial services), it’s worth investigating.

Nameservers can be targeted by DDoS (Distributed Denial of Service) attacks, overwhelming them with traffic and making your website unreachable even if your web server is fine. Using nameservers from reputable hosting providers or DNS services with DDoS protection (like Cloudflare) reduces this risk.

Having multiple nameservers (primary and secondary) on different networks improves resilience. For most small sites, this is handled by your hosting provider, but we recommend checking that your host has DDoS mitigation in place. You can typically find this information in their security documentation or by asking their support team directly.

Two main options exist for managing your domain’s DNS. Using your hosting provider’s nameservers is most common: DNS records are managed in your hosting control panel, simpler for most users, everything in one place and automatically configured for your hosting.

Using your registrar’s nameservers means DNS records are managed at your registrar. This is useful if you want to keep DNS separate from hosting, such as if you frequently switch hosts or use multiple services. It requires manually creating A records, MX records and other records pointing to your hosting IPs.

Typical scenarios: if you have one website on one host, use the host’s nameservers for simplicity. If you’re an agency managing multiple client sites or need advanced DNS features, you might prefer managing DNS at the registrar or using a dedicated DNS service like Cloudflare.

Some advanced users use third-party DNS services (Cloudflare, Route 53) for better performance, DDoS protection or advanced features, whilst keeping hosting separate. For most small business owners, we recommend using your hosting provider’s nameservers unless you have a specific reason not to.

Nameservers are the essential link between your domain name and your web hosting, translating the address people type into the IP where your website actually lives. For most website owners, nameservers become relevant when setting up a new site or switching hosting providers.

You’ll need to update your domain registrar’s nameserver settings to point to your new host’s nameservers, then wait up to 48 hours for DNS propagation. Whilst the technical details can seem complex, the practical steps are straightforward: find your host’s nameserver addresses, log in to your registrar, update the settings and wait for propagation.

We recommend using your hosting provider’s nameservers for most situations, keeping DNS management in one place. For those needing more control, custom nameservers or third-party DNS services are options, but not necessary for typical small business websites. Make sure you secure your domain registrar account with strong passwords and two-factor authentication, since nameserver control means control over your entire online presence.