When you change your domain's DNS settings — such as pointing it to a new server or changing nameservers — those changes don't take effect everywhere instantly. The process of DNS changes spreading across the internet is called DNS propagation.
Why Does DNS Propagation Take Time?
DNS records are stored in caches at multiple levels — your ISP's DNS server, your router, your operating system and your browser. Each cached record has a TTL (Time to Live) value that determines how long it's stored before being refreshed. Until the old TTL expires, DNS servers continue serving the old record.
What Is TTL?
TTL (Time to Live) is a value in DNS records that tells DNS resolvers how long (in seconds) to cache that record. Common values:
- 300 seconds (5 minutes) — Fast propagation, useful before planned changes
- 3600 seconds (1 hour) — Moderate, common default
- 86400 seconds (24 hours) — Slow propagation, reduces DNS server load
Pro tip: Lower your TTL to 300 seconds 24–48 hours before making DNS changes. This shortens propagation time significantly.
Why Different Users See Different Results
During propagation, some users see the old website while others see the new one. This depends on:
- Which DNS resolver their ISP uses
- Whether their local cache still holds the old record
- Their geographic location
How to Check DNS Propagation
Use our free DNS Lookup tool to check what IP address your domain currently resolves to. You can also use online propagation checking tools that query DNS servers in multiple countries simultaneously.
How to Speed Up DNS Propagation
- Lower TTL before making changes (as described above)
- Flush your local DNS cache (on Windows:
ipconfig /flushdns) - Switch to a faster public DNS resolver like Google (8.8.8.8) or Cloudflare (1.1.1.1)