Before you change WordPress DNS records, it is worth checking a few technical details to avoid downtime, broken email delivery, or a situation where your site points to the new hosting platform but visitors still see the old one. DNS changes are often simple in the control panel, but the effects depend on the current records, the hosting setup, and how your WordPress site is configured.
If you are moving a WordPress site to a new hosting account, using Plesk, or preparing a launch after migration, the safest approach is to verify the domain, current DNS zone, nameservers, and WordPress settings before you make any changes. This is especially important in Europe, where DNS propagation may be fast in some networks and slower in others, and where you may also need to consider regional email or compliance requirements.
What DNS records control WordPress traffic
WordPress itself does not depend on a single DNS record. In most cases, the records that matter are the ones that direct the domain to your hosting service and the ones that keep email working correctly.
A and AAAA records
An A record points a hostname, usually the root domain, to an IPv4 address. An AAAA record points to an IPv6 address. If your WordPress site is moving to a new server, these records often need to be updated so the domain resolves to the new hosting environment.
CNAME records
A CNAME record points one hostname to another hostname. It is commonly used for www, for example when www.example.com should follow example.com. In a WordPress migration, it is important to verify whether www is a CNAME, an A record, or redirected elsewhere.
MX and mail-related records
MX records determine where email is delivered. If you change DNS without checking them, your website may work but email may stop arriving. Also review TXT records used for SPF, DKIM, and DMARC, especially if your hosting platform provides mail services or if you use an external email provider.
TXT, SRV, and other service records
Depending on the setup, your domain may also use TXT records for domain verification or security, and SRV records for specific services. These are not always directly related to WordPress, but they can be affected if you replace the entire DNS zone during migration.
Check the current DNS setup before changing anything
Before editing records in your control panel, make a complete inventory of the current DNS zone. This helps you avoid deleting something that is not obvious at first glance.
- Identify the current nameservers for the domain.
- Export or copy the existing DNS zone if your provider allows it.
- List all A, AAAA, CNAME, MX, TXT, and other records.
- Check which records are used by the website and which are used by email or third-party tools.
- Note any custom records for subdomains such as shop, staging, or mail.
If you are using Plesk, you can usually review DNS records in the domain’s DNS settings. On managed hosting platforms, DNS may be separated from the web hosting service, so make sure you know where DNS is actually managed before editing anything.
Confirm where the authoritative DNS is hosted
One of the most common mistakes is editing records in a DNS zone that is not active for the domain. Check the domain registrar and confirm the authoritative nameservers. If the nameservers still point to your old provider, changing records in a new control panel will have no effect.
In a migration scenario, you may either:
- keep DNS at the registrar and update only the A or CNAME records, or
- move the entire DNS zone to the new hosting platform and update nameservers.
Both approaches can work, but they require different checks.
Verify the new hosting account before updating records
Make sure the target hosting environment is ready before you change DNS. The domain should resolve to a server where WordPress can actually respond.
Check the destination IP address
Confirm the IPv4 and, if needed, IPv6 addresses of the new hosting account. In Plesk or another control panel, verify that the domain is added to the correct subscription or site and that the web server is listening on the expected IP.
Confirm the document root and WordPress files
Check that the WordPress files are in the correct document root and that the site will load from the domain you plan to point. A DNS change will not fix an incorrect file path, a missing index.php, or a site that was imported to the wrong directory.
Test the site before switching DNS
Use a temporary URL, hosts file override, preview link, or server-level test domain if available. This allows you to confirm that the migrated WordPress site works before visitors start using the new DNS destination.
- Homepage loads correctly.
- Admin login works.
- Permalinks resolve without 404 errors.
- Images, CSS, and JavaScript load from the correct domain.
- Forms, checkout, or membership features work as expected.
Check WordPress settings that can affect a DNS change
DNS changes are only one part of a WordPress migration. The application itself must also be aligned with the new domain or server.
Site URL and home URL
In WordPress, the site URL and home URL should match the domain you intend to use. If the site was cloned to a staging location or temporarily opened under another domain, verify these values before launch.
Search and replace for old domain references
If the site was moved from another host or domain, old URLs may still be stored in the database. This can cause mixed content, broken internal links, and missing images after DNS propagation.
Check for references to:
- the old domain name;
- the old www or non-www version;
- temporary staging URLs;
- old HTTP links if you are now using HTTPS.
SSL certificate readiness
Before switching DNS, make sure an SSL certificate is issued or ready to issue for the domain. If the new hosting platform uses automatic certificate provisioning, confirm that the domain already resolves correctly on the new server or that the provider supports validation during the transition.
If the certificate is not ready, visitors may see browser warnings once the DNS record points to the new server.
Review email records separately from web records
When people change WordPress DNS records, they often focus only on the website and forget about email. That can cause serious disruptions.
Keep MX records if email stays elsewhere
If your email is hosted by Microsoft 365, Google Workspace, or another external provider, preserve the existing MX records and related TXT records. Only update the web records needed for the WordPress site.
Check SPF, DKIM, and DMARC
These records help protect mail delivery and domain reputation. If the DNS zone is recreated during migration, copy them carefully. If they are missing, outbound messages may land in spam or be rejected.
Verify mail subdomains and service hostnames
Some setups use mail.example.com, autodiscover, or other service hostnames. Make sure they continue to resolve correctly if users depend on them.
Lower the TTL before making the switch
If possible, reduce the TTL for the records you plan to change before the actual DNS update. TTL controls how long resolvers cache the old value.
Lowering TTL ahead of time can help the new address spread faster once you change the record. Common values are 300 seconds or 600 seconds, but the best value depends on the provider and your migration plan.
- Lower TTL 24 to 48 hours before the change if possible.
- Change only the necessary records, not the whole zone.
- Do not lower TTL too late if you expect a quick cutover.
Remember that even with a low TTL, some networks may still cache records for longer than expected.
Choose between changing nameservers or only specific records
There are two common ways to update DNS for WordPress migrations.
Option 1: Update only A/CNAME records
This is usually the safest option when you want to keep DNS management at the current provider but point the site to a new server. You change the web records and leave mail and other services untouched.
This approach is often best when:
- email is already stable and should not change;
- you only need to move the website;
- the current DNS zone contains several custom records.
Option 2: Change nameservers
Switching nameservers moves DNS management to another provider, such as your hosting platform or a new registrar setup. This can be convenient, but it requires careful copying of every record, not just the web ones.
Use this method only if:
- you have recreated all required DNS records at the new provider;
- you understand which services depend on the zone;
- you have confirmed the new DNS zone is active and complete.
Practical pre-change checklist
Use this checklist before changing WordPress DNS records:
- Confirm the domain is registered and unlocked if needed.
- Check the current authoritative nameservers.
- Export or document the full DNS zone.
- Verify the destination server IP address.
- Make sure WordPress files are in the correct document root.
- Test the site on the new hosting account.
- Confirm the site URL and home URL.
- Check SSL certificate readiness.
- Review MX, SPF, DKIM, and DMARC records.
- Lower TTL for the records you plan to change.
- Prepare a rollback plan in case of an issue.
How to avoid downtime during the DNS switch
A well-planned DNS update should keep downtime to a minimum, but only if the old and new environments are both ready. The goal is to make sure that when DNS starts pointing to the new host, the new host can serve the live site immediately.
Keep the old hosting active during propagation
Do not cancel the old hosting account right away. Keep it active until the DNS change has fully settled and you are sure the new site works for visitors and crawlers.
Avoid making multiple changes at once
If you change DNS, update WordPress settings, move email, and switch SSL at the same time, troubleshooting becomes much harder. Make one controlled change at a time whenever possible.
Watch for cached content and propagation delays
Different users may see different results during propagation. Some may reach the new host, while others still resolve the old address. This is normal. Avoid editing the site heavily during the transition unless you are using a maintenance mode or content freeze.
Common mistakes to avoid
- Changing DNS before the new WordPress site is ready.
- Editing records at a provider that is not authoritative for the domain.
- Forgetting to copy MX or TXT records when moving DNS.
- Leaving old domain references inside the WordPress database.
- Pointing www to one server and the root domain to another by mistake.
- Not checking SSL before switching traffic.
- Assuming DNS changes are instant in every network.
What to check in Plesk or a similar control panel
If your hosting platform uses Plesk or a similar control panel, review these items before you update DNS:
- the domain is assigned to the correct subscription;
- the web hosting is enabled;
- the DNS zone contains the right A or CNAME records;
- mail service is configured as intended;
- the SSL certificate is available or can be issued;
- WordPress Toolkit or equivalent tools show the site in the expected location.
In managed hosting environments, DNS may be partially automated. Even so, it is still important to review the zone manually before and after changes.
FAQ
Should I change the A record or the nameservers for a WordPress migration?
If you only want to move the website, changing the A or CNAME record is often simpler and safer. Change nameservers only if you want the new provider to manage the entire DNS zone and you have copied every required record.
How long does DNS propagation take?
It depends on TTL values, caching, and the resolver used by each visitor or network. Some users may see the change within minutes, while others may take several hours or longer.
Will my email stop working if I change WordPress DNS records?
It can, if MX or mail-related TXT records are changed or removed. If email is hosted separately, keep those records unchanged.
Do I need to update WordPress after changing DNS?
Sometimes yes. If the domain changes, or if the site was tested under a temporary address, you may need to update the WordPress home and site URL values and run a search and replace for old links.
Can I switch DNS before copying the WordPress files?
No, not if you want to avoid downtime. The new server should already contain the migrated WordPress files, database, and SSL setup before traffic is pointed to it.
What if the site loads on some devices but not others after the change?
This is usually due to DNS caching or propagation. Check the authoritative records, wait for TTL to expire, and verify that both root and www versions are configured correctly.
Conclusion
Before changing WordPress DNS records, confirm the current DNS zone, the authoritative nameservers, the destination hosting setup, and all service records that should stay intact. In a WordPress migration or launch, the safest DNS change is the one made only after the new site is fully prepared, tested, and ready to receive traffic.
For most hosting environments, the best practice is to update only the records that need to change, keep email records separate, lower TTL in advance, and leave the old hosting active until propagation is complete. That approach reduces downtime and makes troubleshooting much easier if anything unexpected happens.