Why Does a Website Load on One Network but Not Another After a DNS Update?

After a DNS change, different networks can reach different destinations because of resolver caching, multiple authoritative nameservers, split DNS, IPv4 and IPv6 differences, or a local hosts-file override. Seeing the new site once does not prove every resolver is using the same answer.

What to check

Query the authoritative nameservers and compare A, AAAA, CNAME, and delegation results from affected networks. Check TTLs, DNSSEC validation, local resolver cache, and whether the web server accepts both address families and the correct host name.

Recommended next step

Confirm the authoritative zone is consistent, keep the prior destination available during the expected cache window when possible, and test using more than one external resolver. Avoid repeated record changes that restart propagation uncertainty.

How Informatix Systems can help

Informatix Systems provides DNS, domain, and website migration services. We can review the affected systems and workflow, help narrow down the cause, and outline a practical implementation path. Contact us with the platform involved, when the issue began, and non-sensitive error details.