Skip to content

Getting started

Why your phone still shows the old site

DNS cache and carrier resolvers explain why a phone lags behind your laptop after you change nameservers.

Updated Aug 29, 20263 min read12 reads
Why your phone still shows the old site
Why your phone still shows the old site after a DNS change

Your phone still shows the old site because DNS caches keep the previous answers until the TTL runs out. A nameserver change does not clear every resolver at once, so carrier networks often lag behind a laptop that already looks correct. The copy on the new server is usually fine; the phone simply has not requested a fresh lookup yet.

Test on cellular instead of office Wi-Fi

Turn off Wi-Fi so the device uses LTE or 5G. That path hits the carrier’s recursive resolver, not the one on your office or home network. A laptop that already shows the new site only proves one lucky cache miss. It is not proof that every network on the internet has updated.

Safari can keep an old page in memory even after DNS moves on. Close the tab fully rather than tapping refresh alone. Chrome on iOS still uses WebKit, so the same step helps there. If you opened the site inside an app, force-quit the app because it may hold its own cache separate from the system browser.

Compare public DNS with the authoritative answer

Check what a public resolver still holds against what the authoritative nameservers return. When the domain uses LogicWeb, those nameservers are ns1.logicweb.com and ns2.logicweb.com.

bash
dig example.com A +ttlunits @1.1.1.1
dig example.com AAAA +short

If the authoritative side already has the new A record and 1.1.1.1 still shows remaining TTL on the old address, you wait for that timer. If AAAA still points at the old host, dual-stack phones may prefer IPv6 and keep loading the previous server. Correct the AAAA record instead of changing nameservers again.

What to avoid while caches catch up

Do not flip nameservers back and forth to try to unstick a phone. That resets the TTL clock for everyone, including visitors who had already received the new records. Lower the TTL a day before your next move if you want a shorter wait next time. Shared hosting and VPS do not change this behavior, because the delay lives in DNS rather than in the server type.

A check from outside your own network settles most doubts. If a remote lookup already returns the new site, the files and the new host are in place. Your phone will follow once its resolver forgets the old answer.

Share

Send this article

Need someone else to do this? Send them the link — the commands are in the article.

Was this article helpful?

Be the first to rate this article.