NS Record Lookup

NS records name the servers that hold a domain's DNS zone. Look up any domain's NS records across 21 global servers to confirm the authoritative nameservers and check that a nameserver change has propagated.

Global DNS Propagation

New York, USA Google	---
Chicago, USA Gcore	---
Los Angeles, USA Cloudflare	---
Toronto, Canada CIRA	---
Mexico City, MX OpenDNS	---
London, UK Quad9	---
Frankfurt, Germany DNS.Watch	---
Paris, France FDN	---
Amsterdam, NL OpenNIC	---
Moscow, Russia Yandex	---
Singapore Singtel	---
Tokyo, Japan IIJ	---
Mumbai, India Google India	---
Seoul, Korea KT	---
Dubai, UAE Etisalat	---
Sydney, Australia Telstra	---
Auckland, NZ Cloudflare	---
São Paulo, Brazil NIC.br	---
Buenos Aires, AR Telecom Arg	---
Johannesburg, ZA ISPA	---
Cairo, Egypt Telecom Egypt	---

DNS Map

0 0

What an NS record does

An NS (Name Server) record lists the authoritative nameservers for a domain. These are the servers that answer for the zone and hold every other record. When a resolver needs a domain's records, it is directed to the nameservers named in the domain's NS records.

NS records exist in two places: at the registry for the parent zone (the delegation) and inside the zone itself. Both should agree. For the full background, read what is an NS record and DNS vs nameservers.

How to read the results

Each row shows one of the 21 global servers and the nameserver hostnames it returned, for example ns1.example-dns.com. Most domains list two to four nameservers. Every server should return the same set once propagation is complete.

If some regions still show your old nameservers after a switch, propagation is in progress. Nameserver changes are handled at the registry and can take longer than ordinary record edits, since the parent zone's TTL controls how long the old delegation is cached.

Common NS record values

Nameservers usually belong to your DNS provider or registrar. Cloudflare assigns a pair like kate.ns.cloudflare.com and rob.ns.cloudflare.com. Other providers use patterns such as ns-123.awsdns-45.com or dns1.registrar.com.

The names should match exactly what you set at the registrar. A domain listing nameservers from a provider you no longer use is a sign the delegation was never updated, which means your record edits at the new provider have no effect.

Troubleshooting NS records

If DNS changes are not taking effect anywhere, the NS records are the first thing to check. Confirm the nameservers listed here are the ones you edit records at. If they point elsewhere, update the delegation at your registrar and wait for it to propagate. See how to change nameservers.

If different regions return different nameservers, you are mid-migration and both sets are still cached. Keep the old zone answering with correct records until every server shows only the new nameservers, so no visitor hits a dead delegation during the cutover.