What Is DNS Propagation?
DNS propagation is the process by which updated DNS records spread across the global network of DNS resolvers. After changing a DNS record, it can take minutes to 48 hours for all resolvers worldwide to serve the updated information.
Why It Matters
When you set up domain forwarding and change your DNS records, the change doesn’t take effect instantly worldwide. DNS is a distributed, cached system — thousands of DNS resolvers around the world independently cache your records and refresh them on their own schedule.
During propagation, some visitors will see the old behavior and others the new. This is normal and temporary, but it can be confusing if you’re not expecting it.
How It Works
- You update your domain’s A record or CNAME to point to Domain Forward
- Your authoritative DNS server immediately serves the new record
- DNS resolvers worldwide still have the OLD record cached
- As each resolver’s cached record expires (based on TTL), it fetches the new one
- Eventually all resolvers serve the updated record
What Affects Propagation Speed
TTL (Time to Live): The most important factor. If your old record had a TTL of 86400 (24 hours), resolvers that just cached it will keep using the old IP for up to 24 hours.
Resolver behavior: Most resolvers respect TTL, but some (especially ISP resolvers) may cache records longer. Google DNS (8.8.8.8) and Cloudflare DNS (1.1.1.1) reliably respect TTL.
Multiple caching layers: Some corporate networks, routers, and operating systems add their own DNS caching layer on top of the resolver cache.
How to Prepare
- Lower TTL early. Set your current records to a low TTL (300 seconds) at least 24-48 hours before making changes
- Make the change. Update your DNS records to point to Domain Forward
- Verify gradually. Use DNS lookup tools to check propagation status across different regions
- Keep old servers running. Don’t shut down old hosting immediately — some visitors may still reach it during propagation
Related Terms
Related Features
Frequently
asked questions
Typically 15 minutes to 4 hours for most resolvers. In rare cases, resolvers with aggressive caching can take up to 48 hours. The actual time depends on the TTL of the old record that resolvers have cached.
You can't force global propagation faster, but you can prepare by lowering the TTL of your existing records to 300 seconds (5 minutes) at least 24-48 hours before making changes. This ensures resolvers have short-lived caches when you make the switch.
Still Confused? Try It Free.
Set up your first domain forward in under 5 minutes. Free plan includes 5 domains.