DNS-NS-SET-MISMATCH
The NS set inside the zone differs from the delegation
What it means
Resolvers cache whichever set they see first. When the parent and child disagree, behaviour depends on the resolver and problems are hard to reproduce.
How to fix it
- 1Make the apex NS records exactly match the nameservers configured at the registrar.
Re-check after the change
DNS changes can take up to the record's TTL to be seen; use Re-run on the result page to bypass our 10-minute cache.
