How to Check Nameserver Records and DNS Delegation
Nameserver (NS) records define which DNS servers are authoritative for your domain. They are the foundation of your entire DNS infrastructure. If NS records are wrong, every other record (MX, SPF, DKIM, A, CNAME) becomes unreachable. Before troubleshooting any DNS issue, always verify NS records first.
Look up nameservers instantly
Use our free NS Lookup tool to see all authoritative nameservers for any domain.
Step 1: Query NS Records for Your Domain
Use the NS Lookup tool to retrieve the nameservers published in your domain's DNS zone. From the command line:
dig example.com NS +short
# or
nslookup -type=ns example.comYou should see two or more nameserver hostnames. Record these for comparison in the next step.
Step 2: Compare with Registrar Nameservers
Log into your domain registrar (e.g., Namecheap, GoDaddy, Cloudflare) and check the nameservers configured there. These must match the NS records returned by DNS. A mismatch between registrar settings and zone NS records is called a lame delegation and will cause intermittent DNS failures.
Step 3: Verify Each Nameserver Responds
Query each nameserver individually to confirm it responds with your domain's records:
dig example.com A @ns1.dnsprovider.com
dig example.com A @ns2.dnsprovider.comBoth should return the same result. If one fails or returns different data, there is a synchronization or configuration issue with your DNS provider.
Step 4: Check for Subdomain Delegation
If you delegate subdomains to different nameservers (e.g., a separate DNS provider formail.example.com), verify those NS records separately. Use the NS Lookup tool with the subdomain to confirm delegation is correct.
Step 5: Monitor NS Record Health
Nameserver changes are rare but high-impact. After switching DNS providers, always verify NS propagation using the NS Lookup tool. Check that your MX records still resolve correctly with the MX Lookup tool, and run the SPF Checker to confirm authentication records are intact.
Frequently Asked Questions
What is the difference between registrar nameservers and DNS zone NS records?
Registrar nameservers are set at your domain registrar and tell the TLD servers where to find your DNS. DNS zone NS records are published in your zone file. Both should match. A mismatch between them is called a lame delegation and can cause DNS resolution failures.
How many nameservers should I have?
At minimum, you should have two nameservers for redundancy. Most DNS providers offer two to four. Having nameservers in different networks or geographic locations improves resilience against outages and DDoS attacks.
Can wrong NS records affect email delivery?
Yes. If your NS records are misconfigured, DNS queries for your MX, SPF, DKIM, and DMARC records will fail. This means sending servers cannot find your mail servers or verify your authentication records, leading to bounced or rejected email.