How nameservers work

Nameservers are the directory that tells the internet which servers hold your domain’s DNS records. They are not the website itself. Until you update the nameserver setting at your registrar, the old host still answers public lookups, even if every file is already on our side. Shared hosting at LogicWeb uses ns1.logicweb.com and ns2.logicweb.com. Changing nameservers is how you finish a migration, not how you start one.

What happens when someone looks up your domain

Your device asks a recursive resolver for an answer. That resolver asks the top-level domain which nameservers are authoritative for your name. The TLD returns the NS set currently published at the registrar. Those nameservers then return A, MX, TXT, and other records. Nothing pushes a live update to every network when you edit a record. TTL is simply how long a resolver is allowed to remember the previous answer. Lower the TTL a day before a cutover if you can. Do not leave very short TTLs in place forever, because the extra queries do not help once the move is complete.

If ns1.logicweb.com already shows the new A record and a public resolver still shows the old one, you are waiting on cache. If our nameserver still shows the old A record, the wrong zone was edited. Mobile carriers often keep old answers longer than office Wi-Fi, so test on LTE as well.

Glue records and private nameservers

Glue becomes a problem when someone creates names like ns1.example.com inside the same domain. Without matching A records at the parent registry, the lookup can loop and fail worldwide. Shared hosting customers should not invent private nameservers. Use our nameservers instead. Resellers who truly need child nameservers create them with the correct IPs at the registrar first, then point the domain at those names. Wrong glue IPs can take a domain offline in a way that looks like a general outage.

Check the server that should know the answer

Ping and traceroute do not prove what DNS is serving. These two queries do:

dig example.com NS +short
dig example.com A @ns1.logicweb.com +norecurse

The first command shows who the world currently treats as authoritative. The second shows what our nameserver would answer without asking anyone else. If those results disagree with the registrar control panel, the registrar may not have pushed the NS change to the TLD yet. Wait for that update. Copy files first, preview the site on the new host, and only then change nameservers. Mail is the sharp edge because IMAP keeps state on the old server. Keep the old host billed until public resolvers agree on the new answers. Removing the old account the same afternoon you change NS removes your easy rollback.

Paste both dig results in a support ticket when you need help. That lets us see whether you are still inside TTL or looking at the wrong zone.