A nameserver change at the registrar tells the internet which servers answer DNS for your domain. Glue records are the A or AAAA addresses the parent zone publishes when a nameserver name sits inside that same domain, such as ns1.example.com for example.com.
Start at the parent zone, not inside cPanel. You can see the real path with a simple trace:
dig example.com NS +traceThe output walks from the root to the TLD, then shows the NS set the TLD actually publishes. That set is what a nameserver change at the registrar points the world toward. Shared hosting customers use ns1.logicweb.com and ns2.logicweb.com, which sit outside your domain, so they never need glue on their own zone.
What each part of the trace means
When the TLD referral lists A or AAAA records next to the NS names, those addresses are glue. If those addresses still hold an old IP, resolvers keep hitting the old servers even after you edit DNS on a host nobody recursive talks to. You changed nameservers in the wrong place. Glue updates go through the registrar and the TLD, and they often take longer than a simple A change inside your own zone, so plan for that delay rather than five minutes.
If the NS names are out-of-bailiwick, such as ns1.logicweb.com for example.com, the TLD does not need glue for them. Resolvers look up ns1.logicweb.com on their own. That is why shared hosting skips this whole step. Private nameservers under your brand are the case that needs glue.
When glue records are required
Glue exists because a nameserver name inside its own zone has no other clean way to be found. ns1.logicweb.com for example.com is outside the zone, so resolvers look it up separately and never need glue on example.com. Shared customers therefore skip this ticket. The walk above is for people who built private nameservers and later moved the IP underneath them without updating the parent.
Resellers who invent names like ns1.theirbrand.com must register matching glue, or lookups loop. After you fix glue at the registrar, query the TLD again rather than only your child zone. Recursive caches keep old glue until that TTL expires. Changing the A record for ns1 only inside the child zone, while glue still points elsewhere, is the same loop in a different form.
After glue is correct
Once the parent publishes the right addresses, you can safely change A records in the new zone. The TTL on NS data at the TLD is not the same as the TTL on your website A records. Read TTL strategy for cutovers before you move the site the same afternoon you create private nameservers.
Tagged
Was this article helpful?
Be the first to rate this article.
