DNS record changes on Host Dada usually show up everywhere within an hour. Nameserver changes take longer, typically a few hours and occasionally up to 48 hours. Here's why, and how to check progress from anywhere in the world.
Typical timings
| Change | Usually | Worst case |
|---|---|---|
| Adding a brand-new record (for example a TXT for verification) | A few minutes | About 1 hour |
| Changing an existing record on Host Dada DNS (A, CNAME, MX, TXT) | Under 1 hour | A few hours on networks that cache aggressively |
| Changing nameservers | A few hours | 24 to 48 hours |
| Transferring a domain (registration only, nameservers unchanged) | No DNS change. Website and email keep working | n/a |
Why it isn't instant
To keep the internet fast, internet providers and devices remember (cache) DNS answers for a set time called the TTL (time to live). Records on the Host Dada nameservers use a TTL of one hour, so after you change one, some visitors may see the old answer for up to an hour. Nameserver changes are slower because the domain registries (Nominet for .uk, Verisign for .com) tell resolvers to cache nameserver details for up to two days.
This spread of the new value is often called DNS propagation. While it's happening, some people may see your old website or email server and others the new one. That's normal.
How to check progress
- Use a global checker. Go to whatsmydns.net, enter your domain, pick the record type (A for a website, MX for email, NS for nameservers) and run the search. Green ticks with the new value mean that location has the change.
- Check the nameservers. Choose NS. When the results show
ns1.kandekore.nettons4.kandekore.net, the domain is pointing to Host Dada. - Check from your own computer. Open a private browsing window, or use your phone on mobile data instead of Wi-Fi. This avoids your browser's and router's cache.
Clear your own cache
- Windows: open Command Prompt and run
ipconfig /flushdns. - Mac: open Terminal and run
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. - Browser: close every window and reopen, or use a private window.
- Router: turning it off and on again clears its cache.
Troubleshooting
It's been more than 48 hours and nothing has changed
The change probably didn't save. Check the nameservers at your registrar, or the record in Manage DNS, and confirm the value is correct. If the NS check still shows your old provider, the nameserver change wasn't accepted.
Some people see the new site and others the old one
That's propagation in progress. Leave both old and new hosting running until the checker shows the new value everywhere, then wait one more day before cancelling the old hosting.
Email is going to the old server
Senders' mail servers also cache MX records. Keep the old mailbox active for a few days after the switch and check it for stragglers.
Last reviewed: October 2026
