On this page
Definition
DNS propagation is the period after a DNS change where different networks, devices and providers may still show different results because cached DNS information has not yet expired everywhere.
It is not one central update that happens instantly across the internet. It is a gradual refresh process affected by TTL values, recursive resolvers, registrars, DNS providers, internet service providers and local device caching.
Key Takeaways
- DNS propagation usually happens because old DNS answers are cached by resolvers, devices, browsers, networks or providers until their TTL expires.
- Propagation can affect websites, email, SSL certificates, third-party verification records and integrations, not just the visible website.
- Careful planning, lower TTL values before a planned change, testing and staged migration work can reduce disruption, but no provider can make propagation disappear entirely.
Quick Explanation
Why DNS Propagation Happens
How It Works
What Happens After a DNS Record Is Changed
DNS propagation is easier to understand when you separate the authoritative change from the cached copies that exist across the internet.
-
The DNS record is updated at the source
A record is changed in the domain’s DNS zone. This may be an A record for website hosting, an MX record for email, or a verification record for a third-party service. The authoritative DNS provider now has the new value.
-
Resolvers continue using cached answers until they expire
Internet service providers, public DNS resolvers, business networks and devices may have recently looked up the old record. If they cached it, they can keep serving the old answer until the TTL has passed.
-
Different users see the change at different times
One person may be directed to the new host within minutes, while another may still be sent to the old host for longer. The result depends on the resolver, cache age, TTL setting and sometimes local device or browser behaviour.
DNS Propagation Terms Worth Knowing
These terms come up often when diagnosing propagation delays or planning a website, email or hosting migration.
- TTL
- TTL stands for Time To Live. It tells DNS resolvers how long they can cache a DNS answer before asking again. A shorter TTL can help planned changes refresh sooner, but it does not clear every existing cache instantly.
- Authoritative Nameserver
- An authoritative nameserver is the source that holds the official DNS records for a domain. Other systems ask it for current information when their cached answer expires or when they do not already have a cached answer.
- Recursive Resolver
- A recursive resolver is the DNS service used by a device, business network, internet provider or public DNS platform to look up domain information on behalf of users.
Timing
How Long Does DNS Propagation Usually Take?
Propagation Is Not the Same as a Broken Website
Example DNS Change
This simplified example shows how a website’s A record might be changed during a hosting migration. The old server and new server values are examples only.
Before migration:
example.com. 3600 IN A 198.51.100.24
After migration:
example.com. 300 IN A 203.0.113.10A lower TTL before a planned migration can help new lookups refresh sooner, but existing cached records still need to expire.
DNS Record Changes vs Nameserver Changes
Both changes can cause propagation delays, but they do not work in exactly the same way. Knowing the difference helps with migration planning.
| Factor | Changing a DNS Record | Changing Nameservers |
|---|---|---|
| What changes | A specific record inside the current DNS zone is updated, such as an A, CNAME, MX or TXT record. | The domain is pointed to a different DNS provider, which changes where the official DNS zone is managed. |
| Typical use | Useful when moving a website, updating email routing, adding verification records or connecting a third-party platform. | Useful when transferring DNS management to a new provider, consolidating infrastructure or moving to a managed DNS setup. |
| Propagation risk | Usually limited to the changed record, although dependent services may still be affected. | Can affect all records if the new DNS zone is incomplete or different from the previous zone. |
Business Impact
How DNS Propagation Can Affect Websites and Email
Lowering TTL Before a Planned DNS Change
Advantages
- It can reduce the time many resolvers hold old DNS answers after the change.
- It gives technical teams more control during planned launches, hosting migrations or email platform changes.
- It can make rollback easier if a problem is found shortly after the cutover.
Limitations
- It only helps if lowered before the migration, not at the moment the change is made.
- It does not force every resolver, browser, device or network to clear existing cached records immediately.
- Very low TTL values can increase DNS query volume, so they are usually used temporarily rather than as a permanent setting.
Common DNS Propagation Mistakes
Most DNS problems are not caused by propagation alone. They often come from rushed changes, missing records or a lack of documentation.
Changing nameservers without copying all existing records
Do this instead
Before changing nameservers, document the complete DNS zone. Include website, email, SPF, DKIM, DMARC, subdomains, verification records and any third-party platform records.
Assuming the website is live everywhere after one successful test
Do this instead
Test from more than one network and check both the old and new environments. A successful test from your office does not mean every resolver has refreshed.
Changing email DNS records during business-critical sending periods
Do this instead
Plan email changes carefully, especially for businesses that rely on quotes, invoices, bookings or support requests. Test sending, receiving and authentication after the change.
Troubleshooting DNS Propagation Symptoms
These symptoms can appear during or after DNS changes. The right response depends on the record type, timing and business impact.
Some people see the new website and others see the old one
Likely cause
Different resolvers may be serving different cached DNS answers.
Solution
Keep the old hosting environment available during the transition where practical, check DNS from multiple resolvers, and avoid deleting the old site immediately after cutover.
Email stops arriving after a DNS change
Likely cause
MX records may be missing, incorrect or not copied into the new DNS zone.
Solution
Review the current MX records, confirm the intended email provider, and check SPF, DKIM and DMARC records. If email is business-critical, get technical help quickly.
The website shows a security or SSL warning
Likely cause
The domain may be resolving to a server where the SSL certificate is not installed or the certificate validation has not completed.
Solution
Confirm which server the domain resolves to, check the certificate on that server, and allow for DNS and certificate validation timing. Do not assume the SSL product itself is faulty.
DNS Change Planning Checklist
Use this checklist before changing DNS records for a website launch, hosting migration, email change or domain management update.
-
Document the existing DNS zone
Record A, CNAME, MX, TXT, SPF, DKIM, DMARC and verification records before making changes. This gives you a rollback reference if something is missed.
-
Prepare and test the destination environment
Confirm that the new website, hosting, email platform or third-party service is ready before the cutover. DNS should not be used as the first test of an unprepared system.
-
Plan the timing and communication
Schedule changes during a lower-risk period where possible. Let relevant staff know that temporary differences may occur while records update across networks.
Internal or Professional Support
Can You Handle DNS Propagation Yourself?
Our Approach
How We Manage DNS During Migrations
DNS Propagation FAQs
These answers cover common practical questions about DNS timing, website launches and email changes.
Can DNS propagation be made instant?
Why does my website work on mobile data but not office Wi-Fi?
Does DNS propagation affect SEO?
Need Help With a DNS Change or Migration?
If you are moving hosting, changing email platforms, launching a new website or unsure who controls your domain records, we can review the setup and help plan the change with less disruption.