Update glue records to match the nameserver's real address

Why it matters

The address stored at the registry for one of your nameservers differs from the address the nameserver really has. Resolvers that rely on the stored address may contact the wrong server or none.

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. Find the nameserver's correct current address and check that it matches the A or AAAA record in your zone.
2. At your registrar, in the host record or glue section, edit the nameserver's address to the correct value.
3. Wait for the registry to publish the change, then check with the command below that the address in the delegation is the right one.

dig +trace +additional NS example.com
# replace ns1.example.net with the nameserver named in the finding
dig +short A ns1.example.net

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 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
• Check that nameservers are in sync