Network & DevOps ToolkitNS Record Lookup
Who answers for this domain — the first question in every DNS mystery.
Enter a domain — the NS record type is pre-selected.
Loading…
Why NS is the first thing to check
Every DNS debugging session should start here, because records you edit only matter if you edited them at the authoritative provider:
- "I changed the record but nothing happened" — check whose nameservers are live. If NS says Cloudflare and you edited GoDaddy's zone, your change is invisible.
- Migrations: after changing nameservers at the registrar, the switch can take up to 48h (registry TTLs). Both old and new sets may answer during the window — keep zones identical on both.
- Fingerprints:
*.ns.cloudflare.com= Cloudflare,awsdns-*= Route 53,*.registrar-servers.com= Namecheap,ns*.domaincontrol.com= GoDaddy. - Healthy domains have 2+ NS records on separate infrastructure — a single nameserver is a single point of failure.
What's the difference between registrar and DNS host?
The registrar sells the name and records WHERE the DNS lives (the NS records); the DNS host serves the actual zone. They're often different companies — which is exactly why edits go missing.
How long does a nameserver change take?
The TLD registry publishes the new NS quickly, but resolvers cache the old set for up to the registry TTL — commonly 24–48 hours. Lower your record TTLs before a migration, not after.
Why do I see different answers than a friend does?
Resolver caches. Each ISP's resolver expires records on its own schedule during propagation. Authoritative truth is what the NS-listed servers return.
Related tools
- DNS Lookup — query the records those nameservers serve.
- MX Record Lookup — mail-specific delegation checks.
- Subnet Calculator — the IP side of your infrastructure.
🔐 DNS queries are answered server-side by this site's own resolver API and are not logged. Every other tool on this site runs entirely in your browser.