Quick answer
Why is email not arriving at my custom domain?
Email stops reaching a custom domain when its MX records are missing, wrong or mixed with an old provider's, when a DNS change has not spread yet, or when the domain has expired. Postelva counts eight common causes below; the first check is always the MX records, which usually need up to 24 hours to settle.
Eight causes of missing email, with the fix
| Symptom | Likely cause | How to check | Fix |
|---|---|---|---|
| Nothing arrives, no bounce | MX records missing or still on the old provider | Look up the MX records of the domain | Add the MX records of the new provider and remove the old ones |
| Some mail arrives, some does not | Old and new MX records mixed | The MX list shows hosts of two providers | Keep only the new provider's MX, or give them the lowest priority numbers |
| It worked yesterday, not today | DNS change not spread yet | Different resolvers answer differently | Wait for the old TTL to expire; typical MX changes take 1 to 4 hours, up to 24 to 48 hours |
| Bounce says the domain does not exist | Domain expired or suspended | Look up the domain status at the registry | Renew; see what happens to email when a domain expires |
| A record exists but the lookup says it does not | Negative caching of the earlier empty answer | Same record found by one resolver, not another | Wait: an empty answer is cached with the TTL of the zone's SOA record |
| Mail from your domain goes to spam | Two SPF records, or more than 10 DNS lookups | Count the TXT records starting with v=spf1 | Merge into one SPF record; keep it under 10 lookups |
| Provider says the domain is not verified | Verification TXT record missing or copied wrongly | Compare the value with the provider's screen | Paste the value again; some DNS hosts want the host name without the domain |
| Mail bounces after you tightened DMARC | Policy set to reject before SPF and DKIM passed | Read the aggregate reports | Go back to p=none, fix the senders, then tighten again |
What should I check first?
Check the MX records first, because they decide where every message for the domain is delivered. An MX record names a mail server and a priority; senders try the lowest number first. If the list is empty, mail has nowhere to go. If it names the old provider, mail keeps arriving there.
Two commands show the answer. Replace yourname.com with your domain.
dig MX yourname.com +short
nslookup -type=MX yourname.comWhat should the MX answer look like?
It should list only the hosts of your current provider. The expected answer for Proton Mail is two lines: mail.protonmail.ch at priority 10 and mailsec.protonmail.ch at priority 20. For Fastmail it is in1-smtp.messagingengine.com at 10 and in2-smtp.messagingengine.com at 20. The method for reading every record is in how to check MX, SPF, DKIM and DMARC records.
Why does mail still go to my old provider?
Because the old MX records are still in the zone, or because resolvers still hold them in cache. According to Postelva's index of 12 November 2026, three of the providers with documented MX setups, Proton Mail, Mailbox.org and Fastmail, tell you to remove the MX records that point elsewhere or to give the new ones the lowest priority number. Leaving both sets in place sends mail to either server unpredictably.
The time a change needs is about the old TTL on the record at the moment you changed it. A TTL of 3600 seconds means up to an hour of cached answers; a TTL of 86400 means up to a day. Proton Mail says to allow up to a day for MX changes, and Mailbox.org says synchronisation of its verification record can take up to 48 hours. If you are planning a move rather than repairing one, move email to a new provider without losing mail explains how to lower the TTL beforehand.
Can an expired domain stop my email?
Yes: once the domain is past expiry and its DNS stops resolving, incoming mail bounces or is lost. ICANN's Expired Registration Recovery Policy lets the owner renew from the day of expiry. After deletion, gTLD registries offer a 30-day redemption period during which DNS resolution is disabled, transfers are blocked and the registrar can restore the name for an extra fee. The exact day DNS stops varies by registrar.
A second, less known trigger is the registrant email. ICANN requires the registrar to verify it within 15 days of registration, transfer or change of registrant, and a domain whose owner never answers can be suspended. Postelva states it plainly: the registrant email is verified after registration, as ICANN rules require (within 15 days). Answer the verification mail and switch on automatic renewal, which here is automatic renewal from your balance, switched on or off for each domain. The full timeline is in what happens to email when a domain expires.
Can SPF, DKIM or DMARC make mail disappear?
They affect mail you send much more than mail you receive, but a strict DMARC policy can make receivers reject your messages outright. A domain may publish only one SPF record: a second record, or an SPF record that needs more than 10 DNS lookups (RFC 7208), returns a permanent error and receivers treat the check as failed. Add the new provider's include to the existing record instead of creating a new one.
For DMARC, start at p=none with a report address, confirm SPF and DKIM pass on all legitimate mail, then move to quarantine and finally reject. Mailbox.org warns that a strict policy set too early can bounce legitimate mail. The records are explained in how to create an SPF record.
Where does Postelva fit in this?
Postelva hosts the DNS of the domain, so every record in this guide is edited in the client area. The DNS includes free DNS hosting with A, AAAA, CNAME, ALIAS, MX, TXT, NS, SRV and CAA records, DNSSEC, and your own nameservers if you prefer (2 to 13). One-click templates cover Proton Mail, Fastmail and Zoho Mail; for Tuta, Mailbox.org, iCloud+ and Migadu the records are typed in the DNS editor. If a template and a hand-typed record disagree, the zone shows both, so read the full list before you wait for propagation. Support replies by email: email replies within 12 hours, 7 days a week, including help with MX, SPF, DKIM and DMARC records.
Missing email: questions
How long should I wait before assuming a DNS change failed?
Allow up to the old TTL of the record, then check from a second resolver. MX changes typically take 1 to 4 hours and can take 24 to 48 hours.
Why do some senders reach me and others do not?
Each sender's resolver caches your old records for a different time, so during a change some deliver to the new server and some to the old. Removing the old MX records ends the split.
Does a catch-all affect delivery?
Only inside the mailbox: a catch-all accepts names you did not create. If a named address is missing, check that the alias exists and that the catch-all of another account is not taking the mail.
Can the provider block my domain?
A provider can refuse a domain that is not verified. Check the verification TXT record and the status screen of the provider before you look further.
What if my domain shows as expired?
Renew it at once from the client area. During the redemption period the registrar can still restore it, at an extra fee that must be published.
In summary
- Check the MX records first: they decide where mail is delivered.
- Remove old MX records or give the new ones the lowest priority number.
- MX changes take about the old TTL: 1 to 4 hours typically, up to 48 hours.
- One SPF record only, under 10 DNS lookups (RFC 7208).
- An expired domain stops resolving; the redemption period lasts 30 days.
- ICANN requires the registrant email to be verified within 15 days.
- Tighten DMARC from p=none, never straight to reject.
Sources (8)
- RFC 7208, section 4.6.4: limits on DNS lookups — RFC Editor (read 2026-11-12)
- RFC 2308: negative caching of DNS queries — RFC Editor (read 2026-11-12)
- Expired Registration Recovery Policy — ICANN (read 2026-11-12)
- 2013 Registrar Accreditation Agreement — ICANN (read 2026-11-12)
- Custom domain from Namecheap (MX values) — Proton (read 2026-11-12)
- Default DNS records — Fastmail (read 2026-11-12)
- mailbox.org KB: SPF, DKIM and DMARC — mailbox.org (read 2026-11-12)
- How long does it take for DNS changes to propagate — Suped (read 2026-11-12)