An NS mismatch occurs when nameservers declared at registrar level (delegation) don't match NS records in your DNS zone. This inconsistency can cause unpredictable behavior: some resolvers will use delegation NS, others zone NS. While this often works, it's bad practice that complicates troubleshooting and may violate RFCs.
Symptoms of NS Mismatch
- whois shows different NS than dig NS example.com
- Some validation tools flag the inconsistency
- Unpredictable DNS behavior depending on resolver
- Problems during domain transfers or migrations
Causes of Mismatch
- Partial change: You changed NS at registrar but not in zone, or vice versa.
- Incomplete migration: During transfer, zone NS weren't updated to match new provider.
- Copy-paste error: Typo in NS name causing them not to match.
Diagnosis and Correction
- Check NS at registrar: whois example.com | grep "Name Server"
- Check NS in zone: dig NS example.com
- Compare both lists: they should be identical.
- Correct one to match (usually zone aligns with registrar).
Detection with MoniTao
MoniTao detects NS inconsistencies:
- Automatic comparison between delegation and zone
- Alert on detected mismatch
- Verification of accessibility of all declared NS
NS Consistency
- NS at registrar and in zone must be identical
- After NS change at registrar, update the zone
- Use DNS validation tools to verify consistency
- Document your official NS for reference
FAQ - NS Mismatch
Does mismatch prevent site from working?
Usually no. Registrar NS (delegation) are used. But it's bad practice that can cause problems.
Which NS is authoritative?
Delegation (registrar) is authoritative for initial resolution. Zone NS are informational for this resolution.
Should I fix an inherited mismatch?
Yes. Even if it works, fix it to avoid future problems and pass validations.
How do large providers handle this?
They automatically synchronize zone NS with delegation, avoiding this problem.
Ready to Sleep Soundly?
Start free, no credit card required.