Custom Domain Email: Plan DNS, Addresses, and Ownership
Plan custom domain email with clear ownership, intentional addresses, staged DNS changes, independent sending checks, and a practical mailbox migration record.
Read the articlePrivacy & domains / Field guide
Domain Virtual Email Box
Once domain ownership is clear, the next job is operating useful addresses beneath it. Decide which addresses need their own storage, which can route into an existing mailbox, and who is responsible for reading each stream. Then prepare recipients before changing delivery routes. This page concentrates on the practical administration of mailboxes and addresses, using example.com as a fictional domain for planning rather than a live service to contact or a configuration to copy.
Make an address inventory
List each intended address alongside its purpose, reader, reply identity, and destination mailbox. For example, [email protected] may serve general enquiries while [email protected] serves active client work. Decide whether they require different permissions before creating separate storage. Include aliases and automated notification destinations in the same inventory. The inventory should answer who notices a message and who may respond. It also becomes the checklist for a later migration, so addresses do not disappear simply because they were less frequently used.
Prepare recipients and routing
Create the required accounts and routing rules at the intended destination before moving live delivery. RFC 5321's mail routing rules use DNS MX records to locate receiving servers; those records do not create individual recipient accounts. Keep the current routing values available and change only the records required by your plan. For an existing setup, decide how long both stores will be inspected during transition and who will investigate any mail that appears in an unexpected place.
Test identity and history separately
Send a harmless external test to every intended address, then reply from the identity its reader is supposed to use. Inspect the visible sender, reply destination, and sent-copy location. Record failures before making the address widely public. If moving from another mailbox service, inventory older messages, local folders, and saved attachments as a separate migration task. A routing change can direct new delivery while leaving the historical archive where it was, so completion criteria must cover both workstreams.
Go deeper / Virtual Email Box Lab
Put the idea to work.
Detailed examples and practical tradeoffs for the decisions behind this guide.