IPCheckIP Space
DNS Troubleshooting

DNS changed but website still shows old IP

If a domain was moved to a new server but visitors still reach the old site, check DNS records, cache, IPv6 and CDN layers in order.

Most common causes

TTL cacheResolvers may still cache the previous A or AAAA record.Wait for the old TTL to expire.
Wrong record editedThe root domain and www subdomain are separate names.Check both records explicitly.
AAAA still oldIPv6 users may reach the old server through an old AAAA record.Compare A and AAAA records.
CDN cacheA proxy or CDN may still route to the old origin.Review CDN DNS and origin settings.

Quick checklist

  1. Run DNS Lookup for A and AAAA records.
  2. Check the root domain and www separately.
  3. Compare the returned IP with the new server public IP.
  4. Check whether a CDN or DNS proxy is enabled.
  5. Use HTTP Header Check to see whether the response comes from an old redirect or cache.

If only some users see the old server, resolver cache is likely. If every lookup still shows the old IP, the authoritative DNS record may not have been changed correctly.

FAQ

How long should I wait?

Wait at least the previous TTL. If the old TTL was high, some resolvers may keep the old answer for hours.

Can browser cache cause this?

Browser cache can show old content, but it does not usually change DNS answers. Check DNS and HTTP headers separately.

Why does mobile show the new site but Wi-Fi shows old?

Mobile and Wi-Fi often use different DNS resolvers with different cache states.

Related guides

DNS PropagationUnderstand TTL and cache.WWW vs Root DomainFix split domain records.Website Not LoadingFollow a full checklist.