Check what the world sees for your domain
Free, no sign-up — results in seconds.
1. You're still seeing a cached answer
Check the domain with the propagation checker. If public resolvers show the new IP but your computer doesn't, flush your local cache (ipconfig /flushdns on Windows) or test on mobile data. If resolvers still show the old IP, wait for the old TTL to expire.
2. The record doesn't exist at the new provider
After a nameserver change, the new provider only serves the records you created there. If the A record for the root domain or www is missing, the site disappears. Compare the new zone against the records you exported beforehand.
3. The root and www point to different places
example.co.za and www.example.co.za are separate names. A common mistake is updating one but not the other. Check both.
4. A typo in the IP address
One wrong digit sends visitors to someone else's server, or nowhere. Copy the IP from your hosting control panel and compare it character by character with what the checker returns.
5. The new server isn't set up for your domain
DNS only gets visitors to the server. The web server must also have your domain configured (as an addon/parked domain or virtual host). If you see a default hosting page or a “site not found” message from the host, DNS is working — the hosting account isn't.
6. No SSL certificate on the new server yet
Browsers that remember your site uses HTTPS will show a privacy warning if the new server doesn't yet have a certificate. Many hosts issue a free certificate automatically once DNS points to them, which can take a little while. Also check your CAA records don't block the new host's certificate authority.
7. DNSSEC is broken
If the domain had DNSSEC at the old provider and the DS record wasn't removed or updated, validating resolvers return SERVFAIL and the site appears completely down for many users while working for others. Check for a DS record via the All DNS Records lookup.
8. You edited DNS in the wrong place
Changes only matter at the provider that's authoritative. Look up the domain's NS records — if they point to provider X, edits made at provider Y have no effect.
Quick diagnostic checklist
- NS records point to the provider you edited?
- A record for root and www present and correct there?
- Public resolvers returning the new IP?
- Server configured for the domain and serving a valid certificate?
- No stale DS record?
Frequently asked questions
My site works on my phone but not my computer — why?
Your computer or home router has the old IP cached. Flush the DNS cache or restart the router.
I see my host's default page instead of my website
DNS is working. The hosting account doesn't have your domain set up yet, or the files haven't been uploaded.
How long should I wait before worrying?
If public resolvers have shown the correct IP for an hour or more and it still fails, the issue is almost certainly not propagation.
Looking for a more dependable host? HostFaddy web hosting and VPS hosting are backed by South African support.