NS Record Look Up
Related tools
What this is
NS records name the authoritative nameservers for a domain — the servers that actually hold and answer for its DNS zone. The registrar tells the parent zone which nameservers to delegate to; everything else in DNS depends on this being right.
How to read your result
Expect 2 or more nameservers, all belonging to the same DNS provider (the one whose control panel you actually edit records in). If these names surprise you, that explains why your DNS changes "don't work".
Common problems and how to fix them
NS points at one provider, but you edit records at another
How it shows up: Changes you make in a DNS control panel never take effect, no matter how long you wait.
How to fix it: Check the NS records to see who is really authoritative, then either edit records there, or update the nameservers at your registrar to the provider you want to use (which replaces the entire zone — recreate all records there first).
Registrar-level and zone-level NS records disagree
How it shows up: Intermittent, resolver-dependent behavior: some users see one set of records, others see another.
How to fix it: Make the NS set inside the zone identical to the delegation set at the registrar. After migrating DNS providers, update both places.
All nameservers in a single point of failure
How it shows up: When the DNS provider has an outage, the entire domain (web, mail, everything) goes down with it.
How to fix it: Use a provider with anycast nameservers on diverse networks (all major ones do this), or configure a secondary DNS provider for critical domains.
Related reading
- DNS Record Types, ExplainedA practical tour of every DNS record you will actually touch — A, AAAA, CNAME, MX, TXT, SRV, CAA, the DNSSEC set and the modern HTTPS record — with syntax, gotchas and when to reach for each.
- Reading a Domain's Registration Record: A Practical Guide to WHOIS and RDAPWhat a WHOIS/RDAP lookup actually tells you: registrar, lifecycle dates, nameservers, and EPP status codes — plus why modern records omit the owner's contact details.
- Reading a Domain in One Pass: A Guide to Full DNS Record LookupsSee every DNS record for a domain at once - A, MX, TXT, SPF, DMARC, CNAME, NS, SOA, CAA, SRV and WHOIS - and learn what each one actually does.
Frequently asked questions
- What is an NS record?
- An NS (Name Server) record lists the authoritative name servers responsible for a domain's DNS zone. These servers hold the real answers for the domain's other records, such as A, MX and TXT.
- How do I use this tool?
- Enter a domain name and run the lookup; the tool queries the domain's NS records server-side and lists each authoritative name server it finds. Nothing you enter is stored, and the query runs from our server rather than your own network.
- Why do NS records matter?
- NS records tell the rest of the internet which servers to ask for your domain, so a wrong or missing entry can make your whole domain unreachable. They are also what you set at your registrar when you move a domain to a new DNS provider.
- How do I read the results?
- You should typically see two or more name servers, often as matched pairs from the same provider like ns1 and ns2. If the list is empty or shows unexpected hosts, check the delegation set at your registrar.
- Why might the result differ from what I set at my registrar?
- This tool reads the NS records published in DNS by the parent zone and the domain's own zone, which can differ from your registrar panel until changes propagate. Because DNS is cached, updates can take minutes to 48 hours to appear everywhere.