Why Isn't My Domain Live Everywhere Yet? Understanding DNS Propagation Delays
Summary
This guide helps you troubleshoot and resolve: Why Isn't My Domain Live Everywhere Yet? Understanding DNS Propagation Delays. Follow the steps below to fix the issue.
Common Causes
When you register a new domain or update your nameservers, you expect your website to appear immediately for every visitor. In reality, DNS changes propagate gradually across Australian and global internet service provider (ISP) caches. This means your site might load on your mobile phone but not on your office desktop, or appear live to a customer in Sydney while remaining offline for someone in Brisbane. This guide explains how DNS propagation works and how to tell whether your site is still propagating, cached locally, or experiencing actual hosting downtime.
Remember — If you host with us, you don't need to do this yourself — just Open a Ticket and our Brisbane team will get it sorted.
Quick Fix Steps
- Check your domain on a public DNS propagation tool such as Google Admin Toolbox Dig or DNSChecker.
- Clear your local DNS cache using the commands listed below.
- Try accessing your site in an incognito or private browser window.
- Test on a different network, such as your mobile data connection.
Detailed Instructions
Check DNS propagation globally
- Open a web browser and visit a public DNS lookup tool such as Google Admin Toolbox Dig or DNSChecker.
- Enter your full domain name (for example,
example.com.au). - Select the record type you are checking, usually
Afor website addresses orNSfor nameservers. - Review the results from multiple locations. Australian servers should ideally show your new IP address or nameservers, but international nodes may still display the old values.
- If results are inconsistent across locations, propagation is still in progress.
Clear your local DNS cache
Windows 10 and Windows 11
- Select Start, type
cmd, right-click Command Prompt, and choose Run as administrator. - In the User Account Control prompt, select Yes.
- Type the following command and press
Enter:ipconfig /flushdns - Wait for the confirmation message:
Successfully flushed the DNS Resolver Cache.
macOS
- Select Finder, then Applications, then Utilities, and double-click Terminal.
- Type the following command and press
Return:sudo killall -HUP mDNSResponder - Enter your Mac administrator password when prompted and press
Return.
Google Chrome browser cache
- Open Chrome and go to Settings > Privacy and security > Clear browsing data.
- Select "Cached images and files" and clear the data.
- Close and reopen Chrome.
Test from a different network
- Turn off Wi-Fi on your smartphone and use mobile data to visit your domain.
- If the site loads on mobile data but not on your office Wi-Fi, the issue is likely local network or computer caching rather than global propagation.
Troubleshooting
Understanding TTL and propagation time
DNS records include a Time to Live (TTL) value, measured in seconds. This tells resolving servers how long to cache a record before checking for updates. Common TTL values range from 300 seconds (5 minutes) to 86400 seconds (24 hours). If your previous TTL was set to 24 hours, some Australian ISPs may continue serving the old record for up to a day after you make changes.
Most DNS changes propagate within a few hours, but it can take up to 48–72 hours for all caches worldwide to refresh.
How to tell if it is propagation versus downtime
| Symptom | Likely Cause |
|---|---|
| Site loads on some networks but not others | Incomplete DNS propagation |
| Site loads nowhere, including mobile data | Possible hosting downtime or incorrect DNS record |
| Site loads after clearing local DNS cache | Local PC or browser cache |
| DNS tool shows old IP address everywhere | TTL has not yet expired at upstream ISPs |
What to do if propagation is stuck
- Verify that your nameserver or
Arecord was entered correctly at your domain registrar. A single typo in an IP address will prevent propagation. - Confirm that your hosting provider has the domain added to their server and is expecting traffic for it.
- Lower the TTL on your DNS records before making future changes to speed up propagation.
- Wait at least 24–48 hours before assuming there is a fault, as some ISP caches refresh slowly.
hosts file to force a domain to resolve. This can mask real DNS issues and cause confusion when testing from other devices.Remember — If you host with us, you don't need to do this yourself — just Open a Ticket and our Brisbane team will get it sorted.
Still Having Issues?
💻 Open a Ticket