Know if your domain's nameservers change or go dark
Your NS records determine which nameservers are authoritative for your entire domain. Change them by mistake and every DNS record on the domain is affected at once, not just one — and if every nameserver they point to goes unreachable, the effect is the same.
NS changes and nameserver outages affect the whole domain
An unexpected NS change can come from a registrar-panel mistake, a delegation left over from switching DNS providers, or unauthorized account access — and because it redirects every query for the domain at once, its effect is domain-wide rather than limited to a single record. A single nameserver going unreachable is usually a smaller problem on its own, since the others keep answering; it's only domain-wide when every nameserver for a domain goes down together.
NSexample.comns1.example-dns.com, ns2.example-dns.com→ns1.unknown-provider.net, ns2.unknown-provider.net
An unexpected NS change redirects every DNS query for the domain to a different provider.
How OneDollarDNS catches this
OneDollarDNS treats NS records like any other monitored record: an unexpected change generates an alert with the old and new value, at the same hourly (or 5-minute Priority Host) cadence used for every other record type. Separately, if one of a domain's nameservers is briefly unreachable, we try another before treating it as a problem; if every nameserver for a domain is unreachable, that check is skipped rather than reported as records being removed, and a dedicated "nameservers unreachable" alert fires only after repeated failures. See how monitoring works for the full mechanics.
What this doesn't do
OneDollarDNS checks a domain's own configured nameservers directly — it isn't a substitute for your DNS provider's own status page or a global network-monitoring service, and it doesn't monitor DNSSEC validation. For background on what NS records do, read what are NS records.