Free NS Record Lookup & Checker

Quick select:
Your IP:
Check the DNS record Propagation in Multi-Region Check Multi-Region
Domain Type Primary NS Responsible Person Serial Refresh Retry Expire Minimum TTL
Name Server IP Address TTL
Domain Type TTL Record Value
Trace Result
Domain Type Record Status
Domain Type Record Status
Rate this result

Check live NS DNS records, TTL values, and trace the full root-to-authoritative resolution path.

NS (Name Server) Records Overview

What is an NS record?

NS records indicate the authoritative name servers for a domain, responsible for answering DNS queries.

Why do you need an NS record?

NS records are crucial for directing traffic to the correct servers and ensuring DNS resolution for your domain.

NS record structure

An NS record includes the domain name, TTL, record type (NS), and the name server's address. Example: example.com. 3600 IN NS ns1.example.com.

How to create an NS record?

Delegation NS records are set at your domain registrar, not inside the zone: enter the authoritative nameserver hostnames your DNS provider assigns (usually two or more). List every authoritative nameserver so resolvers can still reach the zone if one server is unavailable.

FAQs

Yes, having multiple NS records provides redundancy and improves reliability.

If an NS record is incorrect, DNS queries for your domain may fail, making your website inaccessible.

Your DNS hosting provider will provide the correct NS records to use for your domain.

At least two NS records are recommended for redundancy, so DNS resolution keeps working if one nameserver is unavailable.

The registrar's NS records (the delegation) tell the world which nameservers are authoritative, while the NS records inside the zone should match them. Both must agree for reliable resolution.

NS Record Troubleshooting & Common Fixes

DNS changes in your hosting panel never take effect

A classic issue occurs when you edit DNS records (like A or MX) in your cPanel or web host, but your domain registrar is delegating authority to a completely different DNS service (such as Cloudflare, Route 53, or an old hosting account).

How to fix: Run our NS lookup tool above to see which nameservers currently control your domain. You must make your DNS edits in the control panel of the exact nameserver provider listed in the authoritative response, or update your registrar delegation to point to your new host.

Lame Delegation error (Domain becomes unresolvable)

A “lame delegation” happens when the parent registry (e.g. .com or .org) delegates your domain to a nameserver that is offline, misconfigured, or has deleted your zone file. Resolvers get a REFUSED or SERVFAIL status and your entire website and email stop working.

How to fix: Contact your DNS host to verify that your domain zone is active and loaded in memory. If you switched providers, update your registrar immediately to remove the old, non-responsive nameservers.

Custom private nameservers (ns1.yourdomain.com) fail to resolve

If you create custom branded nameservers using your own domain name (e.g. ns1.example.com and ns2.example.com), DNS resolvers face a circular dependency: they cannot resolve your nameserver's IP without asking the nameserver itself.

How to fix: You must register “Glue Records” (also called Child Nameservers or Host Records) directly at your domain registrar. Provide the static IPv4 and IPv6 addresses for ns1 and ns2 so parent TLD servers can bootstrap the resolution.

DNS Info extension for Chrome is now available

Install

Install