What Is DNS Propagation and How Long Does It Take?

DNS Propagation is the process that happens after you change a domain’s DNS records and those changes begin spreading across DNS servers and resolvers around the world.

If you have ever updated an A record, changed nameservers, connected a domain to a new hosting provider, or modified an MX record, you may have noticed that the change did not appear everywhere immediately. One person might see the new website, while another still sees the old one.

In this guide, we explain how it works, how long it usually takes, what affects propagation time, and what you can do if your DNS changes are taking longer than expected.

What Is DNS Propagation?

DNS propagation describes the period during which DNS changes become visible across different networks, DNS resolvers, and internet service providers.

The Domain Name System, or DNS, works like the internet’s address book. It translates domain names such as example.com into IP addresses that computers can understand.

When you update a DNS record, the new information does not instantly replace every cached copy of the old record.

Instead, DNS resolvers continue using previously stored information until that cached data expires.

Once the cached record expires, the resolver requests fresh DNS information and receives the updated value.

This is why DNS changes may appear at different times for different users.

How Does DNS Propagation Work?

To understand DNS propagation, it helps to understand how DNS caching works.

When you visit a website, your device usually does not contact the domain’s authoritative DNS server directly every time.

Instead, it sends a DNS query to a recursive resolver. That resolver may belong to your internet service provider or a public DNS service.

If the resolver already has the answer stored in its cache, it returns that information immediately.

For example, imagine that your domain currently points to:

192.0.2.10

You then update the A record so that the domain points to:

192.0.2.25

The authoritative DNS server may show the new IP address almost immediately.

However, a DNS resolver that cached the old address may continue returning 192.0.2.10 until its cached record expires.

Another resolver may refresh sooner and start returning 192.0.2.25.

During this period, different users can receive different DNS results.

That is what people usually mean when they say a DNS change is “still propagating.”

How Long Does DNS Propagation Take?

DNS propagation can take anywhere from a few minutes to several hours.

In some cases, changes may take up to 24 or 48 hours to appear everywhere.

However, there is no single fixed propagation time.

The actual delay depends on several factors, especially the TTL value of the DNS record and how different DNS resolvers handle cached information.

Some users may see the new DNS record within minutes, while others continue seeing the old value for several hours.

That does not necessarily mean something is wrong.

What Is TTL and Why Does It Matter?

TTL stands for Time to Live, and it tells DNS resolvers how long they should keep a DNS record in cache before requesting a fresh copy.

TTL values are usually measured in seconds.

For example:

• 300 seconds = 5 minutes
• 1800 seconds = 30 minutes
• 3600 seconds = 1 hour
• 86400 seconds = 24 hours

Suppose your domain has an A record with a TTL of 3600 seconds.

A resolver that just cached the record may continue using that value for up to one hour before checking for an update.

This is one of the main reasons DNS changes do not appear instantly.

A shorter TTL can help DNS updates become visible faster, while a longer TTL reduces the number of DNS queries sent to authoritative servers.

What Affects DNS Propagation Time?

Several factors can influence how quickly DNS changes become visible.

1. TTL Settings

TTL is one of the most important factors.

If the previous DNS record had a long TTL, resolvers may continue using the old value until the cached entry expires.

Lowering the TTL before a planned DNS change can help reduce this delay.

2. DNS Resolver Cache

Different DNS resolvers refresh their caches at different times.

One resolver may already have updated information, while another still holds the older DNS record.

This explains why two users in different locations can see different results.

3. Local Device Cache

Your computer, browser, router, or operating system may also cache DNS information.

Even if public DNS resolvers already return the new record, your own device may temporarily continue using the previous value.

4. ISP DNS Cache

Internet service providers often operate their own DNS resolvers.

These resolvers may keep cached DNS records until the TTL expires.

As a result, users connected through different ISPs may see DNS updates at different times.

5. Nameserver Changes

Changing individual DNS records and changing authoritative nameservers are not exactly the same process.

Nameserver changes can sometimes take longer because parent DNS servers and recursive resolvers may also cache delegation information.

Which DNS Changes Need Time to Propagate?

Almost any DNS record change can involve caching.

Common examples include:

• A Records

A records connect a domain or hostname to an IPv4 address.

If you move a website to a new server, you may need to update the A record.

• AAAA Records

AAAA records work like A records but point to IPv6 addresses.

• CNAME Records

CNAME records make one hostname an alias of another hostname.

Changes to CNAME records may also remain cached until the TTL expires.

• MX Records

MX records tell email systems which mail servers handle email for a domain.

When you change email providers, updated MX records may take time to appear across DNS resolvers.

• TXT Records

TXT records are often used for domain verification, SPF, DKIM, and other security or configuration purposes.

Services that check TXT records may continue seeing old values until DNS caches refresh.

• Nameserver Records

Nameserver changes tell the DNS system which authoritative DNS servers manage your domain.

These changes can take longer than simple record updates.

How Can You Check DNS Propagation?

The easiest way to check DNS propagation is to perform DNS lookups from different resolvers or locations.

You can look up records such as:

• A
• AAAA
• CNAME
• MX
• TXT
• NS

If different DNS servers return different values, the change may still be working its way through cached DNS data.

A DNS lookup tool can also help you confirm whether the authoritative DNS server already contains the correct record.

This distinction matters.

If the authoritative server still returns the wrong value, the problem is probably not propagation. The DNS configuration itself may be incorrect.

Can You Speed Up DNS Propagation?

You cannot force every DNS resolver on the internet to update immediately.

However, you can prepare for DNS changes in a way that reduces delays.

Lower the TTL Before Making Changes

If you know that you will move a website or change an important DNS record, lower the TTL in advance.

For example, you might reduce a TTL from several hours to five minutes before the planned change.

After the change is complete and everything works correctly, you can increase the TTL again.

Keep in mind that lowering the TTL only helps after existing cached records with the old TTL expire.

Clear Your Local DNS Cache

If the updated record is already available publicly but your computer still shows the old result, clearing your local DNS cache may help.

Restarting the browser or router may also clear some cached DNS information.

Try a Different DNS Resolver

You can compare results from different DNS resolvers.

If one resolver shows the new DNS record and another shows the old one, caching is likely the reason.

Conclusion

DNS Propagation is a normal part of updating DNS records. Changes may appear within minutes for some users while taking several hours for others because DNS resolvers, ISPs, and devices cache DNS information.

TTL values play a major role in how long those cached records remain active.

When making an important DNS change, plan ahead, check your TTL, verify the authoritative DNS records, and use DNS lookup tools to monitor the update.