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

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. Decide which set is correct. It is normally the set your current DNS provider assigned to the zone.
2. Update the NS records at the apex of the zone to that set, and update the nameservers at the registrar to the same set.
3. Keep any old nameserver that still serves the zone in both places until the change has been published everywhere. Then remove it from both.
4. Confirm with the commands below that the parent and the zone agree.

# what the parent (registry) says
dig +trace NS example.com
# what the zone itself says
dig NS example.com +short

The examples use example.com. Replace it with your own domain.

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