This page contains affiliate links. If you make a purchase through one, we may earn a commission at no extra cost to you.
Once you’ve moved your site to a new host, there’s one more step that trips people up: pointing your domain’s DNS at the new server. Getting this wrong is the single most common reason a “completed” migration still shows the old site, or shows nothing at all. Here’s what’s actually involved.
The Two Ways to Point a Domain
You have two real options, and they’re not the same thing. Changing your nameservers hands off DNS management entirely to your new host — you point your domain’s nameservers at theirs, and they control every record from there. Changing an individual A record keeps your existing DNS management in place and just updates where your domain name resolves to for web traffic specifically, leaving email and other records untouched. If your new host manages DNS for you, nameserver changes are usually simpler. If you want to keep your current DNS provider and only change where the website itself lives, an A record update is the more surgical option.
How Long This Actually Takes
The old advice of “wait 24 to 48 hours” is outdated and overly cautious for most cases today. In practice, most DNS changes are visible within an hour, and often much faster, though the exact timing depends on your TTL (time to live) setting and how your visitors’ ISPs cache DNS records — some ISPs update their cache only every two or three days regardless of your TTL, which is the actual source of the rare cases where propagation genuinely does take longer. Changing nameservers generally takes a bit longer to fully propagate than updating a single A record, since it involves an extra step at the domain registry level.
Lower Your TTL Before You Make the Change
This is the one real trick that actually speeds things up: if you can, lower your DNS record’s TTL to a short value (5 minutes is a common, reasonable choice) a day or so before you plan to make the actual switch. A low TTL tells resolvers to check back for updates more frequently, so when you do make the change, it propagates faster than it would with a longer default TTL. Set it back to a normal, longer value once the migration is confirmed working — a permanently very low TTL adds a small amount of ongoing DNS lookup overhead for no benefit once you’re not actively changing anything.
Don’t Cancel the Old Host Yet
Keep your old hosting account active for at least a few days after the DNS change, not just until you personally see the new site load. Because of the caching behavior above, some visitors — and search engine crawlers — may still be resolving to the old server for a while after your own browser shows the new one. Cancelling the old host immediately after the switch is a common way to accidentally show some visitors a dead site during that overlap window. Whether you’re setting this up on Contabo or Netart (see our Contabo review or Netart review if you’re still deciding), both give you the IP address or nameserver details you need for this step in their respective control panels.
Do I need to change nameservers or just an A record?
Changing nameservers hands off all DNS management to your new host. Updating an A record only changes where your website resolves to, while keeping your current DNS provider and other records (like email) untouched. Pick based on whether you want your new host managing DNS entirely.
How long does a DNS change actually take in 2026?
Most changes are visible within an hour in practice, though the old 24-48 hour guidance still applies in rare cases where a visitor’s ISP caches DNS records longer than your TTL setting suggests.
When is it safe to cancel my old hosting account?
Wait at least a few days after the DNS change, not just until your own browser shows the new site. Some visitors and search crawlers may still be resolving to the old server during the caching window.