Domains

Child nameservers and glue records: register private nameservers at your registrar

What child nameservers and glue records are, why private nameservers like ns1.yourbrand.com need them, how to register them at a registrar and point domains to them, and how to verify.

IntermediateReseller hosting3 min read

Private nameservers such as ns1.yourbrand.com let resellers show their own brand instead of the host's DNS hostnames. Because those nameservers sit inside the domain they serve, they need child nameservers with glue records registered at the domain registrar. This guide explains why and how.

Before you start

  • A domain for your brand, registered at any registrar.
  • The IP addresses to use for ns1 and ns2. For an MdmHost reseller or master reseller plan, ask support via a ticket which IPs your private nameservers should use.
  • Access to your registrar account.

What glue records are

To find example.com, a resolver asks the .com registry which nameservers serve it. If the answer is ns1.yourbrand.com, and yourbrand.com itself uses ns1.yourbrand.com, the resolver is stuck in a loop: it cannot look up the nameserver's IP without already knowing it. A glue record solves this. The registry stores the nameserver's IP address directly and hands it out together with the delegation.

A child nameserver (also called a host record or registered nameserver) is a nameserver hostname under your domain that is registered with the registry together with its glue IP.

Register child nameservers at your registrar

Every registrar names this differently: Child Nameservers, Register Nameservers, Host Records or Glue Records.

  1. Log in to the registrar and open your brand domain.
  2. Find the child nameserver section.
  3. Add ns1 with the first IP and ns2 with the second IP.
  4. Save. The registry usually updates within minutes to a few hours.

Add matching A records in DNS

The zone for yourbrand.com on your hosting server must also contain A records for ns1 and ns2 with the same IPs. On cPanel hosting, check cPanel → Domains → Zone Editor; in WHM, resellers can see the zone under DNS Functions → Edit DNS Zone.

Point the brand domain and client domains

  1. Set the nameservers of yourbrand.com itself to ns1.yourbrand.com and ns2.yourbrand.com, now that glue exists.
  2. In WHM, set your reseller nameservers to the same names so new accounts show them.
  3. Tell clients to use these nameservers at their own registrars.

Verify the glue records

Ask the TLD servers directly. For a .com domain:

dig +norec @a.gtld-servers.net yourbrand.com NS

The ADDITIONAL SECTION should list ns1 and ns2 with your IPs. Then check that the nameservers answer:

dig @ns1.yourbrand.com yourbrand.com SOA

Tip: You can also check the delegation with the WHOIS checker, which shows the nameservers registered for a domain.

Troubleshooting

  • Registrar says the host does not exist: create the child nameserver first, then use it as a nameserver for a domain.
  • Glue IP differs from the A record: update both so they match; mismatches cause intermittent failures.
  • Domains stop resolving after a server move: the glue still points to old IPs. Update the child nameservers at the registrar.
  • Cannot delete a child nameserver: other domains still use it. Move them away first.

Frequently asked questions

Do I need glue for nameservers on another domain?

No. Glue is only required when the nameserver hostname is inside the domain being delegated, or under the same TLD for some registries.

Do ns1 and ns2 need different IPs?

Most registries accept the same IP, but separate IPs are better practice. Use what your host provides.

How long do glue changes take?

The registry updates quickly, but resolvers may cache the old delegation for up to the TLD's TTL, often 48 hours for .com.

Next steps

Was this guide helpful?

Still stuck?

Ask MdmHost AI for a quick answer, or open a ticket and our team will take a look. We are here 24/7.

Ask MdmHost AIOpen a ticket

Related guides