DNS Propagation — What to Expect During Cutover

After you point your domain at iWebVault, there’s a period where the change spreads across the internet. This is ‘propagation’, and understanding it stops the normal cutover from feeling like something’s broken.

What propagation actually is

DNS answers are cached by servers around the world to keep the internet fast. When you change your nameservers or records, those caches need to expire before everyone sees the new answer. That expiry period is propagation.

How long it takes

• Typical: 1–4 hours for most visitors
• Worst case: up to 24–48 hours globally
• Your own connection: may update sooner or later than others

What you’ll see during propagation

For a while, some visitors reach iWebVault and others still hit your old host — depending on whose cache has updated. This is why you keep the old account running and check email on both servers during this window. It’s normal, not a fault.

Checking propagation

You can use a DNS propagation checker to see which regions have updated. When it shows your new iWebVault nameservers or IP globally, propagation is essentially complete.

After it completes

Once propagation finishes, all visitors and all new email reach iWebVault. At that point you can safely retire your old account after a final check.

A mental model for propagation

Think of DNS as a giant address book that’s been photocopied and handed to servers all over the world for speed. When you change your address (point to iWebVault), each photocopy has to be updated — and they update at different times depending on how long each was told to keep its copy. That ‘how long to keep it’ value is the TTL, and it’s why propagation isn’t instantaneous.

How TTL controls the wait

Every DNS record has a TTL — a number of seconds that resolvers cache the answer. If your TTL is 14400 (4 hours), some resolvers may serve the old answer for up to 4 hours after your change. If you lower it to 300 (5 minutes) a day before cutover, the world refreshes your record far faster. Lowering TTL ahead of time is the single most effective way to speed up a cutover.

1. A day before cutover, lower your record TTLs to 300 seconds
2. Wait for the old (longer) TTL to expire so the low value takes hold
3. Make your cutover change
4. Propagation now completes in minutes for most resolvers

What you’ll observe during propagation

For a period, your site and email may resolve to iWebVault for some visitors and the old host for others, purely depending on whose cached copy has refreshed. Your own connection might update before or after others. This split is completely normal — it’s not a sign anything is broken.

Checking propagation status

Online DNS propagation checkers query resolvers in many countries and show which have your new answer. When they show iWebVault’s nameservers or your new IP consistently across regions, propagation is effectively done. Your own machine can be flushed (restart the browser, or clear the OS DNS cache) to pick up the change sooner locally.

Don’t keep changing things

When propagation is genuinely complete

Once checkers show your new destination everywhere and both your site and email consistently land on iWebVault, propagation is finished. At that point, after a final verification, you can safely cancel your old hosting account.

The address-book analogy in full

DNS behaves like a phone book that’s been photocopied for speed and handed to servers worldwide. When you change your listing (point to iWebVault), each photocopy must be updated — and they update at different times depending on how long each was told to keep its copy. That ‘how long to keep it’ value is the TTL. Propagation is simply the world’s photocopies catching up to your new listing, and the TTL governs how fast that happens.

Using TTL to your advantage

1. A day before cutover, lower your record TTLs to 300 seconds
2. Wait for the previous, longer TTL to expire so the low value takes effect
3. Make your cutover change
4. Most resolvers now refresh within minutes rather than hours

Lowering TTL ahead of time is the single most effective lever for a fast cutover. Without it, resolvers may serve the old answer for as long as the previous TTL dictated — sometimes many hours.

What’s normal during the window

For a period, your site and email may resolve to iWebVault for some visitors and the old host for others, depending purely on whose cached copy has refreshed. Your own connection might update before or after others. This split is entirely normal and not a fault — which is exactly why you keep the old account live and check email on both servers until it settles.

Checking and confirming

Online propagation checkers query resolvers across many countries and show which have your new answer. When they consistently show iWebVault’s nameservers or your new IP worldwide, propagation is effectively complete. Locally, restarting your browser or clearing your operating system’s DNS cache helps your own machine pick up the change sooner if you’re impatient to see it.

Patience beats fiddling

What’s next

• Pointing Your Domain to iWebVault
• Keeping Email Flowing During a Migration
• How to Migrate With Zero Downtime

Still stuck? Our team can run or finish the migration for you — open a support ticket and we’ll take it from there.