Home › Knowledgebase › KB-1622

Why Your New Website Domain Isn't Live Everywhere Yet: DNS Propagation Explained

Summary

This guide helps you troubleshoot and resolve: Why Your New Website Domain Isn't Live Everywhere Yet: DNS Propagation Explained. Follow the steps below to fix the issue.

Quick Tip: Need immediate assistance? 💻 Open a Ticket

Common Causes

After updating your DNS records or launching a new website for your accounting practice, you may find the site loads on your home network but not on your office connection, or appears to some clients in Brisbane but not others. This is usually caused by DNS propagation, the time it takes for updated DNS records to spread across the internet. This article explains how DNS propagation works across Australian ISPs, how to check whether the fault is local DNS caching, your router, or the authoritative nameserver, and what tools you can use to verify record resolution before assuming your hosting is broken.

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

  1. Clear your web browser cache.
  2. Flush your computer's DNS cache.
  3. Restart your office router.
  4. Check your DNS records using an online propagation tool.
  5. Wait up to 48 hours for full propagation across Australian ISPs.

Detailed Instructions

Step 1: Clear your browser cache

Your browser may be storing an old version of the website. Clearing the cache forces it to request fresh DNS information.

  1. Open your web browser.
  2. Press Ctrl + Shift + Delete on Windows, or Cmd + Shift + Delete on macOS.
  3. Select Cached images and files.
  4. Click Clear data or Clear browsing data.
  5. Restart the browser and revisit your website.

Step 2: Flush your computer's DNS cache

Windows and macOS store DNS lookups locally. Flushing this cache removes outdated records.

On Windows

  1. Press Windows Key + R to open the Run dialog.
  2. Type cmd and press Ctrl + Shift + Enter to open Command Prompt as administrator.
  3. Type ipconfig /flushdns and press Enter.
  4. Look for the message confirming the DNS resolver cache was flushed.

On macOS

  1. Open Terminal from Applications > Utilities.
  2. Type sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder and press Return.
  3. Enter your administrator password when prompted.

Step 3: Restart your office router

Small business routers often cache DNS entries to speed up browsing. A power cycle clears this cache.

  1. Switch off your router at the power point.
  2. Wait at least 30 seconds.
  3. Switch the router back on and wait for all indicator lights to stabilise.
  4. Reconnect your devices and test the website again.

Step 4: Check DNS records using online tools

Use a public DNS lookup tool to see what records are being returned globally and across different regions.

  1. Open a DNS propagation checker such as Google Admin Toolbox Dig, MXToolbox, or WhatsMyDNS.
  2. Enter your domain name (for example, www.youraccountingpractice.com.au).
  3. Select the record type you updated, usually A or CNAME.
  4. Review the results from multiple locations, including Australian cities where available.
  5. If some locations show the old IP address while others show the new one, propagation is still in progress.

Step 5: Verify against your authoritative nameserver

If online tools show inconsistent results, check whether your authoritative nameserver is already serving the correct record.

  1. Log in to your domain registrar or DNS hosting control panel.
  2. Navigate to the DNS management or zone editor section.
  3. Locate the record for your website (for example, the A record for www or the root domain).
  4. Confirm the value matches the IP address provided by your web host.
  5. If the record is incorrect, update it and save the changes.

Troubleshooting

Site works at home but not in the office

This usually points to your office router or local network DNS cache. Restart the router as described above. If the issue persists, your office may be using a local DNS server that is holding a stale record. Contact your internal IT administrator or your MSP to clear the server-side cache.

Site works for some clients but not others

Different Australian ISPs cache DNS records for different lengths of time, defined by the Time to Live (TTL) value on your DNS record. A high TTL (for example, 86400 seconds or 24 hours) means some ISPs will continue serving the old record until that period expires. Lowering the TTL before making DNS changes can speed up future updates, but it will not fix a change that has already been made.

DNS records look correct but the site still will not load

Confirm that your web hosting is active and that the IP address in your DNS record matches the server where your website is hosted. Also check that your domain registration has not expired. If the DNS record is correct at the authoritative nameserver and propagation tools worldwide show the new address, but the site remains inaccessible, the issue may be with your hosting account rather than DNS.

DNS changes can take anywhere from a few minutes to 48 hours to fully propagate across all Australian ISPs and global networks. In most cases, updates are visible within a few hours.

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?

Need more help? If the issue persists after trying these steps, please open a support ticket and our team will assist you.

💻 Open a Ticket