
DNS propagation is the delay between changing a domain’s DNS settings and everyone on the internet seeing the change. Most record changes show up within minutes to a few hours; nameserver changes usually take a few hours. Allow up to 48 hours before treating it as a problem, because resolvers around the world keep cached answers until their time to live (TTL) expires.
What is DNS propagation?
The Domain Name System (DNS) turns a name such as yourbusiness.co.zw into the IP address of the server that hosts the website or handles the email. If you are new to how domains work, start with what is a domain name.
The phrase “propagation” is a little misleading. When you change a record, the authoritative nameserver for your domain has the new answer straight away; nothing is pushed around the internet. The delay comes from caching. Resolvers run by internet providers, companies and public DNS services, as well as your operating system and browser, store answers they have looked up recently. Until each cached copy expires, that resolver keeps giving out the old answer. Each cache expires on its own schedule, which is why the change appears gradually.
How long does DNS propagation take?
There is no single figure, because it depends on what you changed and how long the old answer was allowed to be cached.
| Change | Typical time to be seen widely | What controls it |
|---|---|---|
| New record that was never looked up before | Usually minutes | Nothing cached yet, unless someone queried the name before it existed |
| Edit to an existing A, AAAA or CNAME record | Minutes to a few hours | The TTL the old record had |
| Edit to MX, SPF, DKIM or other TXT records | Minutes to a few hours | The TTL the old record had |
| Nameserver change | Usually a few hours; allow up to 48 hours | The registry’s delegation records, which are often cached for up to two days |
| New domain registration | Usually within hours of activation | When the registry publishes the domain; .co.zw applications first need ZISPA approval |
The 48-hour rule of thumb comes mainly from nameserver changes: the delegation records held by the registry for extensions such as .com are commonly cached for up to two days. Ordinary record edits are usually much faster.
What is TTL and why does it matter?
Every DNS record carries a TTL, in seconds, which tells resolvers how long they may cache it. A TTL of 300 means five minutes, 3,600 means one hour, and 86,400 means 24 hours.
- Lower TTL: changes are picked up sooner, at the cost of more lookups to your nameservers.
- Higher TTL: fewer lookups, but a change can take longer to be seen.
The key point is that lowering the TTL only helps if you do it in advance. Copies already cached under the old TTL keep it. If a record had a TTL of 86,400, lower it to 300 at least a day before a planned move, make the change, then raise it again once everything works.
Why does my site work for some people and not others?
Because different people use different resolvers, and each one cached the old answer at a different time. During propagation it is normal for:
- the site to load on mobile data but not on your office Wi-Fi;
- a colleague on another network to see the new site while you still see the old one;
- email to start arriving at the new host before the website switches, or the other way round;
- one browser to show the new version and another the old.
For this reason, keep your old hosting active until the change has finished, so nobody reaches an empty site and no email is lost.
How do you check DNS propagation?
- Use a public checker such as whatsmydns.net to see which answer resolvers in different countries are returning for your record.
- Query directly from a computer: nslookup yourdomain.co.zw on Windows, or dig yourdomain.co.zw on macOS and Linux. Querying your authoritative nameserver shows the answer you published.
- Clear your own cache: restart the browser, or on Windows run ipconfig /flushdns.
- Try another network, for example a phone on mobile data, to compare.
Can you speed up DNS propagation?
You cannot force other resolvers to drop their cache, but you can shorten the wait next time:
- Lower the TTL on the records you will change a day or more before you change them.
- Change individual records (for example the A record) rather than nameservers when you only need to move the website.
- Get the new records right the first time. Each correction restarts the wait for anyone who cached the wrong answer.
- Do not look up a new hostname before you create it, or resolvers may cache the fact that it does not exist.
How to move a website without propagation downtime
A planned move to a new host can be invisible to customers if you follow this order:
- A day or two before, lower the TTL on your A and MX records to 300 seconds.
- Copy the website, databases and mailboxes to the new host while the old one keeps running.
- Test the site on the new server before switching, for example with a temporary URL or a hosts-file entry on your own computer.
- Change the records or nameservers to the new host.
- Keep the old hosting active for at least 48 hours, and check the old mailboxes for anything delivered there late.
- Once traffic has moved, issue the SSL certificate on the new host and raise the TTL again.
Avoid editing the website on the old server during the switch; changes made there will not appear on the new one.
When is it not propagation?
Waiting does not fix a wrong record. If the site still fails everywhere after the TTL has passed, check:
- the nameservers at the registrar are spelled correctly and match your new host;
- the A record points to the right IP address;
- the new server actually has the site files and the domain added to the account;
- MX records point to the right mail server, and old ones have been removed.
Some things only work after propagation finishes. On Tremhost hosting, free SSL (AutoSSL) and new subdomains need the domain to point to Tremhost first, so if either fails straight after a change, wait and try again. You can review and edit records yourself by following how to edit DNS records.
Frequently asked questions
Why does DNS propagation take up to 48 hours?
Mainly because nameserver delegation records can be cached for up to two days. Most changes are visible far sooner, but 48 hours is a safe upper limit before investigating.
Does propagation affect email?
Yes. MX record changes follow the same caching rules, so some senders may deliver to your old mail server for a while. Keep old mailboxes active until the change completes, then check them for stray messages.
Will my website go offline while DNS propagates?
Not if both servers are working. Visitors reach either the old or the new server. Problems arise only when the old hosting is cancelled too early.
How long does a .co.zw domain take to work?
A new .co.zw must first be approved by ZISPA, which aims to process applications within one working day once the paperwork is complete. After that, DNS behaves like any other domain.
Do I need to clear my cache to see the change?
It can help. Your browser and operating system keep their own copies, so restarting the browser or flushing the DNS cache may show the new answer sooner, but it does not affect what other people see.
Next step
If your change still has not appeared after 48 hours, see Tremhost’s Help Centre guide to propagation time and contact support by ticket or WhatsApp, Monday to Friday, 08:00 to 17:00 CAT. If you are moving a website, Tremhost’s free website migration copies your cPanel site first and keeps it live until the switch, so propagation does not cause downtime.


