Blog
How to create an email address with your own domain
Reviewed by the Free Domain Mail editorial team · Updated
Creating hello@yourdomain.com requires a domain you control, a mailbox provider and carefully published DNS records. The safest process records the current configuration first, adds each provider-issued value at the authoritative DNS service and tests both directions before the new address becomes important.
Confirm the prerequisites
You need control of the domain, access to its authoritative DNS zone, a selected mailbox provider and an address that does not collide with a reserved or existing mailbox. The registrar, DNS provider, website host and email provider may all be different companies.
Review the provider’s sending and receiving limits, storage, retention, backup position, client access and support before changing DNS. If you only need inbound redirection, compare forwarding with a hosted mailbox first.
Find the authoritative DNS provider
Public NS records identify the service whose DNS changes are visible to the internet. If the nameservers point to Cloudflare, changes made in the registrar’s default DNS panel will do nothing; edit the Cloudflare zone instead.
Run an MX lookup before editing. Existing MX answers mean mail is already delivered somewhere, so replacing them without a migration plan can lose messages.
Create a safe pre-change record
Export the DNS zone or capture every existing record. Record current MX priorities and targets and the complete SPF value. Preserve website A, AAAA and CNAME records, unrelated verification TXT records and any DKIM selectors still used by active senders.
Define rollback before starting: know which values will be restored, who can restore them and how public DNS will be checked afterward. Lowering TTL in advance can shorten a planned migration, but it does not clear answers already cached under the previous TTL.
Publish records in dependency order
First add the provider-issued ownership TXT record. Next publish the complete MX set with the exact targets and priorities. Then update the single SPF policy so it contains every legitimate sender, publish the exact DKIM TXT or CNAME selectors supplied for this domain, and add DMARC at _dmarc.
Begin DMARC with monitoring when the sender inventory is not yet proven. Move toward quarantine or reject only after real messages from every legitimate service pass aligned SPF or DKIM. Never copy a verification token or DKIM key from a tutorial or another domain.
Understand the one-SPF rule
A hostname should have one SPF policy beginning with v=spf1. When several services send for the same domain, combine their authorized mechanisms into that record instead of publishing one SPF record per provider.
Keep the policy within SPF’s DNS-query limit and remove providers that no longer send. A syntactically valid SPF record can still be wrong if it omits a web form, support tool, billing system or transactional sender.
Verify DKIM and DMARC alignment
A DKIM selector is provider-specific and appears before ._domainkey. Confirm the record type and value in the provider dashboard, then inspect a real outgoing message to prove that the provider actually signs with that selector.
DMARC does not merely ask whether SPF or DKIM passed. At least one passing identifier must align with the domain visible in From. A third-party return path can pass SPF while still failing DMARC alignment.
Test the complete mail path
Query public DNS for TXT, MX, SPF, DKIM and DMARC. Send from an unrelated external mailbox to the new address, reply from the new mailbox, and send a new outbound message. Inspect Authentication-Results for SPF, DKIM and DMARC rather than trusting only a green dashboard indicator.
If verification fails, check the authoritative nameservers, host formatting, MX priority, duplicate SPF policies, the DKIM selector and the previous TTL. Different resolvers may temporarily return different answers during propagation.
Roll back without causing a second outage
Restore the recorded MX set if the new service cannot receive. If SPF was merged, remove only the newly added authorization rather than deleting the whole policy. DKIM records generally do not affect another provider unless that provider uses the same selector.
Re-query public DNS after rollback and send another external test. Keep the old mailbox available until the new route is stable and any important historical mail has been preserved.
Using the same process with Free Domain Mail
Free Domain Mail generates domain-specific ownership, MX, SPF, DKIM and DMARC values and checks them after publication. Once the domain passes verification, you can create browser mailboxes and test inbound and outbound delivery.
The beta currently permits up to three mailboxes, ten sends and twenty receives per verified domain per day. It does not provide attachments, IMAP, POP3, customer SMTP credentials or bulk sending, so use a full-featured provider when those are requirements.
Common mistakes to avoid
- Editing DNS at the registrar when another provider is authoritative.
- Adding a second SPF record instead of merging authorized senders.
- Deleting old MX records before the replacement is accepting mail.
- Guessing a DKIM selector from another account or tutorial.
- Starting DMARC at p=reject before verifying every legitimate sender.
- Testing only inbound or only outbound delivery.
Frequently asked questions
How long does DNS propagation take?
New answers may appear within minutes, but resolvers can retain the old answer until its previous TTL expires. A blanket 24–48 hour wait is not a substitute for checking the actual TTL and authoritative response.
Can I configure email without changing my website?
Yes. Preserve the A, AAAA and CNAME records used by the website and edit only the mail-related records required by the provider.
Does each mailbox need its own DKIM record?
Usually no. DKIM is normally configured for a sending domain or provider integration, not for every mailbox.
Can two mailbox providers use the same domain?
Multiple senders can sometimes share one SPF policy, but two independent inbound mailbox providers cannot both receive the same address merely by mixing MX records. Plan a deliberate migration or routing architecture.
Why does mail go to spam even after DNS passes?
Authentication is only one signal. Domain and IP reputation, recipient expectations, complaints, bounces and message content also influence placement.
Technical references
Primary specifications and provider documentation relevant to this guide: