NS at the registrar vs NS in the zone

Your domain has two places where nameserver records can appear, and they do different jobs. The registrar NS set is what the parent TLD publishes to the world. The NS records inside your DNS zone should match that set so resolvers stay consistent. If they differ, some resolvers follow the parent while others still use older cached data. Change nameservers at the registrar first, then keep the in-zone NS records aligned with that choice.

Why the registrar NS set is the source of truth

When someone looks up your domain, the TLD servers answer with the nameservers you set at the registrar. That referral is what the internet actually follows. Editing NS only inside cPanel does not update the TLD. You can confirm the parent records with a non-recursive query against a TLD server.

dig example.com NS @a.gtld-servers.net +norecurse

Use the correct TLD server for your domain’s extension. If that answer still lists the old host, the registrar still points elsewhere. The zone file is not the authority for which nameservers the world uses. The registrar is. Your zone should simply agree with it.

When NS matches but records still look wrong

If the registrar and the zone both list the same NS names, but A records still look wrong, you may be editing the wrong zone. That can happen with a parked copy, a subdomain zone, or an old cPanel DNS zone that ns1 is not serving. Query the authoritative nameserver for the A record, not only for NS.

Another confusing case is when the in-zone NS list does not match the TLD. For example, the zone lists ns1 and ns2 while the TLD lists ns1 and ns3. Different tools can show different answers, and it is easy to think you are looking at one consistent picture.

How LogicWeb customers should set nameservers

On shared hosting, set the nameservers at your registrar to ns1.logicweb.com and ns2.logicweb.com. cPanel’s zone already lists those names, so leave the in-zone NS records alone unless you have a clear reason to edit them. Resellers who use private nameservers need glue records, registrar NS, and in-zone NS all pointing at the same hostnames and the same IPs. A mismatch is not slow propagation. It is three places telling different stories. Treat the registrar as the parent, make the zone agree, then wait out the TLD TTL.

If NS already matches and phones still hit an old server, leftover AAAA records can be the cause. See our guide on leftover AAAA records for that case.