How to fix: Less Than 2 Authoritative Nameservers
RFC 1035 requires at least two authoritative nameservers for redundancy. A single NS means the entire domain goes dark when that server is unreachable.
Why it matters
If the single authoritative nameserver goes offline, the entire domain becomes unreachable. Attackers who DoS or compromise one server can take your domain offline.
DNS relies on redundant nameservers to prevent single points of failure. Having only one NS means any outage, DDoS, or maintenance window makes your entire domain unreachable for all users.
How to fix it
- 1Add a second NS record pointing to a nameserver on a different subnet or provider.
- 2Consider using a managed DNS provider (Cloudflare, Route 53, NS1) which provides multiple geographically distributed nameservers automatically.
Code examples
Check NS records
dig +short NS example.comDNS zone file: two NS
example.com. IN NS ns1.example.com.
example.com. IN NS ns2.example-backup.com.References
Detected automatically by VulnRadar. The check id is dns-ns-record-count, stable across every scan so you can filter or diff on it.
More dns checks
Questions
- How severe is Less Than 2 Authoritative Nameservers?
- VulnRadar rates this high severity in the dns category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id dns-ns-record-count, which stays the same between runs so you can filter, diff, or gate CI on it.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.