When you move a domain, change DNS records, or set up a new nameserver, you won’t always see the change everywhere immediately. This is due to DNS propagation: the time needed before all DNS servers worldwide have retrieved and stored the new information. This usually takes a few hours, but it can sometimes take a day or longer due to caching. In this article, you’ll learn why this happens, how to check it, and what you can do to prevent problems.
What exactly is DNS propagation?
DNS works with a system of servers that pass information to each other. When you change an A record, MX record, or nameserver, that change must first be processed by your hosting provider or registrar. After that, all DNS resolvers on the internet (for example, at internet providers and public DNS services) need to replace their old, cached version with the new one. This process of spreading and refreshing is called propagation.
Because not every resolver refreshes its cache at the same time, visitors from different locations or providers may temporarily see a different version of your website or email.
Why does propagation sometimes take so long?
The most important factor is the TTL (Time To Live) of a DNS record. This is a setting that indicates how long a resolver may remember a record before it has to request it again. If the TTL is set to a high value, for example, many resolvers will hold onto the old data longer, even though you’ve already made the change.
In addition, these factors play a role:
- Some internet providers and networks refresh their own DNS cache less often than others.
- When moving nameservers (for example, when switching registrars), it often takes longer because the data at the registrar itself also needs to be updated.
- Browsers and operating systems sometimes have their own local DNS cache, separate from your internet provider.
Checking DNS propagation
You don’t have to guess whether a change has already taken effect everywhere. There are a few ways to check this yourself.
Use an online DNS check tool
There are free online tools that let you see what a DNS record looks like from various locations worldwide. This gives you an instant overview of whether the change has arrived everywhere.
Query the record via the command line
With commands like nslookup or dig, you can directly ask a specific DNS server what value it currently returns for your domain.
Check in Plesk
Log in to Plesk and view the DNS management for your domain to see which records are set and whether they match what you expect. This way, you know for sure that the source is correct, regardless of what resolvers are still showing.
Clear your local DNS cache
Sometimes you still see the old situation simply because your own computer or router has remembered the old value. Clearing the local DNS cache or restarting the router can already solve this.
Reducing propagation time and preventing problems
Although you can never fully speed up propagation, you can prevent a lot of trouble by planning smartly around a change.
- Lower the TTL well in advance if you’re planning a major change, such as moving a domain to another host.
- Preferably make changes outside of busy hours, so that any delay has less impact on visitors or email traffic.
- After making a change, always check whether your email settings (MX records) are correct, especially if you’re switching to a different business email solution, so that no email is lost during the transition.
- When moving a domain, only set the new nameservers once everything is ready on the new side, so visitors never end up on an empty or incomplete website.
Moving to a new provider? Read how to tackle this step by step via switching to Tandata, and see how domain names and DNS management come together in this process.
Frequently Asked Questions
How long does DNS propagation take on average?
This depends heavily on the TTL setting and the resolvers involved. Often a change is largely visible within a few hours, but due to caching, it can sometimes take longer before all locations are truly updated.
Can I speed up DNS propagation?
Not directly, but you can limit the impact by lowering the TTL of a record in advance. This way, resolvers refresh their cache faster as soon as the actual change takes place.
Why do I see something different on my phone than on my laptop?
Both devices may use different networks or DNS resolvers, each maintaining their own cache. This can cause a temporary difference in what you see, until both caches have been refreshed.
Does propagation also affect my email?
Yes, MX records also fall under DNS and experience the same propagation delay. Keep this in mind when switching to a different email provider, so that incoming email doesn’t temporarily end up on the wrong server.
Conclusion
DNS propagation is a normal part of every DNS change and is usually completed within a limited time. By lowering the TTL in advance, making changes during quiet times, and properly checking your DNS settings in, for example, Plesk, you can prevent most problems and unpleasant surprises.