How to point a domain to a new host (the DNS walkthrough)

Moving a site to a new host without downtime — the right order to change DNS records, and how to verify it propagated before announcing the move.

6 min read intermediateUpdated Jun 10, 2026
BI
Reviewed by the editorial team · Jun 10, 2026
Before you start
  • The new host's nameservers OR their A record IP
  • Admin access at your domain registrar

Step by step

  1. 01

    Lower the TTL 24 hours before the move

    At your registrar's DNS, change every record's TTL to 300 seconds (5 min) the day BEFORE you switch. This makes propagation fast on switch day.

  2. 02

    Choose: nameservers or A/CNAME records

    Nameserver swap = the new host runs all your DNS (simpler, but you lose registrar-side DNS). A/CNAME = you keep DNS at the registrar (more flexible, especially if you use Google Workspace for email).

  3. 03

    Make the switch

    Nameservers method: paste the new host's 2-4 nameservers, save. A record method: change the @ A record to the new IP, change www CNAME if needed.

  4. 04

    Verify globally

    whatsmydns.net → enter your domain → A record. Wait until 80%+ of the global checkpoints show the new IP. Usually 10-60 min with low TTL.

  5. 05

    Test the site directly

    Open in incognito + on mobile data (not Wi-Fi — your router caches DNS). Click into key pages, submit a form, check images load.

  6. 06

    Restore TTL to 3600

    Once stable, raise the TTL back to 1 hour. Low TTLs increase DNS lookup cost long-term.

Troubleshooting

Email stopped working after the move
You overwrote MX records. Add them back from your email provider (Google Workspace has 5 MX records, Microsoft 365 has 1).
IT & Technical · Done-for-you
Want the boring tech handled?

We set up domains, email, SSL, security and integrations so nothing breaks.

Book a tech call