Give each nameserver name an IP address

Why it matters

A nameserver name listed for the domain does not resolve to any address, so resolvers cannot reach it. It is typically a typo at the registrar or a deleted record.

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. Look at the nameserver names registered for the domain and compare them with the names your DNS provider gave you. A typo at the registrar is the most common cause.
2. If the name is under your own domain (for example ns1 of your domain), register it as a host or glue record at your registrar with its IP address, and create the matching A or AAAA record in the zone.
3. If the name belongs to a provider, correct it at your registrar or use the names the provider currently documents.
4. Confirm the name resolves with the command below.

dig NS example.com +short
# replace ns1.example.net with a nameserver from the delegation
dig +short A ns1.example.net
dig +short AAAA 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
• 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