Spread nameservers across more than one network on Cloudflare
Why it matters
All of your nameservers sit in the same small address range, so one network or provider failure would take them all down. Placing them on different networks keeps the domain reachable.
Staged change. Do this in stages and check each one before the next, so a mistake does not break your site or your mail.
The fix
- Cloudflare's nameservers are anycast and spread across many networks, so this finding does not point at a real weakness if the domain uses only Cloudflare's two assigned names.
- If your registrar lists other nameservers as well, make sure they are intentional. Mixing providers without syncing the zone causes the consistency findings.
Related
- Reported by the Nameservers and delegation check
- Delegate the domain to working nameservers
- Add a second nameserver
- Fix nameservers that do not answer for the domain
- Make unreachable nameservers answer, or remove them
- Give each nameserver name an IP address
- Point nameserver names at public IP addresses
- Point nameserver names at A or AAAA records, not CNAMEs
- Make the registrar's nameservers match the zone's NS records
- Make all nameservers publish the same NS records
- Add glue records for nameservers inside your own domain
- Update glue records to match the nameserver's real address
- Check that nameservers are in sync
Scan your domain to see whether this applies to you.