Moving a website to a new VPS involves more than transferring files and databases. Your domain must point to the new server, while email and other DNS-dependent services continue working normally.

A poorly planned DNS change can cause website downtime, missed emails, broken verification records, or temporary service interruptions.

If you want to migrate website to VPS safely, prepare the new server first and make DNS changes only after checking the records your domain currently uses.

This checklist explains how to handle the DNS switch while reducing the risk of website and email disruption.

1. Record Your Existing DNS Configuration

Before changing anything, document the DNS records currently associated with your domain.

Important records may include:

• A record — Points a hostname to an IPv4 address.
• AAAA record — Points a hostname to an IPv6 address.
• CNAME record — Maps one hostname to another.
• MX record — Determines where incoming email is delivered.
• TXT record — Used for SPF, DKIM, domain verification, and other policies.
• CAA record — Defines which certificate authorities can issue SSL certificates.

DNS Backup Checklist

• Record A and AAAA records
• Record all MX records
• Save SPF and DKIM records
• Check CNAME records
• Check verification and other TXT records
• Save a copy of the complete DNS configuration

This backup makes it easier to restore or compare records if something stops working after the migration.

2. Prepare and Test the New VPS

Do not point your domain to an untested server.

Configure the new VPS with everything your website requires, including the web server, database, application files, SSL certificate, firewall rules, and required services.

Before changing DNS, verify:

• Homepage and important pages load correctly
• Database connections work
• Login and forms function correctly
• Images and static files load
• HTTPS is configured
• Application settings are correct
• Required ports are accessible

The new VPS should be ready to receive production traffic before the DNS switch begins.

3. Lower the DNS TTL

TTL, or Time to Live, controls how long DNS information can remain cached by resolvers.

A high TTL can make a DNS change take longer to reach users. Before migration, lower the TTL for the records you expect to change.

A value such as 300 seconds is commonly used during planned migrations, although the appropriate value depends on your DNS provider and setup.

Lower the TTL before the actual switch so previously cached records have time to expire.

TTL Checklist

• Check the current TTL
• Lower the TTL before migration
• Allow time for the previous TTL to expire
• Keep the lower TTL during the transition
• Restore the normal TTL after migration is stable

Lowering TTL can help make the transition faster, but it does not guarantee instant DNS propagation.

4. Choose Between an A Record Change and Nameserver Change

There are two common ways to point a domain to a new VPS.

Change the A Record

If your current DNS provider will continue managing DNS, change the website’s A record to the new VPS IP.

For example:

example.com → Old VPS IP

becomes:

example.com → New VPS IP

This is often the simpler option because existing MX, TXT, and other DNS records remain under the same DNS provider.

Change the Nameservers

You can instead move DNS management to a new provider by changing the domain’s nameservers.

For example:

ns1.old-provider.com

ns2.old-provider.com

becomes:

ns1.new-provider.com

ns2.new-provider.com

If you choose this method, recreate all required DNS records at the new provider before changing the nameservers.

Otherwise, email, verification services, subdomains, or other applications may stop working.

5. Protect Email Before the DNS Switch

Email requires special attention during a website migration.

If your email provider is staying the same, moving the website to a new VPS does not normally require changing the MX records.

Before the migration, identify:

• Current MX records
• Email provider
• SPF record
• DKIM records
• DMARC policy
• Email-related CNAME records

A typical setup can look like:

Website A record → New VPS

MX records → Existing email provider

This allows the website and email to remain on separate systems.

Email Checklist

• Save existing MX records
• Confirm the email provider
• Preserve SPF records
• Preserve DKIM records
• Preserve DMARC records
• Test incoming email
• Test outgoing email

6. Point the Domain to the New VPS

Once the new VPS has been tested, update the required DNS record.

For example:

@ → 203.0.113.10

can be changed to:

@ → 198.51.100.20

If www uses a separate A or CNAME record, check that record as well.

Avoid changing unrelated DNS entries. The fewer unnecessary changes you make, the easier it is to troubleshoot the migration.

7. Keep the Old VPS Running

Do not shut down the old VPS immediately after changing DNS.

Some users may continue reaching the old server because of cached DNS information. Keeping it online gives you a fallback while traffic moves to the new VPS.

During this period, monitor:

• Website traffic
• Application logs
• Error logs
• Database activity
• Email delivery
• Customer activity

Wait until the new VPS is receiving normal traffic and critical services have been tested before removing the old server.

8. Verify DNS Propagation

After updating DNS, check the domain from multiple networks or DNS-checking tools.

Confirm that the website records point to the new VPS:

example.com → New VPS IP

Also verify that the MX records still point to the correct email provider.

Do not rely only on your own computer. Local DNS caching can make your system show an older result even when other users are already reaching the new server.

9. Test the Website and Email

A DNS migration should be considered successful only after the important services have been tested.

Website Tests

• Homepage loads
• HTTPS works correctly
• Login works
• Forms submit successfully
• Database-driven pages work
• Images and assets load
• Important URLs return the expected status

Email Tests

• Send an email from the business account
• Send an email to the business account
• Confirm incoming messages are received
• Check spam filtering
• Verify SPF, DKIM, and DMARC
• Check for mail delivery errors

This is especially important for ecommerce websites, SaaS platforms, and business websites that rely on email notifications.

10. Common DNS Migration Mistakes

Changing Nameservers Without Recreating DNS Records

Switching nameservers before copying existing records can break email, subdomains, verification services, and other applications.

Forgetting MX Records

If your email provider is not changing, there is usually no reason to replace the existing MX records during a website migration.

Changing Unrelated DNS Records

Modify only the records required for the migration. Unnecessary changes increase the chance of configuration errors.

Shutting Down the Old VPS Too Early

Keep the old server available until the new environment has been verified and traffic has moved successfully.

Assuming DNS Changes Are Instant

DNS caching means different users may see the old and new destinations at different times. Plan for a transition period.

11. Final DNS Migration Checklist

Before completing the migration, confirm:

• Existing DNS records are backed up
• New VPS is fully configured
• Website has been tested on the new server
• DNS TTL was lowered before the switch
• A/AAAA records point to the new VPS
• MX records point to the correct email provider
• SPF, DKIM, and DMARC records are preserved
• Required CNAME and TXT records are present
• DNS propagation has been checked
• Website forms and applications work
• Incoming and outgoing email work
• Old VPS remains available during the transition

Final Thoughts

A VPS migration does not have to disrupt your website or email. The safest approach is to prepare the new server first, document your DNS configuration, lower the TTL, protect your email records, and change only the DNS entries required for the migration.

If you are planning to migrate website to VPS, treat DNS as a separate migration step. Careful preparation and post-switch testing can prevent DNS errors from becoming website downtime or email delivery problems.