Website Maintenance & Hosting

Website Migration: Protect Email and Other DNS-Connected Services

Inventory DNS records before moving hosting or nameservers. Keep email, verification and external services in the migration plan.

Wikimedia Servers-0001 42
Illustrative photograph, not a NithuDev project or team photo. Wikimedia Servers-0001 42 by Helpameout, via Wikimedia Commons · CC BY-SA 3.0. Resized and cropped; photograph retains the linked licence.
In this guide
  1. Map the services first
  2. Plan the transition deliberately
  3. Use a complete test
  4. Keep ownership clear

The new website loads, but business email stops arriving. A hosting move can affect more than web traffic when DNS or nameserver changes are made without a complete record inventory.

Map the services first

Identify the website, mail service and relevant verification records. Record the current DNS provider and who can authorise changes. Do not assume the new host automatically knows every record that exists at the old provider.

Plan the transition deliberately

Review the new provider's instructions and the intended final arrangement. Preserve necessary records and coordinate changes with people responsible for email and other services. Do not remove unfamiliar records simply because they do not point to the website.

  • Save the existing record inventory securely.
  • Confirm the actual mail provider and required records.
  • Review domain authentication configuration.
  • Plan validation and a recovery route.
  • Verify both website and email after the change.

Use a complete test

An authorised test can check public website access and email delivery through designated accounts. Record what was verified and whether any DNS changes are still propagating. Avoid claiming that a homepage response proves the mail system is healthy.

Keep ownership clear

The registrar, DNS provider, web host and email provider can be different organisations. Document that separation in the handover. A controlled migration preserves the business's services, not merely the visible pages.

Need help putting this into practice?

Tell Nithu what your website needs and which systems are involved. The next step is a review of the requirements and an agreed scope, with any paid tools or ongoing costs explained before work.

Discuss website maintenance

Further reading from the official documentation