A domain, hosting account and mailbox subscription are three different services, even when one supplier sells them together. Before changing providers, establish who controls each account and which DNS records keep the website and email working. This prevents a routine website update from becoming a company-wide communications problem.

This guide covers domain ownership, DNS dependencies, hosting responsibilities and a controlled email or website handover. Discuss the relevant requirements through ITZ’s Domains, Hosting & Business Email service.

Domain selection and ownership

Choose a domain that reflects the business and its intended market. Where several domains are registered, select one primary website address and redirect alternatives consistently. Record the registered owner, administrator and renewal contacts.

Register the domain under the appropriate business ownership details and use a monitored renewal contact. TDRA explains that .ae registration is handled through accredited registrars or their resellers and that the registrant controls the name. Keep recovery access independent of a supplier's personal inbox. A domain invoice alone does not establish practical account access.

Hosting requirements

Assess platform compatibility, capacity, backup availability and support before selecting hosting. HTTPS protects data in transit; recovery also requires usable backups and a tested restoration process. Performance depends on the application and delivery configuration as well as hosting.

Ask what the hosting plan actually supports: the selected CMS, expected storage, backups, staging and the person responsible for updates. A basic information site and a customer portal have different operating requirements. Agree on a recovery process before moving data; a provider's statement that backups exist does not explain what can be restored or how.

Plan Your Domain and Email Setup to discuss domain ownership, DNS dependencies, hosting responsibilities and a controlled email or website handover.

Business email configuration

Use an email service suited to mailbox, collaboration and administration requirements. Review mail-routing and authentication records, including MX, SPF, DKIM and DMARC, with the selected provider. Test representative inbound and outbound messages.

Create a DNS inventory covering website addresses, mail routing, authentication and third-party verification. A nameserver change transfers responsibility for the whole DNS zone, not just the homepage. Export and review the current records first, then test mail delivery and key applications after the change. Keep confidential account data out of public handover documents.

Administration handover

Document domain, hosting and email accounts, DNS changes and recurring charges. Authorised business contacts should understand how access is managed, who approves changes and how services can be transferred if responsibilities change.

Prepare a responsibility register with the supplier, authorised administrator, renewal date and escalation route for each service. Include what happens when an employee leaves or the business changes support partners. Store passwords and recovery codes in the approved credential system, with the register pointing to that location rather than exposing secrets.

A practical example

Illustrative example: a trading company changes web hosting but keeps Microsoft 365. Moving the website address may be enough; replacing nameservers without recreating the mail records could interrupt email. The correct migration plan starts from the existing DNS dependencies, not the assumption that every service must move together.

Your review checklist

  • Confirm business access to the registrar and DNS account.
  • Identify the active website host and email provider separately.
  • Document a rollback route before changing nameservers or records.
  • Test public pages and representative inbound and outbound mail.

Frequently asked questions

Does moving a website require moving email?

Not necessarily. Review existing DNS and mail-provider dependencies before a website migration so that web changes do not interrupt email delivery.

References and further reading

Related services and guides

Discuss the next step

Plan Your Domain and Email Setup. Use the form below to discuss domain ownership, DNS dependencies, hosting responsibilities and a controlled email or website handover. Share the relevant goals and existing arrangements; do not include passwords, private records or access tokens.

Plan Your Domain and Email Setup ↗

Reviewed and expanded on 15 October 2026. Examples are illustrative; the appropriate approach depends on your business requirements and existing systems.