How to Change DNS Safely When Moving a Joomla Website
Prepare the destination before changing DNS
Finish copying Joomla files and database, update destination configuration.php, configure HTTPS, and test the new server before public DNS changes. Use a hosts-file override, provider preview, or temporary hostname when possible. Do not use the DNS cutover itself as the first test of whether the migrated Joomla site works.
Inventory every DNS record that matters
Record the current A, AAAA, CNAME, MX, TXT, CAA, and other service records before editing the zone. A Joomla move may require changing only the web records. Preserve mail, verification, SPF/DKIM/DMARC, subdomain, and third-party service records unless those services are intentionally moving too.
Plan for DNS caching
Resolvers and clients can cache existing records according to TTL and their own behavior. If your DNS provider permits it, lower the relevant TTL ahead of a planned migration, then allow time for the old value to age out before the cutover. Raising the TTL again can wait until the destination is stable.
Keep old and new servers consistent during transition
During DNS propagation, some visitors can reach the old server while others reach the new one. For sites that accept registrations, orders, form submissions, or content changes, use a maintenance window, final synchronization, shared backend, or another deliberate consistency strategy. Avoid allowing independent writes that cannot be reconciled.
Change only the required web records
Update the records that direct the website hostname to the new destination. Confirm both apex and www behavior if both are used, and account for IPv6 when an AAAA record exists. Verify the new server has a valid TLS certificate for every hostname visitors may use.
Verify DNS and Joomla from multiple viewpoints
Check authoritative DNS and several public resolvers, then request the site over HTTPS. Test frontend, Administrator, SEF URLs, media, forms, login, email, scheduled tasks, APIs, and integrations. Review the new server's access/error logs to confirm real traffic is arriving there.
Retain a rollback window and finish cleanup deliberately
Keep the old server available until the migration is accepted and DNS caches have substantially expired. If rollback is necessary, understand that DNS caching also affects the reverse change. Once stable, raise TTLs as appropriate, create a fresh destination backup, update monitoring, and securely retire the old site copy.
Need More Help with Joomla?
Still having trouble? Open a support ticket with QuantaCade Support and we'll be happy to help where we can.
Support priority is given to QuantaCade products, services, and customers. However, we're also happy to assist fellow Joomla users with general Joomla questions and troubleshooting when possible.
QuantaCade is an independent Joomla extension developer and is not official Joomla support. Some issues involving third-party extensions, hosting environments, server configurations, or other systems outside our development control may be beyond what we're able to resolve.