You changed your domain’s nameservers or DNS records, but your website still shows the old server. Perhaps it works on mobile data but not on Wi-Fi, or the website opens correctly for you while someone in another location still cannot access it.

In most cases, this does not mean your DNS change has failed.

The reason may simply be DNS propagation.

DNS changes can start appearing relatively quickly, but different DNS resolvers and networks may continue using previously cached information until it expires. This means a DNS change may appear to work in one location before it works everywhere else.

In this guide, we’ll explain what DNS propagation is, how long DNS propagation takes, how TTL affects DNS changes, how to check DNS propagation, and what to do when your DNS appears stuck.

---

What Is DNS Propagation?

DNS propagation is the commonly used term for the period after a DNS change during which different DNS resolvers across the internet begin returning the updated DNS information.

DNS stands for Domain Name System.

It allows domain names such as:

example.com

to be associated with information such as:

• Web server IP addresses
• Mail servers
• Nameservers
• Subdomains
• Domain verification records
• Other internet services

When you modify DNS information, the change is made at the authoritative source. However, DNS resolvers around the internet may already have the previous result stored in their cache.

Those cached records are not necessarily discarded immediately.

As their cached information expires and they request the record again, they begin receiving the updated DNS information.

This is why a DNS change can appear in some locations before others.

---

How Does DNS Propagation Work?

To understand propagation, it helps to understand what happens when someone visits a website.

Suppose a visitor enters:

www.example.com

into a browser.

The device needs to determine where that domain should go.

A simplified DNS lookup may involve:

1. The user’s device checking its local DNS cache.
2. The browser or operating system checking for previously cached information.
3. A recursive DNS resolver checking its cache.
4. The resolver querying the DNS hierarchy when necessary.
5. The authoritative nameserver returning the current DNS record.
6. The resolver caching that result according to its TTL.
7. The visitor connecting to the IP address returned by DNS.

If a resolver already has the previous DNS record cached, it may continue returning it until that cached record expires.

Therefore, after a DNS change:

Visitor A may receive the new DNS record while Visitor B still receives the old one.

This temporary difference is commonly referred to as DNS propagation.

---

How Long Does DNS Propagation Take?

There is no single propagation time that applies to every DNS change.

Many DNS changes can become visible relatively quickly, while nameserver changes may take up to approximately 24–48 hours to become consistently visible across different networks.

Several factors affect how quickly a change becomes visible:

• The previous DNS record’s TTL
• The type of DNS record changed
• Recursive DNS resolver caching
• Internet service provider caching
• Nameserver changes
• Local operating-system DNS cache
• Browser cache
• CDN or proxy caching
• The DNS provider being used
• Whether the previous DNS information had already been cached

This is why statements such as “DNS always takes 24 hours” are not technically accurate.

Some users may see your updated website within minutes, while others may temporarily continue reaching the previous destination.

---

What Is DNS TTL?

TTL stands for Time To Live.

TTL tells DNS resolvers approximately how long a DNS record may be cached before it should be queried again.

TTL is normally expressed in seconds.

For example:

300 = 5 minutes

3600 = 1 hour

14400 = 4 hours

86400 = 24 hours

Suppose an A record previously had:

TTL: 14400

A resolver that cached that record may continue using it for up to four hours before requesting fresh information.

If you change the A record immediately after the resolver has cached it, that resolver may continue returning the previous IP until its cache expires.

---

Does Lowering TTL Make DNS Propagation Faster?

It can help—but only when done before the DNS change.

For example, imagine your current A record has a TTL of 14,400 seconds.

You want to move your website to another server tomorrow.

If you reduce the TTL to:

300

well in advance of the migration and allow the previous TTL period to expire, subsequent DNS caches can begin using the shorter TTL.

When you later change the server IP, resolvers may refresh the record sooner.

However, changing the TTL to 300 at the same time as changing the IP address does not force resolvers that already cached the old record under the previous TTL to immediately refresh it.

Recommended Approach Before a Website Migration

If you are planning a server migration:

1. Lower the relevant DNS TTL well before the migration.
2. Allow enough time for the previous TTL to expire.
3. Migrate and test the website on the new server.
4. Change the required DNS record.
5. Monitor propagation.
6. Keep the old server available while DNS changes settle.
7. Restore a normal TTL after the migration is stable.

If you are moving WordPress between hosting providers, our complete WordPress migration guide explains the process in greater detail.

---

How to Check DNS Propagation

Instead of repeatedly refreshing your website, check the actual DNS result.

myglobalHOST provides a free DNS lookup tool that can help you check your domain’s DNS status.

Use the myglobalHOST DNS Checker to check your domain.

Enter your domain name and review the DNS information being returned.

This can help determine whether a problem is related to DNS rather than your website itself.

---

Which DNS Records Can Be Affected by Propagation?

Propagation is not limited to nameservers.

DNS caching can affect several record types.

A Record

An A record connects a hostname to an IPv4 address.

Example:

example.com → 192.0.2.10

If you move your website to another server and change the A record, some resolvers may temporarily return the previous server IP.

---

AAAA Record

An AAAA record performs a similar function for IPv6.

If both A and AAAA records exist, make sure both records are intentionally configured.

An incorrect AAAA record can sometimes cause confusing situations where a website appears to work over IPv4 but fails for visitors whose devices or networks prefer IPv6.

---

CNAME Record

A CNAME creates an alias from one hostname to another.

For example:

www.example.com → example.com

Changes to CNAME records can also be cached.

---

MX Record

MX records determine which mail servers should receive email for a domain.

Changing MX records can therefore affect email delivery while DNS caches are updating.

If you are migrating email services, keep the old email environment available long enough to avoid losing messages that may still be routed according to previously cached DNS information.

---

TXT Records

TXT records are commonly used for:

• SPF
• DKIM
• DMARC
• Domain verification
• Google services
• Microsoft services
• Search engine verification
• Third-party applications

When adding a TXT record for domain verification, the service checking your domain may not immediately see a newly created record if cached DNS information is involved.

---

NS Records / Nameservers

Nameserver changes determine which DNS servers are authoritative for your domain.

For example, when connecting a domain to myglobalHOST, you may change its nameservers to the ones assigned to your hosting service.

If you’re doing this now, follow our complete guide on how to point a domain to myglobalHOST.

You can also learn where to find your myglobalHOST nameservers.

---

Why Is My Website Showing the Old Server After Changing DNS?

This is one of the most common symptoms during DNS propagation.

Suppose your website was hosted on:

Old Server → 192.0.2.10

and you change its DNS to:

New Server → 192.0.2.20

A resolver with the previous record cached may still send you to:

192.0.2.10

while another resolver already sends visitors to:

192.0.2.20

Consequently, two visitors can enter exactly the same domain name and temporarily reach different servers.

This is why the old hosting account should generally not be cancelled immediately after changing DNS.

---

Why Does My Website Work on Mobile Data but Not Wi-Fi?

This is a classic DNS propagation symptom.

Your Wi-Fi connection and mobile-data connection may use different DNS resolvers.

For example:

Wi-Fi DNS resolver: still has the previous server IP cached.

Mobile network DNS resolver: has already retrieved the new IP.

Your website may therefore work correctly over mobile data while the same device receives the old website—or an error—over Wi-Fi.

The reverse can also happen.

Before changing DNS again, check the domain using the myglobalHOST DNS Checker.

Repeatedly changing DNS records during propagation can make troubleshooting more difficult.

---

Why Can Someone Else See My Website but I Cannot?

Your computer, router, ISP or DNS resolver may still be using cached DNS information.

The other visitor may be using a resolver that has already refreshed the record.

Try checking the domain from:

• Another internet connection
• Mobile data
• Another device
• A public DNS resolver
• A DNS checking service

If external DNS checks return the correct server but your own connection does not, the problem may be local caching rather than incorrect authoritative DNS.

---

How to Clear DNS Cache

If authoritative DNS is correct but your device still receives an outdated result, clearing the local DNS cache may help.

Clear DNS Cache on Windows

Open Command Prompt as Administrator and run:

ipconfig /flushdns

Windows should confirm that the DNS Resolver Cache was successfully flushed.

---

Clear DNS Cache on macOS

The command can vary between macOS versions, but modern versions commonly use:

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

Enter your Mac password if prompted.

The command may complete without displaying a confirmation message.

---

Restart Your Router

Home and office routers may also cache DNS information.

Restarting the router can sometimes help clear locally cached information.

However, restarting your router cannot force an external ISP or recursive DNS resolver to discard a still-valid cached record.

---

Restart the Browser

Browsers can maintain their own caches.

Close and reopen the browser or test the website using a private/incognito window.

Remember, however, that browser cache and DNS cache are not the same thing.

---

Browser Cache vs DNS Cache: What’s the Difference?

These two problems are frequently confused.

DNS cache stores information about where a domain resolves.

Browser cache stores website resources such as:

• HTML
• CSS
• JavaScript
• Images
• Fonts
• Other static content

If DNS points to the correct server but you still see an old page, the issue may be browser, application, server or CDN caching rather than DNS propagation.

---

DNS Propagation vs Website Cache

Another important distinction is between DNS and website caching.

Suppose your DNS checker already shows the correct IP address, but the website displays an older design.

That does not automatically mean DNS is still propagating.

The old content might be coming from:

• Browser cache
• WordPress cache
• LiteSpeed Cache
• CDN cache
• Cloudflare cache
• Server-side cache

If you use WordPress with LiteSpeed, our LiteSpeed Cache optimization guide can help you understand and configure website caching correctly.

---

DNS Propagation vs Cloudflare Cache

Cloudflare can add another caching layer between visitors and your origin hosting server.

If your domain uses Cloudflare’s proxy, a DNS lookup may return Cloudflare IP addresses rather than your hosting server’s direct IP.

This can be perfectly normal.

In that configuration:

Visitor → Cloudflare → Origin Hosting Server

Therefore, seeing a Cloudflare IP does not necessarily mean your domain is pointed incorrectly.

You need to distinguish between:

1. Authoritative DNS configuration
2. Cloudflare proxy status
3. Origin server configuration
4. Cloudflare cache
5. Website/application cache

Changing all of these at once can make diagnosis unnecessarily difficult.

If you use Cloudflare, our guide on Cloudflare and SEO explains several important Cloudflare configuration considerations.

---

How to Know Which DNS Provider Is Authoritative

Your domain’s authoritative nameservers determine where its public DNS records are controlled.

For example, if your domain’s nameservers point to Cloudflare, changing an A record only inside cPanel will generally not change the public DNS record served by Cloudflare.

Likewise, if your domain uses the DNS infrastructure associated with your myglobalHOST hosting account, DNS changes should be made in the appropriate hosting DNS zone.

You can learn how to add, edit and manage DNS records in cPanel if your DNS is managed there.

---

How to Tell Whether DNS Propagation Is Complete

Do not judge propagation only by whether the website opens on your computer.

Instead, verify several things.

1. Check the authoritative nameservers

Make sure the domain uses the nameservers you intended to configure.

2. Check the relevant DNS record

For a website migration, check whether the domain’s A record returns the intended server IP.

3. Check www

Check both:

example.com

and:

www.example.com

They may use different DNS records.

4. Check IPv6 if applicable

If an AAAA record exists, make sure it is correct.

5. Check email DNS records

If email services were moved, verify MX and associated email-authentication records.

6. Test from different networks

Compare Wi-Fi and mobile data if necessary.

7. Confirm the website is configured on the destination server

Correct DNS only directs visitors to a server.

The destination hosting account must also be configured to serve the requested domain.

If you’re using cPanel and adding an additional domain, see how to add a new domain in cPanel.

---

DNS Is Propagated but My Website Still Doesn’t Work — What Now?

Once DNS definitely returns the correct server, continuing to wait for propagation may not solve the problem.

Check the following.

1. Is the Domain Added to Your Hosting Account?

The server must know which hosting account should serve the domain.

For additional domains, verify that the domain exists in cPanel.

---

2. Are the Website Files in the Correct Document Root?

Make sure the site’s files have been uploaded to the directory assigned to the domain.

If WordPress was installed through cPanel, follow our WordPress installation guide using Softaculous to verify the setup.

---

3. Is SSL Active?

After DNS points correctly to the server, SSL can be issued and configured.

If HTTPS produces a certificate warning, follow our guide to install and activate SSL in cPanel.

---

4. Is the Website Redirecting Somewhere Else?

An incorrect .htaccess rule, WordPress URL, application configuration or CDN setting can redirect visitors away from the intended domain.

This is no longer purely a DNS propagation problem.

---

5. Is Cloudflare Still Pointing to the Old Server?

If Cloudflare manages your DNS, verify the origin IP configured in Cloudflare DNS.

Updating DNS inside cPanel will not replace records being served by another authoritative DNS provider.

---

Common DNS Propagation Mistakes to Avoid

Mistake 1: Changing DNS Repeatedly

You change the nameservers, wait 20 minutes, assume they failed, change them again, and then change them back.

This makes troubleshooting unnecessarily complicated.

Make the correct change, verify it, and allow caches time to refresh.

---

Mistake 2: Cancelling the Old Hosting Immediately

During a migration, some visitors may temporarily continue reaching the previous server.

If the old hosting is cancelled too soon, those visitors may see an error.

Keep the previous hosting active until the migration and DNS transition have been verified.

---

Mistake 3: Editing DNS at the Wrong Provider

Always determine which nameservers are authoritative.

If your authoritative DNS is managed externally, editing records somewhere else will not necessarily affect public DNS.

---

Mistake 4: Forgetting the www Record

example.com and www.example.com can have different DNS configurations.

Always test both.

---

Mistake 5: Forgetting Email Records

A website may work perfectly while email stops working because MX, SPF, DKIM or other necessary records were not preserved during a nameserver change.

---

Mistake 6: Assuming Every Website Problem Is DNS

Once DNS returns the correct destination consistently, look elsewhere.

Possible causes include:

• Incorrect document root
• Missing website files
• PHP errors
• Database problems
• SSL problems
• .htaccess rules
• WordPress errors
• Firewall/security rules
• CDN configuration
• Application configuration

DNS is only one part of the request path.

---

DNS Propagation During Website Migration

DNS planning is especially important when moving a live website.

A safer migration process is:

Step 1: Copy the website to the new hosting server.

Step 2: Test the website on the new server before changing public DNS whenever possible.

Step 3: Reduce the relevant TTL ahead of the migration if appropriate.

Step 4: Keep the old website online.

Step 5: Change the nameservers or required DNS records.

Step 6: Monitor DNS.

Step 7: Keep both servers available while cached DNS information expires.

Step 8: Verify website functionality, SSL, email and forms on the new server.

Step 9: Cancel the old hosting only after you are satisfied that the migration is complete.

For WordPress websites, read our zero-downtime WordPress migration guide before starting the move.

---

How to Point a Domain to myglobalHOST

If you’re reading about DNS propagation because you recently purchased a myglobalHOST hosting plan, make sure the domain was pointed correctly in the first place.

Our dedicated domain pointing guide for myglobalHOST explains:

• How to find your nameservers
• How to change nameservers
• Nameservers vs individual DNS records
• A, CNAME, MX and TXT records
• Cloudflare considerations
• SSL after DNS changes
• Troubleshooting a domain that does not load

If you only need your hosting nameserver information, see where to find your myglobalHOST nameservers.

---

Frequently Asked Questions About DNS Propagation

What does DNS propagation mean?

DNS propagation is the commonly used term for the period after a DNS change during which recursive DNS resolvers and other caches begin returning the updated DNS information instead of previously cached records.

How long does DNS propagation take?

There is no universal propagation time. Many DNS changes become visible relatively quickly, while nameserver changes can take up to approximately 24–48 hours to become consistently visible across different networks.

Can DNS propagation take less than an hour?

Yes. Depending on the DNS record, its previous TTL and resolver caching, a change may become visible to many users within minutes or an hour. This does not guarantee that every resolver worldwide has refreshed the information.

Why does my website work on mobile data but not Wi-Fi?

Your mobile provider and Wi-Fi connection may use different DNS resolvers. One may already have the updated DNS information while the other still has the previous record cached.

Can I speed up DNS propagation?

You cannot force every DNS resolver to immediately discard a valid cached record. For planned changes, lowering the relevant TTL sufficiently in advance can reduce how long future cached records remain valid.

Does clearing my browser cache speed up DNS propagation?

No. Browser content cache and DNS cache are different. Clearing browser cache can resolve stale website-content issues, but it does not force DNS resolvers across the internet to update their records.

Does restarting my router speed up DNS propagation?

Restarting a router may clear some local caching, depending on the equipment, but it cannot force your ISP or external recursive DNS resolver to refresh a record before its cached information expires.

Why is DNS correct but my website still shows the old content?

The old content may be coming from browser cache, WordPress cache, LiteSpeed Cache, a CDN or Cloudflare. Verify the server IP first before assuming that DNS is responsible.

Should I cancel my old hosting after changing DNS?

Not immediately. During a hosting migration, keep the old hosting available until DNS changes have settled and you have confirmed that the website and any required services work correctly on the new server.

How do I check my DNS propagation?

Use the free myglobalHOST DNS Checker and verify that your domain returns the DNS information you expect.

---

Final Thoughts

DNS propagation is usually not an error. It is a consequence of the distributed and cached nature of the Domain Name System.

After changing nameservers or DNS records, different networks can temporarily return different results because previously cached records have not yet expired.

The key is to avoid making repeated changes simply because the new DNS information is not immediately visible everywhere.

Instead:

• Confirm that you made the correct DNS change.
• Verify which nameservers are authoritative.
• Check the relevant DNS records.
• Use a DNS checker instead of relying only on your browser.
• Allow existing DNS caches to expire.
• Keep the old server running during migrations.
• Troubleshoot the hosting/application only after confirming DNS is correct.

If you are connecting a new domain to your hosting account, continue with our complete guide to pointing a domain to myglobalHOST.

You can then use the myglobalHOST DNS Checker to verify your domain’s DNS status.