DNS propagation is the time it takes for changes to your Domain Name System (DNS) records to be recognised across the internet. When you update name servers, change an A record, add an MX record, or make other DNS changes, those updates are not visible everywhere immediately. Different networks and DNS resolvers may continue using older cached information until that cache expires.

Understanding DNS propagation is important because it helps explain why a website, email service or other domain-based service may work in one location but not in another shortly after a DNS change. It is a normal part of how DNS works and does not usually mean there is a fault with your hosting or domain.

DNS, or Domain Name System, is the service that translates domain names such as example.com into the technical records used by browsers, mail servers and other systems. When a DNS record is changed, internet providers, devices and public DNS resolvers may keep a saved copy of the old result for a period of time. This saved copy is called a cache.

DNS propagation is the period during which old cached data is gradually replaced by the new DNS information. During this time, some users may reach the new service while others still reach the old one.

Common changes that can trigger DNS propagation include:

* Updating your domain’s name servers

* Changing the A record for a website

* Updating the MX records for email

* Adding or editing a CNAME record

* Moving a website to a new hosting provider

* Connecting a domain to Microsoft 365 or another third-party service

DNS propagation is influenced by DNS caching. Each DNS record has a setting called TTL, which stands for Time To Live. TTL tells DNS resolvers how long they can keep a cached copy of a record before checking again for an updated version.

If a resolver cached your old DNS record before you made a change, it may continue serving that old record until the TTL expires. Once the cache expires, the resolver requests the latest DNS information and begins serving the updated record.

This process does not happen in a single global update. Instead, it happens gradually across many systems, including:

* Internet service provider DNS resolvers

* Public DNS services such as Google Public DNS or Cloudflare DNS

* Local computer and mobile device caches

* Corporate and office network caches

* Browser-level DNS caching in some cases

Because these systems refresh at different times, propagation can appear inconsistent until the old cached data has cleared everywhere relevant.

In many cases, DNS changes begin appearing within a few minutes to a few hours. However, full DNS propagation can take up to 24 to 48 hours depending on the type of change, the previous TTL value, and the behaviour of individual DNS resolvers.

Name server changes often take longer to settle fully than simple DNS record updates because they affect where the authoritative DNS information is sourced from. Email-related changes can also appear delayed if remote mail servers continue using cached MX records.

Typical timeframes are:

* Small DNS record updates may be visible within minutes or a few hours

* Changes with a high previous TTL may take longer to appear

* Name server changes can take up to 24 to 48 hours

* Some individual networks may retain cached results longer than expected

Even when a change is technically correct, waiting is sometimes the only required step.

During DNS propagation, it is normal to see mixed results. For example, you may notice:

* Your website loads correctly on mobile data but not on your office connection

* Email starts arriving at the new provider for some senders before others

* One DNS checking tool shows the new record while another still shows the old one

* You can access the new website from one device but another device still shows the previous site

This happens because different devices and networks may query different DNS resolvers, each with its own cache state.

If you recently moved your website or email service, avoid making repeated DNS changes during propagation unless necessary. Frequent changes can make troubleshooting more difficult and extend confusion about which records should be active.

You can verify DNS changes by checking the current DNS records being returned from different locations or resolvers. This helps confirm whether the new records are live and whether propagation is still in progress.

Useful ways to check include:

* Viewing your DNS zone in the service where your domain’s DNS is hosted

* Using online DNS lookup tools to test your domain from multiple locations

* Querying public DNS resolvers directly

* Testing website or email behaviour after the change

When checking DNS, make sure you are looking at the correct record type. For example, website access commonly depends on A or CNAME records, while email routing usually depends on MX, SPF, DKIM and sometimes autodiscover-related records.

Before assuming a DNS issue, confirm the following:

* The DNS change was saved successfully in the correct DNS zone

* The domain is using the intended name servers

* The record type and value were entered correctly

* Enough time has passed for propagation to occur

* Your browser, device or local network is not showing a cached result

If all of these are correct, the behaviour may still be part of normal propagation.

Some delays are expected, but others may be caused by configuration issues. Common causes include:

* The domain is pointing to different name servers than expected

* The DNS record was updated in the wrong DNS host

* A previous TTL value was set very high

* Local DNS cache has not been cleared

* Browser cache is showing an older site result

* Email software is still connecting using older settings

* There is a typo in the DNS record value

If a DNS change appears not to be working after the normal propagation period, it is worth reviewing the full DNS configuration carefully.

If your DNS changes do not appear to be taking effect, work through the following checks.

1. Confirm which name servers your domain is using by checking the domain’s current delegation.

2. Verify that the DNS record was created or edited in the authoritative DNS zone, not in a different control panel.

3. Check that the record type is correct. For example, an A record and a CNAME record are not interchangeable in many situations.

4. Review the exact record value for typing mistakes, missing dots, or incorrect hostnames.

5. Test the domain using multiple DNS resolvers or online lookup tools to see whether the new record is visible elsewhere.

6. Clear your local DNS cache and browser cache, then test again.

7. Allow up to 48 hours for full propagation if the change was recent, especially for name server updates.

If your website or email still does not work after that period, the issue may be configuration-related rather than propagation-related.

Planning DNS changes carefully can reduce disruption. Recommended practices include:

* Make DNS changes during a low-traffic period where possible

* Review all record values before saving changes

* Avoid deleting old records until replacement settings have been confirmed where appropriate

* Lower TTL values in advance if you expect to make a planned migration and your DNS provider allows it

* Keep a record of the previous DNS settings before making changes

* Test website and email functionality after propagation begins

These steps can make it easier to roll back or troubleshoot if something does not work as expected.

How long does DNS propagation usually take?

Many DNS changes appear within a few hours, but full propagation can take up to 24 to 48 hours.

Can DNS propagation be sped up?

Not always. If resolvers have already cached the old record, you usually need to wait for that cache to expire. Lowering TTL before a planned change can help in some cases.

Why does my website work for some people but not others?

This usually means different DNS resolvers are returning different cached results during propagation.

Does clearing my cache fix DNS propagation?

Clearing your local DNS cache can help your own device see newer results, but it does not affect caches held by internet providers or public DNS resolvers.

Is DNS propagation the same for websites and email?

The underlying process is the same, but different record types are involved. Website changes often use A or CNAME records, while email commonly depends on MX and related DNS records.

* What is DNS?

* DNS Records Explained

* What Are Name Servers?

* How to Change Name Servers for a Domain

* How to Update DNS Records

* Troubleshooting Website DNS Issues

* Troubleshooting Email DNS Issues

Need More Help?

If you require further assistance, please contact Apexhost Support at support@apexhost.com.au.