NS Lookup - Nameserver Lookup
Find the authoritative nameservers for any domain. Verify DNS is delegated to the right provider, debug propagation issues, and confirm nameserver changes went through.
What is an NS lookup?
An NS lookup queries the DNS system for the nameserver (NS) records of a domain. Nameservers are the authoritative DNS servers that hold all the DNS records for your domain - including your MX, SPF, DKIM, DMARC, A, CNAME records, and more.
When you change your DNS provider or move a domain to a new registrar, NS records are the first thing that needs to update. If your NS records still point to the old provider, none of your other DNS changes will take effect.
When to use an NS lookup
-
After changing DNS providers
Verify that your domain is now pointing to the new nameservers (e.g., Cloudflare, Route 53, or Namecheap FreeDNS). -
When DNS changes are not taking effect
If you updated an MX or SPF record but the change is not showing up, checking NS records confirms whether the right DNS provider is being queried. -
When taking over a domain
Confirm which DNS provider currently manages the domain and whether it needs to be migrated. -
For email deliverability debugging
If you added SPF or DMARC records but they are not being found, a wrong NS delegation is often the cause.
Common NS records by DNS provider
| Provider | Nameservers (examples) |
|---|---|
| Cloudflare | xxx.ns.cloudflare.com |
| Google Cloud DNS | ns-cloud-X.googledomains.com |
| AWS Route 53 | ns-XXX.awsdns-XX.com |
| Namecheap | dns1.registrar-servers.com |
| GoDaddy | ns37.domaincontrol.com |
| Squarespace | ns1.squarespace.com |
How long does nameserver propagation take?
NS record changes (domain delegation) typically propagate in 1-24 hours, though most registrars complete the change within 2-4 hours. During propagation, different DNS resolvers around the world may return different nameservers - this is normal and temporary.
Changes to other DNS records (SPF, DMARC, MX) after NS propagation typically take just a few minutes to an hour, depending on TTL.
FAQ
Why is my NS lookup showing two different sets of nameservers?
This can happen during propagation after a nameserver change, or if your domain registrar and DNS provider are different services with their own NS records. Check both your registrar's control panel (where NS records are delegated) and your DNS provider (where records are hosted).
How many nameservers should a domain have?
Most domains have 2-4 nameservers for redundancy. Having at least two nameservers is required by ICANN for domain registration. More is fine and increases resilience.
My SPF and DMARC records are not showing up - what to check first?
Check your nameservers first. If the NS records point to the wrong provider, none of your DNS records will be found. Then check the actual DNS records at the correct provider. Use the TXT Lookup to see all TXT records and the InboxGreen checker for a full SPF/DKIM/DMARC scan.
Can I have different nameservers for different subdomains?
Yes, this is possible using NS delegation at a subdomain level. For example, mail.yourdomain.com can be delegated to a different DNS provider than the root domain.
This is common for large organizations but unusual for small business setups.
Related tools: