This guide explains what DNS propagation is, why it takes time, how to check its progress, and how to identify propagation-related issues.

What DNS propagation means

DNS propagation is the time it takes for DNS changes to become visible across the internet.

When you update DNS records for your domain, the change does not appear everywhere at the same time. Different DNS resolvers, internet providers, browsers, and networks may continue using cached DNS information until that cache expires.

This means some visitors may reach the new destination while others may still reach the previous one for a short period.

Why DNS propagation matters for Pressidium EDGE

Pressidium EDGE is activated through DNS. Your domain is pointed to EDGE so traffic can pass through the edge layer before reaching your origin infrastructure. EDGE then handles caching, security, routing, and delivery before forwarding uncached valid requests to your origin when needed.

Because DNS controls where your domain sends traffic, propagation affects when your site starts routing through EDGE.

During propagation, you may see mixed results:

  • Your domain may work correctly from one network but not another.
  • DNS checking tools may show different results by location.
  • Some users may reach EDGE while others still reach the previous DNS target.
  • SSL or domain verification may remain pending until the expected DNS records are visible.

Why DNS propagation takes time

DNS propagation takes time because DNS records are cached.

The most important factor is TTL, or Time to Live. TTL tells DNS resolvers how long they can cache a DNS record before checking for an updated value.

For example:

  • A low TTL, such as 300 seconds, allows changes to appear faster.
  • A higher TTL, such as several hours, can delay updates.
  • Some networks or internet providers may keep cached records longer than expected.

Propagation is not controlled by Pressidium EDGE alone. It depends on your DNS provider, the record TTL, recursive DNS resolvers, and local network caching.

Common situations during propagation

You may notice DNS propagation when:

  • Adding a domain to EDGE
  • Updating DNS records to point traffic to EDGE
  • Changing an A, AAAA, CNAME, TXT, or other DNS record used for setup or verification
  • Switching from a previous CDN, proxy, or firewall service
  • Updating records at your DNS provider
  • Waiting for SSL validation or domain verification

How long DNS propagation takes

Many DNS changes appear within minutes, especially when TTL values are low.

In some cases, propagation can take several hours. DNS propagation can also take up to 48 hours or more, especially after nameserver changes, high TTL values, or resolver caching outside your control.

Important: If you recently changed your domain’s nameservers, propagation may take longer than a simple record update.

How to check DNS propagation

Use these checks to confirm whether your DNS changes are visible.

1. Check the record in your DNS provider

Go to your DNS provider and confirm that the record exists.

Verify:

  • The record type is correct.
  • The hostname is correct.
  • The value matches the value shown in the Pressidium Dashboard.
  • There are no duplicate or conflicting records.
  • The record is saved in the active DNS zone for the domain.

2. Check the domain from multiple locations

Use a DNS propagation checker to test the record from different regions:

These tools show DNS results from different locations and resolvers. If some locations show the new value and others show the old value, propagation is still in progress.

3. Check locally

You can also check DNS from your own machine.

For example:

dig example.com

To check a specific record type:

dig example.com A
dig www.example.com CNAME
dig example.com TXT

Replace example.com with your own domain.

4. Check using a public resolver

You can compare results from public DNS resolvers.

dig example.com @1.1.1.1
dig example.com @8.8.8.8

If the results differ, some resolvers have updated while others are still using cached data.

5. Check with nslookup

You can also use nslookup, which is available on Windows, macOS, and Linux.

nslookup example.com
nslookup example.com 8.8.8.8

The second command checks the result from Google Public DNS.

6. Check with host

On macOS and Linux, you can also use host.

host example.com
host -t CNAME www.example.com
host -t TXT example.com

How to know propagation is complete

DNS propagation is effectively complete when the public DNS resolvers you check consistently return the new expected record value.

If the expected value appears consistently across multiple resolvers but domain verification, traffic routing, SSL, or the website still does not work, the issue is probably no longer DNS propagation.

Use the relevant setup or troubleshooting guide to continue diagnosing the problem.

Check the domain status in the EDGE Dashboard

You can also compare public DNS results with the status shown in Pressidium EDGE.

  1. Open the relevant website.
  2. Go to the domain or DNS details.
  3. Review the current verification or routing status.
  4. Compare the expected DNS value shown by EDGE with the result returned by public DNS lookups.

If public DNS still returns an older value, propagation is still in progress.

If public DNS returns the correct EDGE value but the Dashboard remains pending, follow the relevant domain verification or DNS troubleshooting guide.

Troubleshooting DNS propagation issues

Symptom: The domain still points to the old destination

Likely causes:

  • The previous DNS record is still cached.
  • The DNS change was made in the wrong DNS zone.
  • The old record still exists.
  • The domain is using different nameservers than expected.

Resolution steps:

  1. Confirm which nameservers your domain uses.
  2. Log in to the DNS provider that controls those nameservers.
  3. Check that the correct DNS record exists.
  4. Remove duplicate records that point to the old destination.
  5. Wait for the previous TTL to expire.
  6. Recheck the record from multiple DNS resolvers.

Verification:

Confirm that the DNS result returns the value shown in the Pressidium Dashboard.

Symptom: Domain verification is still pending

First, check whether the verification DNS record is publicly visible.

If public DNS lookups still return the old value or no record, allow more time for propagation.

If the expected verification record is already visible publicly but verification remains pending, follow Verify your domain for Pressidium EDGE for configuration checks and troubleshooting.

Symptom: The site works on one network but not another

Likely causes:

  • Different networks are using different cached DNS results.
  • A local router or device is caching DNS.
  • Browser DNS cache is still using the previous value.

Resolution steps:

  1. Test the site from another network, such as mobile data.
  2. Clear your browser DNS cache.
  3. Restart your browser.
  4. Flush your operating system DNS cache.
  5. Restart your router if the issue is limited to your local network.

On macOS, you can flush local DNS cache with:

sudo dscacheutil -flushcache;
sudo killall -HUP mDNSResponder

On Windows, use:

ipconfig /flushdns

Verification:

The domain should resolve to the same expected value across networks after caches expire.

Symptom: DNS has propagated, but the site does not load

If public DNS lookups consistently return the expected EDGE routing value, the DNS change has propagated.

At that point, the issue may involve the origin, SSL, routing configuration, or another part of the site setup rather than DNS propagation itself.

Follow Site not loading after setup for further troubleshooting.

Best practices before changing DNS

Before updating DNS records:

  • Keep a copy of the previous DNS records.
  • Make changes during a low-traffic period when possible.
  • Confirm you have access to the active DNS provider.
  • Avoid changing multiple DNS providers or nameservers at the same time unless required.

Lower TTL before a planned DNS change

If you are planning a DNS change in advance, consider lowering the TTL of the records you will change.

A lower TTL can help recursive DNS resolvers refresh those records sooner after you update them.

Important: Lowering the TTL does not take effect immediately. The previous, higher TTL may remain cached until it expires. Lower the TTL far enough in advance for the new value to propagate before making the actual DNS change.

After the DNS change has propagated and the new configuration is stable, you can restore the TTL to its normal value.

Need help?

Contact Support if DNS records appear correct but the issue persists.

Include:

  • The affected domain
  • The DNS record type and value
  • A screenshot of the DNS provider record
  • The time the DNS change was made
  • Any error message shown in the EDGE dashboard
  • Results from a DNS lookup or propagation checker

This helps Support determine whether the issue is still related to DNS propagation or requires further setup troubleshooting.

Where to go next

Now that you understand how DNS propagation works, continue with the next guide that matches your setup status.