What is it?
This RDAP/DNS finding means the nameservers reported by registrar or registry data do not match the nameservers observed in DNS answers. It usually appears during DNS provider changes or incomplete migrations.
Why does it matter?
Nameserver mismatch can make different resolvers see different authority paths. That can cause intermittent DNS failures, stale records, or delayed cutovers for web and mail services.
How to fix it?
Choose the intended authoritative nameserver set and make both registrar delegation and zone apex NS records match it.
dig example.com NS
dig +trace example.com NSUpdate registrar delegation if it still points to old nameservers. Update the zone apex NS records if they do not match the active provider. Wait for parent-zone TTLs before treating the mismatch as unresolved.