Most guides on how to transfer a website to a new host tell you what to do: copy the files, lower the TTL, switch DNS, wait. That's the right order, and if you want the full list we keep a step-by-step website migration checklist for exactly that.
This piece is about the part those checklists skip: what is actually going on between the moment you press "save" on a DNS record and the moment the last visitor lands on the new server. Once you understand that window, "propagation" stops being a mystery you wait out and becomes something you can measure and control.
Propagation is mostly caches expiring
When you change an A record, nothing gets pushed out to the world. Your authoritative nameservers (the ones that hold your zone) start giving the new answer within seconds to a few minutes. Check each one listed in your NS records, because a lagging secondary nameserver is a real cause of mixed answers. Most of the delay comes from everyone else.
A visitor's browser asks a recursive resolver: their ISP's, their office router's, or a public one like 1.1.1.1 or 8.8.8.8. That resolver asked your nameserver some time ago, got an answer with a TTL attached, and is allowed to reuse that answer until the TTL runs out. Until then it doesn't ask again. So "DNS propagation" is really thousands of independent caches, each expiring on its own clock.
That gives you two practical rules:
- The worst case after a change is roughly the TTL that was on the record before the change, not after it.
- The browser, the operating system and some home routers keep small caches of their own, so one person can still see the old site for a while even after their resolver has moved on.
If you want to know how the resolvers Indian users actually hit compare, we covered them in our guide to the fastest DNS resolvers in India.
Why you lower the TTL one full old-TTL period ahead
Say your A record has a TTL of 86400 (one day). You lower it to 300 at 10 am today. A resolver that cached the record at 9:59 am got it with the old 86400-second TTL, and it will keep that copy until 9:59 am tomorrow. Lowering the TTL only affects answers handed out after the change.
So the rule is: lower the TTL, then wait at least one full period of the old TTL before you switch the IP. With a one-day TTL, lower it at least a day ahead. With a four-hour TTL, four hours is enough (give it a little extra). After that wait, every cache holds a copy that expires within five minutes, so your switch takes effect within about five minutes too.
Caveats worth knowing:
- Some resolvers enforce their own minimum TTL and hold a record longer than you asked. It's uncommon with the big public resolvers, but it's one reason you keep the old server running anyway.
-
Changing nameservers is a different case. If you're also moving the zone to new nameservers, the NS records that matter sit with the registry for your TLD, and the registry sets their TTL. You can't lower it. You can see it: for a .com, run
dig +norecurse @a.gtld-servers.net example.com NS(for a .in, find the TLD's servers withdig NS in +shortand query one of those instead). The TTL in the authority section is the delegation TTL you have to wait out; for .com it is two days. The safe way is to make the new nameservers serve an identical, already-correct zone before you change NS at your registrar, so it doesn't matter which set a resolver asks. -
Check DNSSEC before a nameserver change. Run
dig DS example.com +short. If it returns anything, DNSSEC is on. Either remove the DS record at your registrar and wait out its TTL before changing nameservers, or set up signing at the new DNS provider and add its DS record first. A DS record that doesn't match the new nameservers makes the whole domain, mail included, fail to resolve for validating resolvers such as 1.1.1.1 and 8.8.8.8.
Checking DNS yourself with dig
Don't rely on a "propagation checker" website alone. dig tells you exactly what each layer is saying. Install it if needed:
# Ubuntu / Debian
sudo apt update && sudo apt install bind9-dnsutils
# AlmaLinux / Rocky / RHEL
sudo dnf install bind-utils
(On Debian and Ubuntu the older dnsutils package name also still works.)
Find your authoritative nameservers, then ask one of them directly:
dig +short NS example.com
dig @ns1.your-dns-provider.net example.com A +noall +answer
The answer from the authoritative server shows the configured TTL and the current IP. This is the source of truth: if it's wrong here, it's wrong everywhere.
Now ask a couple of public resolvers:
dig @1.1.1.1 example.com A +noall +answer
dig @8.8.8.8 example.com A +noall +answer
The number in the second column is the remaining TTL in that resolver's cache. If it still shows a large number (thousands of seconds) after you lowered the TTL, that resolver holds an old long-lived copy, and that number tells you roughly how long is left. Don't expect a neat countdown between runs: each public resolver is many separate caches behind one IP, so consecutive answers can jump around. Look at the highest value you see. For your own view, your ISP's resolver is the one that matters.
Do the same for www, for MX, and for any other record you're changing. A common mistake is moving the apex record and forgetting that www is a separate A record, or a CNAME pointing somewhere else.
Check IPv6 as well:
dig example.com AAAA +noall +answer
dig www.example.com AAAA +noall +answer
If the old host published an AAAA record, visitors on IPv6 (a large share of Indian mobile and broadband users) connect to that address whatever your A record says. Lower the AAAA TTL in advance like the A record, then at switch time either point it at the new server's IPv6 address or delete it. If you forget, IPv6 visitors keep reaching the old server indefinitely.
Test the new server before the world can see it
You should be able to load the site from the new server while DNS still points at the old one. Two ways:
The hosts file. Add a line mapping your domain to the new IP. On Linux and macOS it's /etc/hosts; on Windows it's C:\Windows\System32\drivers\etc\hosts (edit it as administrator):
203.0.113.10 example.com www.example.com
Your machine now resolves the domain to the new server and nobody else's does. If the browser still shows the old site, it is usually the browser's own DNS cache or a connection it already has open to the old IP: close all its windows (or clear the cache at chrome://net-internals/#dns) and check which IP it actually connected to under DevTools > Network > Remote Address. Remove the line when you're done, or you'll confuse yourself later.
curl with --resolve. This is cleaner because it changes nothing on your machine, and it is the unambiguous check:
curl -sI --resolve example.com:443:203.0.113.10 https://example.com/
curl -sI --resolve www.example.com:443:203.0.113.10 https://www.example.com/
--resolve makes curl connect to that IP while still sending the right hostname for TLS (SNI) and the Host header, so you're testing exactly what a real visitor will get. If the new server has no certificate yet, add -k to skip verification, and take that as a reminder to read the SSL section below.
The override applies only to the exact host and port you give it. To check the HTTP-to-HTTPS redirect, add one for port 80:
curl -sI --resolve example.com:80:203.0.113.10 http://example.com/
If you follow redirects with -L, every hostname and port in the chain needs its own --resolve, otherwise curl quietly goes back to normal DNS and tests the old server. Also note these tests only exercise IPv4; the AAAA check above covers the IPv6 side.
Check more than the homepage: a deep URL, a page that reads from the database, the login, a form, and a URL that should return 404. A 500 error or a blank page after the move most often comes from a PHP version mismatch or a missing PHP extension. Check the PHP error log on the new server.
Email: the part that fails quietly
Website downtime is loud. Lost email is quiet, and people find out days later. A few things to understand:
Mail in flight is retried, not lost. If a sending server can't deliver, it queues the message and retries for anywhere from about a day to five days, depending on the sender. That covers brief hiccups, but it doesn't help when mail is delivered successfully to the wrong server.
During the switch, mail can land on both servers. Senders look up your MX record through their own resolvers, so for a while some deliver to the old mail server and some to the new one. MX usually points at a hostname such as mail.example.com, and in a host move it is usually that hostname's A (and AAAA) record that changes, not the MX record itself. So lower the TTL on the MX record and on the address records of the mail hostname it points to. Keep checking the old mailboxes for a few days after the switch. If you use IMAP, a tool like imapsync can do a final copy from old to new once things settle.
If your email is hosted somewhere else, leave MX alone. When mail runs with a separate provider, a web host move should leave the MX, SPF, DKIM and DMARC records exactly as they are. The danger comes when you change nameservers and the new zone is missing those records. Compare the old and new zones record by record before switching.
If mail is moving with the site, add the new server's sending IP to your SPF record before switching. DKIM needs more care. It is the server that sends the mail that has to sign with a key matching DNS, and cPanel uses the same selector (default._domainkey) on every server. If you publish the new server's key under that selector while the old server is still sending, the old server's mail fails DKIM. So either publish the new key at the moment you switch outgoing mail, or use a different selector on the new server so both keys can sit in DNS during the overlap.
SSL: before or after the switch?
This decides whether visitors see a browser warning on the day. Let's Encrypt validates that you control the domain in one of two main ways:
-
HTTP-01: the CA fetches a file from
http://example.com/.well-known/acme-challenge/.... That only works once DNS points at the new server, because the CA has to find the new IP (unless you proxy the challenge path from the old server, which is more work than it is worth for most sites). So with HTTP-01 the certificate is issued after the switch, and there is a gap. On cPanel, AutoSSL issues it on its next scheduled run, which can be hours away unless you (or your host) trigger it by hand right after the switch. Many hosts issue automatically once DNS resolves to them or let you trigger it yourself, but if any gap is not acceptable, use DNS-01 or copy the old certificate first. -
DNS-01: you prove control by publishing a TXT record at
_acme-challenge.example.com. It doesn't care where the A record points, so you can get the certificate before you switch. It's also the only way to get a wildcard certificate.
With certbot, a manual DNS-01 run looks like this:
sudo certbot certonly --manual --preferred-challenges dns \
-d example.com -d www.example.com
Run this on any Linux machine you control; it doesn't have to be the web server. certonly writes the certificate and key to /etc/letsencrypt/live/example.com/. On shared hosting, where you have no root, you then paste the contents of fullchain.pem and privkey.pem into cPanel > SSL/TLS > Install. A manual certificate won't renew on its own. For automatic renewal you need a DNS plugin for your DNS provider, or you let the new server switch to HTTP-01 renewals (AutoSSL on cPanel) after the move.
The third option is to copy the existing certificate and private key from the old server. That works until the certificate expires.
If your site sends HSTS (check the response headers for Strict-Transport-Security), returning visitors' browsers will refuse to load it at all during any certificate gap, with no "proceed anyway" option. In that case, issue or copy the certificate before the switch.
One more check before cutover: run dig CAA example.com. If a CAA record allows only one specific CA and your new host issues from a different one, issuance fails whichever challenge you use.
Dynamic sites: watch the database during the window
For a static site, two servers answering at once is harmless. For WordPress, WooCommerce or anything with a database, it isn't. During the switch, a comment, an order or a form entry can be written to the old database by a visitor whose resolver hasn't moved yet. Either switch at a quiet hour (late night or early morning IST for an Indian audience) and put the old site into maintenance mode once most traffic has moved, or plan a final database export and check for anything written after your copy.
Keep the old host for a week
Cancelling the old plan on switch day removes your rollback and the place where late email and stragglers land. Keep it running for at least seven days. During that week:
- Watch the old server's access log. When it goes quiet apart from bots, the caches have expired.
- Check the old mailboxes for anything delivered late.
- Once everything is stable, raise the TTL back to something normal (an hour or more) so resolvers aren't asking every five minutes.
If you'd rather not do this yourself
All of the above is manageable with a terminal and a calm evening, but it's also easy to get slightly wrong. If you're moving to our cPanel web hosting or managed WordPress hosting, migration is free and done by our team. For WordPress, we move the site, database, uploads and email and give you a preview URL to check before DNS changes. For cPanel accounts, we move every site, database, email account and DNS record from your current cPanel host. Either way, nothing at your old host is deleted until you confirm. The servers for both are in India. The rest of what we offer is on the Bigdomainhost homepage.
Whether you do it yourself or hand it off, the principle is the same: the new server should be complete and tested before a single resolver sees its IP, and ideally already holding a valid certificate.
Disclosure: written by the team at Bigdomainhost, an Indian hosting provider. We sell the hosting linked above.
Top comments (0)