DNS propagation is the time it takes for DNS changes to update across DNS servers and caches.

When you point your domain to Pressidium EDGE, some visitors may reach the new EDGE route before others. This is normal while DNS changes are still propagating.

What this guide covers

This guide explains:

  • What DNS propagation means
  • Why DNS changes can take time
  • How to check whether your DNS records have updated
  • What to do while propagation is still in progress
  • When to contact Support

When to use

Use this guide when:

  • You recently changed DNS records for a site using Pressidium EDGE
  • Your domain works from some locations but not others
  • Your site still points to the previous destination
  • DNS lookup tools show mixed results
  • You want to confirm whether DNS propagation is still in progress

How DNS propagation works

DNS records are cached by DNS resolvers, ISPs, local networks, browsers, and devices.

When you update a DNS record, the new value does not appear everywhere at the same time. Some resolvers update quickly. Others continue using the old cached value until the record’s TTL expires.

TTL means Time To Live. It controls how long DNS resolvers can cache a DNS record before checking for a new value.

Expected propagation time

DNS propagation often starts within minutes, but full propagation can take longer.

Typical timeframes are:

  • Fast propagation: 15 minutes to 1 hour
  • Common propagation window: 4 to 24 hours
  • Maximum propagation window: up to 48 hours

Propagation time depends on your DNS provider, the previous TTL value, DNS resolver caching, and the location being checked.

Check whether DNS has propagated

Use the checks below to confirm whether your domain is resolving to the expected EDGE records.

Check your DNS provider

First, confirm that the DNS records were saved correctly at your DNS provider.

Check:

  • The correct domain or subdomain
  • The correct record type
  • The correct record value
  • No duplicate or conflicting records
  • The TTL value

If the record was not saved correctly, update it before continuing.

Check from multiple locations

Use a global DNS lookup tool to check your domain from different regions.

Some locations may show the new value while others still show the old one. That usually means propagation is still in progress.

Check from your computer

You can also check DNS resolution from your local machine.

For an A record, run:

dig example.com A

Or:

nslookup -type=A example.com

For a CNAME record, run:

dig www.example.com CNAME

Replace example.com with your domain.

The returned value should match the DNS value shown in your Pressidium EDGE setup instructions.

Clear your local DNS cache

If global checks show the correct value but your local machine still sees the old result, clear your local DNS cache.

Windows

Open Command Prompt as Administrator and run:

ipconfig /flushdns

macOS

Open Terminal and run:

sudo dscacheutil -flushcache
sudo killall -HUP mDNSResponder

Linux

For systems using systemd-resolved, run:

sudo systemd-resolve --flush-caches

You can also clear your browser cache or test in a private browsing window.

What to do while propagation is in progress

If your records are correct and propagation is still incomplete:

  1. Wait for DNS caches to expire.
  2. Avoid making repeated DNS changes.
  3. Recheck DNS from multiple locations after some time.
  4. Keep a note of when the DNS change was made.
  5. Continue only after the expected records appear consistently.

Making several DNS changes during propagation can make troubleshooting harder.

Common issues and solutions

DNS works from some locations but not others

This is normal during DNS propagation.

Wait for full propagation and check again later. Full propagation can take up to 48 hours.

DNS still shows the old value

Check the previous TTL value. If the old record had a long TTL, resolvers may keep using it until that TTL expires.

Also verify that the new record was saved correctly at your DNS provider.

DNS has propagated but the site still does not load

DNS propagation may be complete, but another part of the setup may still need attention.

Check:

  • The site is added in the Pressidium Dashboard
  • The domain is configured correctly
  • SSL is active or still provisioning
  • The origin is reachable
  • There are no conflicting DNS records

DNS has not propagated after 48 hours

If DNS still has not propagated after 48 hours:

  1. Verify the DNS record values again.
  2. Check for duplicate or conflicting records.
  3. Confirm the changes were saved at the DNS provider.
  4. Contact your DNS provider if the records are not being served correctly.

Best practices

Before making DNS changes:

  • Take a screenshot of your current DNS records.
  • Lower the TTL in advance, if your DNS provider allows it.
  • Make DNS changes during a low-traffic period when possible.
  • Keep a record of the old and new values.

After propagation is complete:

  • Confirm the domain resolves to the expected EDGE values.
  • Test the site in a browser.
  • Restore a stable TTL if you lowered it temporarily.
  • Monitor the site for connection or SSL issues.

Verification

DNS propagation is complete when:

  • DNS lookup tools show the expected EDGE values from most or all locations
  • Your local DNS lookup returns the expected value
  • The site loads through the expected domain
  • The Pressidium Dashboard no longer shows a DNS-related setup issue

Need help?

Open a support request if:

  • Your DNS records are correct but the site still does not work.
  • DNS still shows inconsistent or incorrect results after 48 hours.
  • The Pressidium Dashboard continues to show a DNS or connection error.
  • You are unsure which DNS records should be configured.

Include:

  • Domain name
  • DNS provider
  • Record type and value
  • Approximate time you made the DNS change
  • Screenshot of the relevant DNS records
  • Screenshot of any Dashboard error
  • Results from a public DNS lookup, if available

Where to go next