How do I find my domain's nameservers?

Use the command 'dig NS yourdomain.com' or 'nslookup -type=NS yourdomain.com' in a terminal. You can also run 'whois yourdomain.com' and look for the Name Server entries. Online, enter your domain in any DNS lookup tool and query for NS records. Your registrar's dashboard also lists the current nameservers under DNS Settings or Nameservers.

What do nameservers look like?

Nameservers are hostnames, not IP addresses. They follow a pattern like ns1.provider.com and ns2.provider.com. Examples: Cloudflare nameservers look like 'alma.ns.cloudflare.com'; AWS Route 53 nameservers look like 'ns-123.awsdns-45.com'; registrar default nameservers often look like 'ns1.registrar.com'. Most providers assign two to four nameservers for redundancy.

Where do I update my nameservers?

Nameservers are always updated at your domain registrar — the company where you purchased the domain. Log in to your registrar, find the domain in your account, and look for a section called DNS, Nameservers, or DNS Settings. Do not confuse this with the DNS management dashboard at your DNS hosting provider, which is where you manage individual DNS records.

Why do I have multiple nameservers?

Multiple nameservers provide redundancy. If one nameserver is unreachable due to a network issue, hardware failure, or maintenance, resolvers automatically try the others. The DNS specification requires at least two nameservers for every zone. Most providers assign two to four nameservers spread across different networks and geographic locations to maximise availability.

How To Find Your Nameservers

Get a detailed answer to how to find your nameservers along with step-by-step troubleshooting instructions and related DNS resources.

ReviewMyDNS is a free DNS propagation checker that queries 50+ global DNS servers to verify your DNS records. Check A, AAAA, MX, CNAME, TXT, NS, and SOA records instantly.

How to Find Your Domain's Nameservers

Your domain's nameservers are the authoritative DNS servers that answer queries for your domain worldwide. Knowing your current nameservers is essential when troubleshooting DNS issues, switching DNS providers, or verifying that a nameserver change has propagated correctly.

Method 1: Using dig (macOS, Linux, Windows with WSL)

The dig command is the most reliable way to look up nameservers. Open a terminal and run:

dig NS yourdomain.com

The output shows the NS records in the ANSWER section. Each NS record lists one nameserver hostname. If you want to see the glue records (the IP addresses of the nameservers as published by the TLD), add the +additional flag:

dig NS yourdomain.com +additional

To trace the full delegation path from the root zone down to your authoritative nameservers — useful for diagnosing delegation problems — use:

dig NS yourdomain.com +trace

Method 2: Using nslookup (Windows, macOS, Linux)

On Windows, macOS, and Linux, nslookup is available by default. Run:

nslookup -type=NS yourdomain.com

The output lists the domain's authoritative nameservers. You can specify a particular resolver to query (useful for comparing results from different DNS servers):

nslookup -type=NS yourdomain.com 8.8.8.8

Testing against multiple resolvers — 8.8.8.8 (Google), 1.1.1.1 (Cloudflare), and your ISP default — shows whether nameserver propagation has completed globally or is still in progress.

Method 3: Using whois

The WHOIS protocol returns domain registration data including nameservers. Run whois yourdomain.com in a terminal, or use any online WHOIS tool. Look for the "Name Server" fields in the output. WHOIS data comes from the registrar, so it shows nameservers as your registrar has them recorded — useful for spotting discrepancies between what the registrar has on file and what the TLD zone is actually serving. During nameserver propagation, WHOIS and DNS queries may temporarily show different values.

Method 4: Using an Online DNS Lookup Tool

Enter your domain in the ReviewMyDNS lookup tool, select NS as the record type, and run the query. The tool simultaneously checks nameserver records from 50+ global DNS servers and shows whether all servers are returning consistent NS records — helpful when verifying that a nameserver change has fully propagated.

Understanding What You Find

Nameservers are always hostnames, not IP addresses. Most domains have two to four nameservers for redundancy. Common nameserver patterns by provider:

Cloudflare: Two account-unique hostnames, e.g. alice.ns.cloudflare.com and bob.ns.cloudflare.com — these names vary per account
AWS Route 53: Four nameservers across different TLDs, e.g. ns-123.awsdns-45.com, ns-678.awsdns-90.net, ns-111.awsdns-22.org, ns-999.awsdns-33.co.uk
GoDaddy: Typically ns1.domaincontrol.com and ns2.domaincontrol.com
Namecheap: Typically dns1.registrar-servers.com and dns2.registrar-servers.com
Google Domains / Squarespace: Typically ns-cloud-X1.googledomains.com through ns-cloud-X4.googledomains.com

Where to Update Nameservers at Your Registrar

Nameservers are always changed at your domain registrar — the company where you originally purchased the domain. Do not confuse this with the DNS management dashboard at your current DNS provider, which is where you manage individual DNS records. Registrar-specific navigation paths:

GoDaddy: Domain Settings → Manage DNS → Nameservers → Change. See the GoDaddy DNS guide.
Namecheap: Domain List → Manage → Nameservers → Custom DNS. See the Namecheap DNS guide.
Google Domains: DNS → Nameservers → Use custom name servers.

After changing nameservers, verify global propagation by querying NS records across multiple resolvers or using the propagation checker with NS record type selected. Full nameserver propagation takes 24-48 hours. During this period, use Nameservers vs DNS Records as a reference for understanding which system to make changes in. See the Cloudflare DNS Setup Guide for the complete activation workflow after switching to Cloudflare nameservers.

Troubleshooting Inconsistent Nameserver Results

If different DNS servers return different NS records for your domain, nameserver propagation is still in progress — this is normal within 24-48 hours of a change. If inconsistency persists beyond 48 hours, check your registrar to confirm the nameservers are saved correctly and that your domain is not on a registrar lock or hold status. Some registrar locks prevent nameserver changes from taking effect. Also verify there are no typos in the nameserver hostnames — a single character error in a nameserver hostname causes resolution failures for all DNS records under that domain.