You point your domain to a new host, change a DNS record, or move your website to a different server, and then you wait. Your friend in another city sees the new site, but your own browser still shows the old one, or nothing at all. Nothing is broken, and you probably did nothing wrong. You are watching domain propagation in progress. This is one of the most confusing parts of managing a domain for beginners, because there is no progress bar, no finish button, and no single moment when the change applies everywhere at once. This guide explains what propagation really is, how long it usually takes, why different visitors see different results, how to check your records around the world, and what you should avoid doing while you wait.
What Is Domain Propagation?
Domain propagation is the time it takes for a DNS change to spread across the internet. DNS, short for Domain Name System, is the system that turns a human readable domain name such as example.com into an IP address, which is the numeric address of the server that hosts the website. When someone types your domain into a browser, their computer asks a DNS resolver, usually run by their internet provider or a public DNS service, where that domain points. The resolver looks up the answer and returns the IP address, and the browser then loads the site from that server.
Here is the catch. DNS resolvers do not look up the answer fresh every single time. They store, or cache, the answer for a period of time so that future visits load faster and DNS servers are not overloaded. When you change a DNS record, resolvers around the world still hold the old cached answer until that cache expires. Propagation is simply those old answers expiring and being replaced by the new answer, resolver by resolver. There is no central switch that updates the whole internet at once.
What Is TTL and Why Does It Control Propagation Speed?
TTL stands for Time To Live, and it is a setting attached to each DNS record. It tells resolvers how long, in seconds, they are allowed to cache that record before they must check again for a fresh answer. A TTL of 3600 means one hour, a TTL of 14400 means four hours, and a TTL of 86400 means a full day. In general, a lower TTL means faster propagation, because caches expire sooner, while a higher TTL means slower propagation but less strain on DNS servers and slightly faster repeat visits.
Most hosting providers and domain registrars set a default TTL between one hour and one day. You can often lower it before a planned move. If you know you will change hosts in a few days, lower the TTL to 300 seconds, which is five minutes, at least 24 to 48 hours in advance. That gives old caches time to expire, so resolvers pick up the change within minutes. After the move is stable, raise the TTL back to a normal value. If you are new to domains, our guide to the difference between a domain and hosting explains how domains, DNS, and hosting fit together.
How Long Does Domain Propagation Usually Take?
For most common changes, propagation takes anywhere from a few minutes to 48 hours, and in practice most visitors see the new result within a few hours. Small changes, such as updating a record with a low TTL, can spread in under 30 minutes in many locations. Nameserver changes, which happen when you point a domain to a new host, tend to take longer, because nameserver records themselves are often cached for a longer period by internet providers. Changes at the domain registrar level can also take extra time to reach the global DNS root servers before resolvers even start picking them up.
The often quoted 48 hour figure is a safe upper limit, not a promise that you will wait two full days. Today, most major providers refresh much faster, and many changes are visible worldwide within one to six hours. Still, a few visitors on slow updating networks may see the old site for up to 48 hours. If your site still shows the old result after 48 hours, that usually points to a different problem, such as a wrong record or a local cache on your own device, rather than normal delay. If you are moving a domain between registrars, our guide on how to transfer a domain between registrars covers the extra steps and waiting periods involved in that kind of move.
Why Do Different Visitors See Different Results?
Different visitors see different results because they use different DNS resolvers, and each resolver has its own cache with its own expiry time. Your visitor in the United States may use a fast public resolver that refreshed five minutes ago, while your visitor in another country may use a local provider that still holds yesterday cached answer. Your own computer adds another layer, because operating systems and browsers cache DNS answers too, so you may keep seeing the old site even after most of the world has moved on.
Location is only part of the story. The type of device matters as well. A phone on mobile data uses a different resolver than the same phone on home WiFi, so switching networks can suddenly show the new site. A visitor who visited your site yesterday will have a cached answer, while a first time visitor will fetch the fresh answer straight away. This is also why testing with a single browser on a single connection gives a misleading picture. To judge propagation properly, you need to check from several locations and networks, not just your own screen. If you are setting up a new part of your site during this period, our guide on how to create a subdomain in cPanel and install WordPress shows a setup that also depends on DNS records resolving correctly.
How Can You Check Propagation Around the World?
The best way to check propagation is to use a DNS checker tool. These free online tools query DNS servers in many cities and countries at once and show you, in one table, which IP address each location returns for your domain. If most locations show your new IP address and only a few still show the old one, propagation is nearly complete and you just need to wait a little longer. If locations disagree wildly, or if some show no answer at all, you may have a record problem worth investigating.
When you check, compare the exact record you changed. For a website move, check the A record, which points the domain to a server IP address. For a nameserver change, check the NS records. For email moves, check the MX records. Make sure you are comparing against the correct new value from your hosting provider, because a checker can only tell you what the world sees, not whether that value is right. You can also flush the DNS cache on your own computer, or test in a private browser window, or test on mobile data, to rule out your own local cache before concluding that propagation is still pending. For authoritative background on how the global DNS system works, the ICANN website is a reliable starting point. If you are still choosing where to host the site you are pointing the domain to, our web hosting guide compares the main options in plain language.
- Open a DNS checker tool and enter your domain name.
- Select the record type you changed, such as A, NS, or MX.
- Compare the results across locations with the new value from your host.
- Repeat the check after a few hours instead of every few minutes.
What Should You NOT Do While Waiting for Propagation?
The biggest mistake beginners make during propagation is impatience. They change a record, wait ten minutes, see no change, and then change it again, or switch nameservers back and forth, or add duplicate records hoping one of them will work. Every new change restarts the clock, because resolvers now have to expire the previous answer and pick up the newest one. Repeated edits turn a short wait into a long and confusing one, and they make troubleshooting much harder, because nobody, including you, can tell which change the world is currently seeing.
Instead, follow a calm routine. Make the change once, double check that you typed the IP address or nameserver correctly, note the new values, and then wait. Check a DNS checker tool after an hour or two, and again later, rather than refreshing constantly. Do not reinstall WordPress, do not delete the site from the old host too early, and do not cancel the old hosting plan until propagation is complete, because visitors still reaching the old server need that site to stay up.
What Should You Do If Propagation Takes Too Long?
If 48 hours have passed and your domain still points to the wrong place, work through a short checklist before assuming the worst. First, confirm the record at your registrar or DNS provider, and check for typos in the IP address or nameserver names, since a single wrong character sends visitors to the wrong server. Second, check whether you edited the right DNS zone, because domains can have DNS managed at the registrar, at the host, or at a third party service, and editing the inactive zone changes nothing. Third, clear your local DNS cache and test on a different network, to rule out your own device. Fourth, ask a friend in another city, or use a DNS checker, to see whether the problem is global or only on your connection.
If the problem is global, contact your hosting provider support with the exact record, the old value, the new value, and a screenshot from a DNS checker. That information lets support spot a typo, a conflicting record, or a registrar delay quickly. In most cases the fix is simple once the wrong value is identified. Remember that propagation is a normal, expected part of changing DNS, not a sign that domains are unreliable. Once you understand TTL and caching, you can plan moves in advance, lower TTL ahead of time, and avoid the stress of watching a half updated internet.
Frequently Asked Questions
How long does domain propagation take?
Most changes propagate within a few hours, and the safe upper limit is 48 hours. The exact time depends on the TTL value, the type of record changed, and how quickly each internet provider refreshes its DNS cache.
Why can I see the new site but my friend cannot?
You and your friend use different DNS resolvers with different caches. Your resolver may have already picked up the new record, while your friend resolver still holds the old cached answer. This difference disappears on its own once the old cache expires.
Can I speed up domain propagation?
You cannot force every resolver in the world to update instantly, but you can plan ahead by lowering the TTL to 300 seconds at least a day before a planned change. After the change, you simply wait for caches to expire, and you should avoid making further edits in the meantime.
Should I keep changing DNS records until the new site appears?
No. Repeated changes restart propagation and make the situation worse. Make the change once, verify that the values are correct, and then wait. If nothing has changed after 48 hours, check for typos or contact your hosting support instead of editing again.
Last updated: October 2026.
