Make the registrar's nameservers match the zone's NS records on Cloudflare

Why it matters

The nameservers listed at your registrar differ from the NS records inside your DNS zone, so different resolvers see different servers. It often follows a provider change where one side was not updated.

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. In a Cloudflare zone the apex NS records are managed by Cloudflare, so the fix is at the registrar. Set the registrar's nameservers to exactly the two assigned to your zone (shown on the Overview page) and remove any others.
2. If the domain is registered at Cloudflare Registrar, they are set for you, so check that no other nameservers were added manually.
3. With a deliberate multi-provider setup, make Cloudflare's apex NS and the registrar list the same full set of nameservers, across all providers.

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
• 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 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