How to handle DNS cutover when migrating to Web60

This article explains how to switch your domain's DNS to point at Web60 when migrating from another hosting provider. This step is called the DNS cutover.

Before the cutover

Only switch DNS after you have confirmed your site works correctly on Web60. Use the temporary URL provided in the portal to test your site thoroughly. Check that pages load, images display, forms work, and any important functionality behaves as expected.

If you have not already done so, lower your DNS TTL to 300 seconds at your current registrar at least 24 hours before the cutover. This speeds up propagation.

Step 1: Get your Web60 DNS details

Log in to the Web60 portal.
Go to Domain.
Note either the Web60 nameservers or the IP address (A record), depending on which method you will use.

Step 2: Log in to your current domain registrar

Go to the registrar where your domain is currently managed (for example, Blacknight, Register365, GoDaddy, or your previous host's domain panel). Find the DNS or nameserver settings for your domain.

Step 3: Update nameservers or A record

You have two options:

Option A: Change nameservers (recommended)

Replace your current nameservers with the Web60 nameservers. This hands full DNS control to Web60 and is the simplest approach. Web60 will manage all DNS records for you, including those needed for SSL and email.

Option B: Update the A record only

If you want to keep managing DNS at your current registrar, update the A record to point to the Web60 IP address. With this option, you remain responsible for managing all other DNS records (MX, SPF, DMARC, CNAME) at your registrar.

Step 4: Wait for DNS propagation

After making the change, DNS propagation begins. This is the process of the updated records spreading across the internet's DNS servers.

Worldwide propagation: up to 48 hours
.ie domains via IEDR: typically 2 to 4 hours

During propagation, some visitors will see your new Web60 site while others still see the old site. This is normal and temporary.

Step 5: Do not delete your old hosting yet

Keep your old hosting active for at least 48 hours after the DNS cutover. This ensures that any visitors still reaching the old server due to DNS caching can still see a working site. After 48 hours, propagation should be complete and you can safely cancel the old hosting.

Step 6: Set up email DNS records

If you changed nameservers to Web60 (Option A), your email DNS records (MX, SPF, DMARC) need to be configured in the Web60 portal. Do this immediately after the cutover:

Go to Domain then DNS Records in the portal.
Add your MX records for your email provider (Google Workspace, Microsoft 365, or other).
Add SPF and DMARC records.

If you noted these records before migration (as recommended in the pre-migration checklist), you can enter them directly. If you are unsure what records to use, contact your email provider for the correct values.

FAQ

Q: How long does DNS propagation take?

A: DNS propagation typically takes up to 48 hours worldwide. For .ie domains, IEDR propagation is usually faster at 2 to 4 hours. During propagation, some visitors may still see your old site.

Q: Should I update nameservers or just the A record?

A: Updating nameservers is recommended because it lets Web60 manage all your DNS records including those needed for email and SSL. Updating just the A record works but means you manage other records at your current registrar.

Q: What about my email? Will it stop working?

A: If you change nameservers, your MX records need to be set up in the Web60 portal after the cutover. Do this immediately after changing nameservers to avoid email disruption.