Nameservers in WHOIS Lookups
whois nameservers · check domain nameservers · ns delegation whois
How to read nameserver fields in WHOIS, match them to DNS NS records, fix delegation after migrations, and avoid split-brain DNS.
By DN01 Network Team
Registrar WHOIS nameserver fields show what the registry publishes at the TLD parent — they must match NS inside the zone and what recursive resolvers cache. Mismatch is the root cause of many «DNS works in panel» tickets.
Use WHOIS for registry view, DNS Checker for live answers, and DIG NS for resolver-specific traces.
Registrar NS vs zone NS
Update registrar glue when changing DNS provider — panel at new host alone is insufficient.
Minimum two distinct NS hostnames on different networks recommended.
Glue records required for in-bailiwick NS names (ns1.example.com for example.com).
After migration checklist
Lower TTL before cutover, change registrar NS, wait propagation, populate records at new provider.
WHOIS NS updated + DNS Checker shows same NS + spot-check MX/A/TXT.
Keep old provider read-only until TTL expires globally.
Frequently asked questions
- WHOIS NS updated but site down?
Zone at new NS may be empty or wrong A records — check authoritative answers, not just WHOIS.
- How long for NS changes?
Registry-side often minutes; caches honor prior TTL up to previous value — plan hours.
- Can WHOIS NS differ from DNS NS temporarily?
During propagation yes — document both timestamps when debugging.