Add glue records for nameservers inside your own domain

Why it matters

A nameserver is named under the domain it serves, so resolvers need its address from the registry to find it. Without that glue record resolution can fail in a loop.

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. At your registrar find the section called glue records, host records, child nameservers or personal nameservers.
2. Create a host record for each nameserver named under your domain (for example ns1.yourdomain) with its public IPv4 address, and IPv6 if it has one.
3. Make sure the same address exists as an A or AAAA record in the zone.
4. Alternatively use nameservers under a different domain, for which no glue is needed.
5. Wait for the registry to publish the change and confirm with the command below. The glue addresses appear in the additional section of the last delegation answer.

dig +trace +additional NS example.com

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
• Update glue records to match the nameserver's real address
• Check that nameservers are in sync