Nameservers
Nameservers agree on the NS set
ns.set-agreement
Disagreement here means resolvers can end up with different views of the zone.
What this check measures
This asks each authoritative nameserver, separately, for the zone's own NS record set and compares the answers. It is a different question from the one the delegation section asks: that one compares the registry against the zone, this one compares the zone against itself.
Disagreement means the servers are not serving the same zone. A resolver learns the nameserver set from whichever server it happened to ask, caches it, and sends its next queries to those — so which servers a visitor ends up using depends on which server answered them first. Two visitors, two views, no pattern to it.
It nearly always travels with a serial mismatch, and it is the same underlying fault seen from another angle: replication has stopped, or an edit was applied at one provider and not the other. Where it appears on its own, the usual cause is a zone hand-edited on one server.
How to fix it
Compare the SOA serials first — the serial-agreement check in this report shows them per server. The server reporting the lower serial is the one that has not received the update, which turns a disagreement into a replication problem with a direction.
For a primary and secondaries, two things account for most of it: NOTIFY not being sent by the primary, and transfers refused by the secondary's ACL. The secondary's log will name the reason, which beats inferring it from outside.
Where two independent providers each hold a copy, the sync pipeline is the suspect rather than either provider. This is the failure mode that makes managing both zones from one source of truth worth the setup.
References
Run the full report on a domain
There is no separate test for this one. Entering a domain runs the full report — all 62 checks, across delegation, mail authentication, TLS and registration — and Nameservers agree on the NS set is one of them, with the evidence behind its result.
Also in Nameservers
- Every nameserver is authoritative
- At least two nameservers
- Nameservers are independent of each other
- Nameserver hostnames are valid
- IPv6 reachability
- Nameservers are not open resolvers
- Nameservers agree on the SOA serial
- Nameservers respond over TCP
- Nameservers respond over UDP
- Zone transfers are not open to the world