How to switch DNS after a migration (nameservers or A records)
On this page
After a migration, websites and email still run on the old server until the domains point here. The switch (cutover) is done at each domain's registrar or DNS provider, not in this panel.
Before you start
- A day before: lower the DNS TTL of the domains on the old server (for example to 300 seconds), so the switch spreads quickly.
- Just before: run the final sync and verify the websites.
Option A: change the nameservers (recommended)
- Open the account's migration page (Transfer Tool → server → Details, or Import a Backup → Open).
- In Point the domain here, copy the two nameservers with Copy.
- At each domain's registrar, replace the nameservers with these two.
DNS, websites and email then all move together, because this server answers for the zones it imported.
Option B: keep DNS at the registrar or another provider
If the customer keeps DNS elsewhere:
- Point the A records of the domain,
wwwandmailto the IP shown on the migration page. - Copy the email records (SPF, DKIM and DMARC) from the customer's Email page into that DNS.
Check the switch
The table in Point the domain here shows, for each domain, its Nameservers now, its A record now and its status:
- Uses our nameservers
- Points here (A record)
- Still on the old server
The card shows action needed while a domain still points to the old server, and All domains of this account point to this server. when the switch is complete.
What happens next
- Free SSL certificates are issued automatically as soon as the domains point here.
- Visitors move over as DNS caches expire. With a low TTL this takes minutes; otherwise up to the old TTL.
- Keep the old server running for a few days, until DNS has spread everywhere.
Common questions
Some visitors still see the old site. Why?
Their DNS resolver still caches the old address. It follows once the old TTL expires.
Mail arrives on both servers during the switch. What do I do?
That is normal while DNS spreads: some senders still use the old address. Messages that reached the old server stay there. Run the final sync as close to the switch as possible and lower the TTL beforehand to keep this window short.
Thank you — this helps us improve the article.
Still stuck?
Ask the AI about your exact situation — it answers from this knowledge base — or contact us.
Related articles
- How to run the final sync before switching DNS
Copy only what changed on the old server since the transfer — new files, new email and fresh databases — just before you point the domains here.
- How to check migrated websites before switching DNS
Compare every migrated website on the old and the new server with one click, before visitors are sent to the new server.
- After a migration: checklist for passwords, SSL, email and PHP
What to check after moving accounts: new passwords to send, warnings, SSL certificates, email records and routing, PHP versions, packages and resellers.
- What is copied in a migration, and what is not
The full list of what a transfer or backup import copies — websites, email, databases, DNS, cron, passwords — and what you must set up again.