DNS After A WordPress Migration

Plan DNS changes, TTLs, propagation, rollback, and post-cutover verification when moving WordPress.

Editorial Team • Updated September 25, 2026

What Matters

WordPress hosting decisions become clearer when you identify the actual constraint. A slow page, an overloaded PHP process, an unreliable migration, an email-routing mistake, and a recurring outage are different problems. Each needs different evidence before you change infrastructure.

For an existing site, capture a baseline: representative response times, important page types, traffic shape, storage growth, PHP version, critical plugins, scheduled jobs, email dependencies, DNS provider, and the recovery point you can tolerate. For a store or membership site, include logged-in and uncached flows rather than testing only a cached homepage.

How To Evaluate It

Hosting capacity is multi-dimensional. CPU affects computation, RAM supports processes and caching, PHP workers affect concurrent uncached PHP requests, storage affects local data, and bandwidth affects transfer. Caching and CDN delivery can reduce origin work, but neither automatically fixes inefficient PHP, database queries, or third-party calls.

Operational features matter too. Backups need a credible restore process. Staging needs realistic testing. Security is shared responsibility. Migration support has scope boundaries. Support quality should be judged by useful resolution and escalation, not merely a fast greeting.

Migration Sequence

Inventory dependencies, create a recoverable source backup, copy the site, test on a temporary or hosts-file address, verify application flows, plan DNS, cut over traffic, then re-test SSL, redirects, forms, analytics, email, scheduled jobs, and commerce callbacks. Keep the old environment available until the new one has passed a normal operating cycle.

WPX's current migration policy is WordPress-focused and includes exclusions. It states that malware is scanned during migration and may extend the timeline, and that email migration can be included when the necessary DNS information is supplied. Unsupported platforms and some special migration operations are excluded, so read the current policy for your setup.

DNS Controls Where Services Live

Nameservers delegate the zone; A and AAAA records point hosts to IP addresses; CNAMEs alias names; MX records route mail; TXT records commonly carry verification and email-authentication data. During a migration, change only the records you intend to change and preserve unrelated services.

Decision Checklist

• What problem or workload are you actually solving?
• Which requests bypass full-page cache?
• What CPU, RAM, PHP concurrency, storage, and transfer headroom do you need?
• How quickly must you restore after a failure?
• Which migration, DNS, email, security, and support tasks do you expect the host to handle?
• Have you verified current plan terms for the tier you would actually purchase?

Frequently Asked Questions

Should I Change Hosts As Soon As I See This Problem?

No. Diagnose first. A host change can help when infrastructure or service limitations are the constraint, but application problems can move with the site.

Does A CDN Fix Slow WordPress Hosting?

It can improve delivery and reduce origin work for cacheable content. It does not automatically fix slow PHP, database queries, external calls, or uncached application flows.

How Much Hosting Headroom Should I Keep?

Enough to absorb normal variation and predictable peaks without running continuously at the limit. The exact margin depends on how bursty and business-critical the workload is.

Why Do You Link To WPX?

We have substantial hands-on experience with WPX and it is the primary hosting service evaluated on this publication. Some WPX links are affiliate links, so we may earn a commission at no extra cost to you.