DNS Migration Checklist: How to Point Your Domain to a New VPS Without Email Disruption
Learn how to safely migrate your website to a new VPS while keeping website traffic and email services running smoothly.
Migrating a website to a new VPS is not complete when the website files and database have been moved. You also need to make sure your domain points to the new server correctly.
This is where DNS migration becomes important.
If DNS records are changed without checking the existing setup, your website may become temporarily unavailable, visitors may still reach the old server, or email services can stop working. The good news is that DNS migration does not have to be complicated. With the right checklist, you can migrate your website to a VPS while keeping both website traffic and email services running smoothly.
This guide explains how to move your domain to a new VPS, when to change DNS records, when to change nameservers, and what to check before and after the migration. For additional context, you can also refer to this DNS migration resource.
What Happens During a DNS Migration?
DNS, or Domain Name System, connects your domain name with the servers that handle your website and other services.
When you move a website from an old hosting server to a new VPS, the domain needs to be updated so visitors are directed to the new server.
However, a domain can have several DNS records for different services:
- A record – points a domain or subdomain to an IPv4 address
- AAAA record – points a domain or subdomain to an IPv6 address
- CNAME record – points one hostname to another hostname
- MX record – determines where email for the domain is delivered
- TXT record – commonly used for email authentication and verification
- NS record – identifies the nameservers responsible for the domain's DNS
The important point is that your website and email may use different DNS records. Changing one does not automatically mean the others should be changed.
Before You Start: Create a DNS Migration Checklist
Before touching your DNS settings, document the current configuration.
Log in to the DNS provider or domain registrar currently managing your domain and make a copy of the existing records.
Your checklist should include:
This step may look unnecessary, but it gives you a reference if something goes wrong.
Check Where Your Email Is Hosted
This is one of the most important checks before migration.
Your website might be hosted on the old server while email is handled by another provider such as a business email platform. In that situation, you usually do not want to replace the existing MX records with records from the new VPS.
Write down your current MX records before making changes.
MX → mail.example.com
or your email provider may use completely different MX hostnames.
Do not assume that moving the website means moving email.
Prepare the New VPS
Before changing DNS, make sure the new VPS is ready to receive traffic.
Install and configure everything your website requires, such as:
- Web server
- PHP or another required runtime
- Database
- SSL certificate
- Firewall rules
- Required extensions
- Application files
- Database
- Cron jobs
- Website configuration
If possible, test the website on the new VPS before changing the domain's DNS.
The goal is simple: when DNS starts sending visitors to the new VPS, the server should already be ready.
Copy the Website to the New VPS
Move your website files and database from the old hosting environment to the new VPS.
For a typical website, this may include:
- Website files
- Database
- Configuration files
- Uploaded media
- SSL configuration
- Scheduled tasks
If the website is receiving regular updates, orders, registrations, comments, or other database changes, pay special attention to the final database synchronization.
A simple file transfer is not enough if the live website continues changing while the migration is happening.
Lower the DNS TTL Before Migration
TTL stands for Time to Live. It controls how long DNS information can be cached before a fresh lookup is made.
Before the migration, you can lower the TTL of the records you plan to change.
For example, if the current TTL is several hours, reducing it to a shorter period before migration can make the eventual DNS change easier to manage.
So do not treat TTL as a magic switch that makes DNS changes immediate.
Decide Whether You Need to Change the A Record or Nameservers
This is an important decision during DNS migration.
Option 1: Change the A Record
If your current DNS provider will remain the same, you can usually update the website's A record to the new VPS IP.
example.com → 203.0.113.10
New:
example.com → 203.0.113.25
Your DNS provider stays the same. Only the destination for the website changes.
This approach can be useful when you want to keep your existing DNS management and email records exactly where they are.
Option 2: Change the Nameservers
You can also move DNS management to another provider by changing the domain's nameservers.
ns2.old-provider.com
could be replaced with nameservers supplied by the new DNS provider.
But this requires more preparation.
When nameservers are changed, the new DNS provider must contain all the important records from the old DNS zone. That includes not only the website record but also email-related records and any records used by subdomains or third-party services.
Protect Your Email Records
This is the part that deserves extra attention.
Your website's DNS records and email DNS records may serve completely different purposes.
MX Records
MX records tell mail servers where to deliver incoming email.
If you use an external email provider, keep its MX records intact.
SPF
SPF identifies which servers are authorized to send email for your domain.
Check your existing SPF TXT record before migration.
DKIM
DKIM helps authenticate outgoing email using cryptographic signatures. Your email provider may publish one or more DKIM-related DNS records.
DMARC
DMARC tells receiving mail servers how to handle messages that fail authentication checks and provides reporting options.
Make sure existing DMARC records are preserved if you move DNS management.
Important Rule
Do not change or delete MX, SPF, DKIM, or DMARC records simply because the website is moving to a new VPS.
Only change them if your email service itself is being migrated.
Change the Website DNS Record
Once the new VPS is ready and your DNS records have been checked, update the website's A record.
Host: @
Value: NEW_VPS_IP
If your website uses www, check its record as well.
Host: www
Value: example.com
or it may use a separate A record.
Do not assume that changing @ automatically fixes every hostname. Check the actual DNS configuration.
Check IPv6 Before Going Live
One commonly missed issue is the AAAA record.
If your domain has an AAAA record pointing to the old server's IPv6 address but the new VPS is not configured for that IPv6 address, some users may still be directed to the old or unreachable server.
AAAA → Correct IPv6 address, if used
If you do not use IPv6 on the new VPS, make sure an old AAAA record is not accidentally sending traffic somewhere it should not go.
Keep the Old Server Online
Do not immediately cancel the old VPS or hosting account after changing DNS.
DNS propagation takes time, and different networks can update their cached DNS information at different times.
Keeping the old server available during the transition gives you a safer fallback.
Monitor both servers during the migration window.
- Website accessibility
- Login pages
- Forms
- Images
- Database operations
- API connections
- SSL certificate
- Email sending
- Email receiving
Test the Website on the New VPS
After updating DNS, test the website from multiple networks and devices.
Check the main domain:
Then test:
Also test important pages and functions.
For an e-commerce website, test:
- Product pages
- Cart
- Checkout
- Payment flow
- Customer login
- Order creation
- Transaction emails
For a business website, test:
- Contact forms
- WhatsApp links
- Inquiry forms
- Email notifications
- Important landing pages
Do not only check whether the homepage opens. A migration can appear successful while individual services are still broken.
Test Email Separately
Website testing and email testing should be treated as two different checks.
Send a test email from an external account to your domain email address.
Then send an email from your domain email account to an external address.
Confirm:
- Incoming mail works
- Outgoing mail works
- Emails are not bouncing
- Email authentication is working
- Important mailboxes are receiving messages
If email stopped working immediately after a nameserver change, review the DNS zone first. Missing MX, SPF, DKIM, or other required records can cause problems.
Monitor DNS Propagation
DNS changes do not necessarily appear everywhere at exactly the same time.
Some users may reach the new VPS while others temporarily reach the old server because of DNS caching.
During this period, monitor your domain from different networks and DNS-checking services.
You are looking for consistent results such as:
If some locations still show the old IP shortly after the change, that does not automatically mean the migration failed.
Keep Monitoring After the Migration
Once most traffic is reaching the new VPS, continue monitoring the website and email.
Look for:
- Server errors
- Broken links
- Missing images
- Database errors
- Contact-form failures
- SSL warnings
- Email delivery problems
- Unexpected redirects
- Application errors
For websites that process transactions or user data, monitor especially carefully during the first part of the migration.
DNS Migration Final Checklist
Use this checklist before considering the migration complete.
Before Migration
During Migration
After Migration
Final Thoughts
A DNS migration is not simply a matter of replacing an old IP address with a new one. Your domain may be connected to several different services, and email is often the easiest one to overlook.
If you want to migrate a website to a VPS safely, prepare the new server first, document your existing DNS records, understand which records actually need to change, and treat email DNS separately from website DNS.
For many migrations, updating the website's A record while keeping the existing DNS provider and email records unchanged can be simpler than moving the entire DNS zone. If you do decide to change nameservers, make sure the new DNS provider has a complete copy of the records before making the switch.
A little preparation before changing DNS can prevent a much bigger problem afterward.
No comments:
Post a Comment
Your Post is Publishing