What is DNS propagation?
DNS propagation is the period of time it takes for updated DNS information to spread across the internet after you change a DNS setting for your domain.
For example, if you update your domain’s A record to point to a new server,
some people may reach the new server quickly while others still reach the old one for a while.
That is because DNS answers are cached by many systems between the user and your domain.
DNS
The system that translates domain names like instantqr.io into IP addresses.
Propagation
The time it takes for updated DNS records to be seen by resolvers across different regions.
Result
Some users see the new record first, while others may still see the old one temporarily.
Why does DNS propagation happen?
DNS propagation happens because DNS is designed to be efficient. Instead of asking authoritative DNS servers for the same answer every single time, recursive resolvers and local devices cache results for a set amount of time.
That means when you change a DNS record, caches around the world do not all refresh at the exact same moment. Each resolver updates on its own timeline.
DNS changes are not “slow” because something is broken. They are delayed because older answers may still be stored in DNS caches until they expire and refresh.
How DNS caching works
Here is the basic flow:
You visit a domain
Your device, browser, router, ISP, or DNS resolver may ask for the domain’s DNS record.
The answer gets cached
The resolver saves that answer for a set period based on the record’s TTL.
You change the DNS record
The authoritative DNS zone is updated, but cached copies elsewhere may still hold the old answer.
Caches expire and refresh
As caches expire, resolvers request the updated record and users begin seeing the new result.
How long does DNS propagation take?
DNS propagation can take anywhere from a few minutes to as long as 24 to 48 hours. The exact time depends on the type of change, cache behavior, and TTL settings.
| Change Type | Typical Time | Notes |
|---|---|---|
| A / AAAA record | Minutes to 24 hours | Can be faster if TTL is low and resolvers refresh quickly. |
| CNAME record | Minutes to 24 hours | Often similar to A record timing. |
| MX record | Minutes to 48 hours | Email routing changes may take longer to appear globally. |
| TXT record | Minutes to 24 hours | Used for SPF, DKIM, verification, and other ownership checks. |
| Nameserver change | Up to 48 hours | Often the slowest type because delegation data must refresh widely. |
“Up to 48 hours” is a common rule of thumb, but many updates complete much sooner. The key point is that not every user or resolver updates at the same time.
What is TTL in DNS?
TTL stands for Time To Live. It tells resolvers how long they are allowed to cache a DNS record before checking again for an updated answer.
For example, a TTL of 300 means a resolver may keep that DNS answer for about 5 minutes.
A TTL of 3600 means about 1 hour.
Low TTL
Faster updates, but more frequent DNS lookups.
High TTL
More caching efficiency, but slower visible changes.
Best use
Lower TTL before migrations, cutovers, or important DNS changes.
What affects DNS propagation speed?
- TTL value: Lower TTLs generally allow faster refreshes.
- Resolver caching behavior: Some public and ISP resolvers refresh more quickly than others.
- Browser or device cache: Your local system may still hold old DNS results.
- Nameserver changes: These often take longer than simple record edits.
- Registrar and DNS host updates: Some control panel changes apply almost instantly, others take time.
How to check if DNS has propagated
The best way to verify propagation is to compare the DNS record you expect with the result being returned from different locations or resolvers.
Ways to check
- Use a DNS lookup tool to check
A,AAAA,CNAME,MX, orTXTrecords. - Test with public resolvers such as Google DNS or Cloudflare DNS.
- Clear your browser, OS, or local DNS cache if you suspect you are seeing an old result.
- Verify the record at the authoritative DNS provider if possible.
If your DNS panel shows the new value but your domain still behaves like the old one, the most common cause is caching, not a failed DNS update.
Common DNS propagation scenarios
Website moved to a new server
You update the A record to a new IP address. Some visitors reach the new server immediately.
Others still reach the old server until their cached answer expires.
Email provider changed
You update MX records. Some senders route to the new mail system first, while others may still
route using old cached data temporarily.
Domain verification for a service
You add a TXT record for Google, Microsoft, or another platform. The service may not detect it
immediately if its resolver still sees an older DNS state.
Nameservers changed
This can take longer than editing a normal record because the internet must update which authoritative nameservers are responsible for your domain.
How to reduce DNS propagation delays
- Lower TTL ahead of time. Do this before a planned migration or DNS cutover.
- Double-check the new record values. Small mistakes can look like propagation delays.
- Keep the old service active during transition. Useful for websites and mail routing.
- Use DNS lookup tools from multiple resolvers. This confirms whether the issue is global or local.
- Allow enough time. Not all resolvers refresh simultaneously.
Common DNS propagation myths
“DNS propagation means my DNS is broken”
Not necessarily. In many cases, the DNS change is correct, but cached results have not fully expired yet.
“Everyone sees the new DNS at once”
No. Different networks, devices, browsers, and recursive resolvers may refresh at different times.
“Propagation always takes 48 hours”
No. Many changes complete much sooner. Forty-eight hours is just a cautious upper range often used in support docs.
DNS propagation summary
DNS propagation is the delay between making a DNS change and having that change seen everywhere online. It happens because of DNS caching and TTL behavior across devices, browsers, ISPs, and public resolvers.
Most changes resolve faster than the maximum warning you often hear, but temporary inconsistency is normal. When troubleshooting, verify your records, compare results across resolvers, and allow time for caches to refresh.
FAQ
What is DNS propagation?
It is the time it takes for DNS changes to be reflected across cached DNS systems on the internet.
How long does DNS propagation take?
It may take a few minutes to up to 48 hours depending on TTL, resolver behavior, and the type of DNS change.
Why do some people see the change before others?
Because different resolvers and devices refresh cached DNS data at different times.
Does clearing my cache help?
It can help locally if your browser, operating system, or router is using an old cached DNS answer.
Are nameserver changes slower than record changes?
Often yes. Nameserver updates can take longer because delegation information needs to refresh broadly.