Why isn't my website update showing up?
Summary
This guide helps you troubleshoot and resolve: Why isn't my website update showing up?. Follow the steps below to fix the issue.
Common Causes
After you update your DNS records—such as A, CNAME, or MX entries—those changes do not appear instantly across the internet. This delay is known as DNS propagation. It happens because internet service providers (ISPs) and network caches store DNS information for a set period defined by the Time to Live (TTL) setting. As a result, some visitors may see your updated website while others still see the old version until the cache expires.
Quick Fix Steps
- Confirm that your DNS record changes have been saved and published in your domain registrar or hosting control panel.
- Check the TTL value assigned to the record you changed; this determines how long caches hold the old information.
- Wait for the TTL period to elapse before expecting changes to appear globally.
- Use an online DNS propagation checker to verify that your records have updated across multiple locations.
Detailed Instructions
Understanding TTL and Propagation
TTL is measured in seconds and tells DNS resolvers how long they can cache a record before checking for updates. For example, a TTL of 3600 seconds means caches may hold the old record for up to one hour. Lowering the TTL before making changes can reduce propagation time, but the previous TTL may still be cached by some networks until it expires.
Checking Your DNS Records
- Log in to your domain registrar or DNS hosting control panel.
- Navigate to the DNS Management, Zone Editor, or Advanced DNS section.
- Locate the record you updated (for example, an
Arecord for your website or anMXrecord for email). - Verify that the value, such as the IP address or mail server address, is correct.
- Note the TTL value to estimate how long propagation may take.
Verifying Propagation Globally
- Open a DNS lookup tool such as Google Admin Toolbox Dig, MXToolbox, or DNSChecker.org.
- Enter your domain name and select the record type you changed (for example,
A,CNAME, orMX). - Review the results from multiple servers and regions to see whether the new record is visible worldwide.
- If some locations still show the old record, wait for the TTL period to pass and check again.
Clearing Local DNS Cache
If your computer is still showing the old website, your local DNS cache may need to be cleared.
Windows
- Press
Windows Key + R, typecmd, and pressCtrl + Shift + Enterto open Command Prompt as administrator. - Type the following command and press
Enter:ipconfig /flushdns
macOS
- Open Terminal from Applications > Utilities.
- Type the following command and press
Enter:sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. You may be prompted to enter your Mac administrator password.
Troubleshooting
Website Still Shows Old Content After TTL Has Passed
- Double-check that you edited the correct DNS zone for your domain.
- Ensure the changes were saved or published, not left in a draft state.
- Confirm that you are not viewing a cached version of your website in your browser; try opening the site in an incognito or private window.
- If you recently changed your domain’s nameservers, propagation can take longer—up to 48 hours in some cases.
Email Not Working After MX Record Changes
- Verify that the MX record points to the correct mail server address provided by your email suite.
- Check that any associated
AorCNAMErecords for mail subdomains are also correct. - Remember that email delivery may be disrupted during propagation, as some sending servers may still use the old MX record.
Some Users See the New Site While Others See the Old One
This is normal during propagation. Different ISPs and networks refresh their DNS caches at different intervals based on the TTL. No action is required other than waiting for the TTL to expire.
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