Nameserver-change findings compare two registry observations. They help identify a changed delegation, but do not say whether the change was authorised or whether the website works.

Enable change detection

1. Open PD Modules → Domain Radar → Settings.
2. Review Flag when a domain’s nameservers change.
3. Save and allow a successful scan to establish the domain’s first nameserver baseline.
4. Review later Nameservers changed findings under Needs attention.

The first usable nameserver list is a baseline, not a change. A later nonempty list is compared with the previous stored list. Ordering, case and trailing dots are normalised, so presentation differences alone should not raise a change finding.

Review the evidence

Read What we found for the previous and current nameservers. Compare the domain, checked time and intended DNS provider. The portfolio abbreviates long nameserver lists, so the first two displayed names are not necessarily the full delegation.

A nameserver-change finding is not a comparison with Your nameservers. That separate setting supports the optional not-using-your-nameservers rule. A domain can change between two external providers without ever using your nameservers.

Avoid a false conclusion

This is a comparison between observed snapshots, not continuous DNS monitoring or an ownership audit. Missing nameserver data does not establish a verified unchanged delegation. A failed lookup needs investigation even if an earlier change finding drops out of the open list.

If a change was expected, review it before using Accept. If it was unexpected, follow your normal authorised domain-management process. Domain Radar does not change the delegation for you.

See the PD Domain Radar Blesta guide for related tasks, or explore PD Domain Radar.