NS Lookup with DIG
dig ns lookup · nameserver check · dns ns record · authoritative dns
How to check NS records with DIG, delegation glue, mismatched registrar NS, and fixing DNS after hosting moves.
By DN01 Network Team
NS records identify authoritative nameservers for a zone. If NS at the registrar does not match the NS inside the zone, resolution fails unpredictably. NS lookup is step one when «DNS looks fine in the panel but the world sees nothing».
Run DIG type NS, then cross-check with WHOIS nameserver fields and a full DNS Checker pass for sibling records (A, MX, TXT).
Delegation and glue
In-bailiwick NS (`ns1.example.com` for `example.com`) need glue A/AAAA records at the parent. Out-of-bailiwick NS (`ns1.hosting.com`) rely on the parent of the NS hostname.
Minimum two NS hosts on different networks is best practice for redundancy.
Debugging wrong NS after a move
Compare registrar NS, zone NS, and cached recursive answers. Update registrar first when switching DNS providers, wait for propagation, then populate records at the new host.
SOA serial increments when the zone changes — note it in change tickets.
Frequently asked questions
- Can NS change without other records changing?
Yes — nameserver migrations swap NS while copying A/MX/TXT. Verify all records after NS cutover.
- Why two NS names resolve to one IP?
Misconfiguration — providers expect diverse anycast or separate hosts. Fix for resilience.
- Does NS affect email?
Indirectly — if NS points to wrong host, MX published there is what the world uses.