The short answer

You need three separate pieces: a domain you control, an email provider that hosts the mailbox, and DNS records that tell the internet where your mail belongs. Your website host does not have to host your email, and moving the email does not require moving the website.

Choose the email provider first. Then copy that provider’s current DNS values exactly. Do not copy record values from an article, because the correct values depend on the service and sometimes on your specific account.

Draw this ownership map before changing anything

Write down the answer to each question:

These may be five different answers. If you do not know where DNS is managed, check the nameservers shown in the domain account and ask the registrar or current technical helper. Do not guess by logging into the website dashboard and changing the first DNS screen you find.

Choose the address before you create the mailbox

For a one-person business, a named address such as marge@example.com makes personal conversations feel personal. You can add hello@example.com as an alias for general inquiries and route it into the same inbox.

Keep the first setup small:

• one named mailbox for the owner.
• one public general-contact alias.
• role addresses only when someone is responsible for them.
• a separate administrator identity when the provider recommends it.

Avoid using admin@ as the public contact address. It attracts automated attacks and mixes customer conversations with system administration.

Understand the DNS records without becoming a technician

Your provider will supply the exact records. It helps to know their jobs:

MX controls incoming routing. SPF, DKIM, and DMARC help receiving systems evaluate outgoing messages and impersonation. They are related, but one does not replace another.

Google’s sender guidelines require mail sent to Gmail accounts to use SPF or DKIM, with more authentication requirements for high-volume senders. That is one reason authentication should be part of initial setup, not something saved for a future marketing campaign.

Use a safe order of operations

1. Secure the domain and administrator accounts

Turn on multifactor authentication. Confirm the recovery email and phone. Save recovery codes somewhere protected outside the mailbox they recover. Make sure the domain’s renewal payment and notices go to an address you will still control if the new mailbox fails.

2. Create the mailbox at the new provider

Verify the domain as instructed, create the owner mailbox, and add only the necessary aliases. Note the provider’s administrator URL, support route, and recovery process.

3. Record the existing DNS before editing

Save a screenshot or export of the current DNS zone. Label records that support the website, old email, forms, verification services, and other tools. This gives you a reference if something stops working.

4. Add the provider’s records

Follow the provider’s own setup screen. If you are moving from an old provider, create every mailbox and alias before changing MX. Microsoft’s current domain instructions, for example, warn administrators to create users and mailboxes before updating MX so email can continue without interruption.

Do not delete website A, AAAA, or CNAME records merely because they are not on the email provider’s list. The list normally tells you what email needs, not everything the domain uses.

5. Wait only when a changed record requires it

DNS updates may take time according to their time-to-live and resolver caches. Do not spend that waiting period making unrelated changes. Recheck the exact record and use the provider’s verification tool.

6. Test the complete loop

From an outside Gmail account and an outside Microsoft account:

• send to the new domain address.
• reply from the domain address.
• check the visible From and Reply-To fields.
• verify that the reply arrives in the expected conversation.
• look in spam and save the original message headers.
• test aliases separately.
• test the phone and computer.

A green “domain verified” message does not prove that every direction, alias, and device works.

Keep the website and marketing senders in view

Your contact form, store, booking system, invoice app, and newsletter platform may send mail using the same domain. Add each legitimate sender to an inventory before enforcing DMARC. Use the authentication instructions supplied by that sender instead of giving it your mailbox password.

Create a simple register:

This becomes invaluable when a message fails six months later and you need to know which system actually sent it.

Protect the setup after launch

Keep renewal, administrator, DNS, and recovery details in a business-controlled record. Review access when a contractor leaves. Test the public address after any domain, website, or provider change.

The ICANN domain-security guidance recommends protecting the registrant account, using multifactor authentication where available, and keeping registration contact information current. Losing domain control can interrupt both the website and every address attached to it.

Sources and further reading

• Google: Email sender guidelines
• Microsoft: Connect a domain by adding DNS records
• ICANN: Domain-name registrant security and recovery

If you are building the email system around it

The Email Marketing System can help you connect your authenticated domain with subscriber forms, permission, sending, and ongoing email operations.

A free next step

Not sure which business fits you yet?

The free Freedom Path Assessment can help you compare your strengths, schedule, income goals, and preferred way of working before you commit to a business direction.

Take the Freedom Path Assessment Free

Related Questions

• How do I move business email to a new provider without losing mail or breaking delivery?
• Which business email provider should I choose: Google Workspace, Microsoft 365, or another option?
• When should a small business use aliases, shared inboxes, or separate mailboxes such as support@?
• How do I read and send my domain email from Gmail or Outlook?