Redundant DNS servers
NS servers are the "directories" that answer DNS questions about your domain. Having at least two NS servers ensures that if one goes down, …
Analyse my site for freeUnderstanding "Redundant DNS servers"
A domain's NS (Name Servers) are the authoritative servers, the ones that ultimately answer any DNS question about it. Redundancy means having at least two independent NS servers (ideally on physically distinct networks and infrastructure), so that the failure or unavailability of a single server doesn't cause the domain to vanish entirely from the internet.
This is such a fundamental requirement that it's mandated by the DNS protocol itself — RFC 1034 formally recommends a minimum of two NS servers for any domain — but it's sometimes still overlooked with self-hosted or poorly migrated DNS setups.
How TheSiteFuse checks "Redundant DNS servers"
TheSiteFuse queries the root domain's NS records and counts the number of distinct servers returned (up to 4 displayed). Two or more servers passes the check. A single NS server (or none, a very rare case) triggers a warning flagging a risk of total DNS outage if the single server goes down.
Why "Redundant DNS servers" matters
- Total domain outage — with a single NS server, any unavailability of that server (hardware failure, network outage, unplanned maintenance, targeted DDoS attack) makes the domain entirely unreachable — website, email, every DNS-dependent service stops simultaneously.
- No tolerance for geographic outages — even with two servers, if they're hosted in the same physical location or with the same provider, a local incident (power outage, datacenter issue) can affect both at once — redundancy needs to be both numerical and geographic/organisational.
- Prime target for denial of service — a domain with a single DNS point of failure is a particularly effective target for an attacker looking to cause maximum impact with minimum effort.
Fix "Redundant DNS servers" step by step
Recommended solution — third-party managed DNS
Almost every registrar and managed DNS host (Cloudflare, OVH, Gandi, AWS Route 53…) automatically provides several redundant, geographically distributed NS servers — no manual configuration is needed beyond choosing the provider.
If you run your own DNS servers
- Deploy at least 2 NS servers, ideally 3 to 4, on physically distinct networks and data centers.
- Consider a mix of providers (e.g. a self-hosted primary + a managed secondary DNS service) to eliminate any common point of failure.
Verification
dig yourdomain.com NS +short
Reference resource
To deepen your understanding of the technical concepts behind this check, see the dedicated Wikipedia article.
Wikipedia — Redundant DNS serversDoes your site pass this check?
Run the free full audit (120 checks) and instantly discover what needs fixing.