Fix nameservers that do not answer for the domain on Cloudflare

Why it matters

A server listed as authoritative for the domain does not actually serve its zone, so lookups sent to it fail or return nothing. Some visitors then see slow or failing lookups.

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

1. A Cloudflare zone is answered only by the two nameservers Cloudflare assigned to it (see the Overview page). If your registrar lists any other nameservers, remove them there.
2. If the domain is registered elsewhere, make the change at that registrar. Cloudflare cannot edit your registrar's delegation unless the domain is registered with Cloudflare.
3. If you removed the domain from Cloudflare and added it again, the new zone has a new pair of nameservers. Set exactly the new pair at the registrar.

Read the documentation ↗(opens in a new tab)

Related

• Reported by the Nameservers and delegation check
• Delegate the domain to working nameservers
• Add a second nameserver
• Spread nameservers across more than one network
• 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