When you update a domain's DNS records or change its nameservers, the change may not appear immediately everywhere. This delay is commonly called DNS propagation.
Understanding DNS propagation helps you know what to expect after connecting a domain to hosting, updating a website address, changing email settings, or moving DNS management to another provider.
What Is DNS Propagation?
DNS propagation describes the process through which DNS changes become visible to DNS resolvers around the internet.
When someone visits a domain, their device typically asks a DNS resolver for the information needed to reach that domain. Resolvers may temporarily store previous DNS answers in a cache. This allows future requests to be answered more efficiently.
After you update a DNS record, a resolver may continue using its cached information until the applicable cache period expires. As a result, different visitors or locations may see different results for a period of time.
How Long Does DNS Propagation Take?
There is no single propagation time that applies to every DNS change.
Some updates become visible relatively quickly, while others take longer. Timing can depend on:
-
The previous record's Time to Live (TTL).
-
Whether DNS resolvers have cached the old information.
-
Registrar processing when nameservers are changed.
-
The DNS provider's update process.
-
The type of record being changed.
-
Local network or device caching.
A DNS update may become visible within minutes in some locations, while other resolvers may continue returning older information for longer. Do not assume that a change has failed simply because it is not visible immediately.
What Is TTL?
TTL stands for Time to Live. It is a DNS setting that indicates how long a resolver may cache a DNS record before checking for an updated answer.
For example, a record with a TTL of 3,600 seconds has a one-hour cache period for resolvers that honor that value.
Reducing a record's TTL before a planned DNS change can help reduce the time some resolvers retain the previous answer. However, lowering the TTL does not instantly clear existing caches, and it does not control every resolver or network.
What Happens When You Change Nameservers?
Changing nameservers is different from editing an individual DNS record.
When you change a domain's authoritative nameservers, you are changing which DNS service is responsible for publishing the domain's records.
Before making this change:
-
Identify the DNS records currently in use.
-
Recreate the required records in the new DNS zone.
-
Confirm that website, email, verification, and other service records are present.
-
Update the nameserver settings at the domain registrar.
-
Allow time for the change to become visible.
If you forget to recreate important records, your website or email may stop working even after the nameserver change has completed.
How to Check Whether a DNS Change Has Taken Effect
You can check DNS results using public DNS lookup tools or command-line utilities such as nslookup and dig.
When checking a change:
-
Look up the exact hostname you changed.
-
Confirm the record type.
-
Compare the returned value with the destination supplied by your provider.
-
Check more than one public DNS resolver if results appear inconsistent.
-
Verify the authoritative nameservers when you have changed them.
Remember that a successful DNS lookup does not automatically confirm that the website or email service itself is working. The destination server must also be configured correctly.
What to Do If Your Website Still Does Not Load
If your website is unavailable after a DNS update:
-
Confirm that you changed the correct domain and hostname.
-
Verify the current authoritative nameservers.
-
Check the A, AAAA, or CNAME records relevant to your website.
-
Confirm that your hosting service is active and configured for the domain.
-
Check whether the browser is displaying a cached page or an error from an earlier connection.
-
Verify SSL configuration after the domain reaches the correct hosting destination.
For additional guidance, see How to Connect a Domain to Your WebDaddy Pro Hosting. Replace this placeholder with the permanent Knowledgebase URL after publishing that article.
Be Careful When Changing DNS
Avoid repeatedly changing records while waiting for an earlier update to become visible. Each additional change can make troubleshooting more difficult.
Keep a copy of the original DNS settings and make one planned change at a time whenever possible.
Need Help With a DNS Change?
If a domain is still resolving incorrectly after you have verified its settings, contact WebDaddy Pro Support.
Include the domain name, the record or nameserver change you made, when you made it, and the result you are seeing. Never include passwords or private account credentials.