Editorial guide · Updated September 2026 · Review current provider documentation before purchasing.
Understand DNS records, propagation and email precautions during a hosting move. The guidance below explains what to inspect and how to verify the details for your own website.
Identify current records
Export or record A, AAAA, CNAME, MX, TXT and other relevant records before editing anything.
Keep email separate
Changing nameservers can remove mail records unless you recreate them. Confirm mail routing before the cutover.
Understand propagation
Resolvers cache records according to TTL and other behavior; changes may not appear everywhere immediately.
Check HTTPS and redirects
Verify the new origin certificate and preferred hostname before directing all visitors to it.
Monitor after cutover
Check both www and apex hostnames, email, forms and analytics, and retain rollback information.
Check the current plans and terms directly. We may earn a commission if you buy through our link, at no additional cost to you.
See WPX plans ↗Know which records you are changing
A website move may require an A, AAAA or CNAME change; it does not automatically require changing nameservers. Export the current zone before editing. Preserve MX, SPF, DKIM and DMARC records if email is hosted elsewhere. Record the old and new values so you can reverse a mistaken change.
Verify the transition
Check the authoritative DNS response and compare it with several public resolvers. Caches may continue returning an older address until their TTL expires. Test the site using HTTPS and the intended hostname, including www behavior. Do not cancel the previous host solely because your own laptop already resolves to the new server.
Your practical evaluation worksheet
Use this worksheet while researching dns changes when moving wordpress. It is designed to turn a general hosting question into a decision you can verify for your own website, rather than relying on a generic rating or an unsupported promise.
- Define the outcome: write down the specific problem or decision that brought you to dns changes when moving wordpress, and identify one measurable sign of improvement.
- Collect a baseline: record your current provider, plan, billing term, site count, storage, audience location and any recent performance or reliability issues.
- Separate essentials from extras: identify the features your website cannot operate without, and do not count a feature until its limits and responsibilities are clear.
- Verify current documentation: consult the provider’s official plan page, knowledge base and contract for every detail that could affect the purchase.
- Test a representative journey: check a public page and any important form, login, membership or checkout flow before committing to a migration.
- Keep an exit plan: retain an independent backup, confirm how to export your data and note the renewal or cancellation date.
If you cannot answer a critical question from the published documentation, ask the provider in writing. The right decision is the one whose limits and responsibilities you understand before moving a live site.