How long do DNS changes take to work?
It mostly depends on the TTL (time to live) set on the old record. Many changes show within minutes to a few hours, but some networks keep the old answer for a day or more. "Up to 48 hours" is a cautious rule of thumb, not a fixed limit.
What actually happens when you change DNS
DNS is the phone book of the internet. It turns your domain name into the address of your website or email server. When you edit a record, the new answer sits at your DNS host straight away.
The delay comes from copies. Internet providers and other resolvers keep copies of old answers so they do not have to ask again every time. Until a copy expires, some visitors still see the old site while others see the new one.
So "propagation" is not your change travelling around the world. It is old copies running out, one network at a time.
TTL: the timer that sets the wait
Every DNS record carries a TTL, a number of seconds. It tells resolvers how long they may keep a copy. The original DNS standards describe TTL as a limit on caching, set by whoever runs the zone.
A record with a TTL of 3600 can be kept for up to an hour after a resolver last fetched it. One with 86400 can be kept for a day.
Check the TTL in your DNS panel before you edit anything. That number is a good guide to your worst-case wait for most visitors.
- 300 seconds is five minutes
- 3600 seconds is one hour
- 86400 seconds is one day
Why "up to 48 hours" is only a rule of thumb
Many hosts quote 48 hours as a safe upper estimate. It covers the slow cases, not the usual one.
Some resolvers ignore low TTLs and hold records longer. Browsers, operating systems, office routers and apps can add their own caches on top.
Changing nameservers can also take longer than editing a single record, because the change has to be updated at the registry first and the old delegation may be cached too. For background on .pk names, see /pk-domain/.
If your site still looks wrong after a day, the cause is often a wrong record, not slow propagation.
How to check whether your change has spread
Do not trust only your own browser. It may be showing a cached page. Try these checks instead.
Wait for the TTL of the old record to pass first. Then compare results from different places, because one network can be ahead of another.
- Open the site on mobile data, then on home Wi-Fi.
- Use a free online DNS lookup tool that queries many locations.
- Run nslookup or dig for your domain and read the answer and TTL.
- Clear your browser cache or try a private window.
- Restart your router if only your office still sees the old site.
Speed it up: lower the TTL first
The best trick is planning. A day or two before a move, lower the TTL on the records you will change to something short, such as 300 seconds. Lowering it at the same moment as the change does not help, because resolvers already hold copies made under the old TTL.
Once the old TTL has passed, make your change. Many visitors will then switch within minutes. Afterwards, raise the TTL again so your DNS host is not queried more than needed.
This matters most when you move a shop, launch a new site or switch email. If you are still choosing a name, search at /domains/ or read /guides/ for setup steps.
A calm checklist for a DNS change
Small businesses and freelancers can follow the same steps every time. It keeps downtime low and avoids panic calls from clients.
If you register a name through us, it is filed in your own name. Our /order/ page and /register-pk-domain/ guide explain how new names are filed.
- Note the current records and TTL values before touching anything.
- Lower the TTL a day or two ahead.
- Make the change at a quiet hour for your customers.
- Test from more than one network.
- Keep the old server running until traffic has fully moved.
- Raise the TTL back afterwards.
Common questions
Is DNS propagation really 48 hours?
No. It is a cautious upper estimate. With a low TTL most visitors see the change within minutes or hours, but a few networks may hold the old answer longer.
Why can I see the new site but my client cannot?
Each network and device keeps its own cached copy. Yours expired first. Ask your client to try mobile data, a private window, or wait until the old TTL has passed.
Can I force DNS to update faster after the change?
Not for other people's resolvers. You can clear your own browser, device and router caches. For next time, lower the TTL a day or two before the change.
Does my domain name stop working during propagation?
Usually not. Visitors reach either the old or the new address, so keep the old server running until everyone has moved over.
Do .pk domains take longer to propagate?
The same caching rules apply. A change of nameservers can take longer than editing one record, because the registry must update first. See /pk-domain/ for background.