GithubBackup/cloudflare_temp_email
1
0
Fork 0
mirror of https://github.com/dreamhunter2333/cloudflare_temp_email.git synced 2026-09-05 23:47:50 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs: clarify wildcard MX requirement for random subdomain (#1036)

Browse Source 
Random subdomain mailbox creation only generates addresses; mail delivery
depends on DNS / Cloudflare Email Routing covering *.<base-domain>.
Cloudflare Email Routing does not inherit apex configuration onto
subdomains, so a wildcard `*` MX record on the base domain is required
for random subdomains to actually receive mail.

- Add `[!IMPORTANT]` block in subdomain.md (zh/en) explaining the two
  deliverable paths: DNS-only wildcard MX (recommended for random
  subdomains) vs Cloudflare dashboard "Add subdomain"
- Link to Cloudflare Email Routing — Subdomains official docs from
  worker-vars.md and subdomain.md
- Instruct copying apex MX records to host `*` preserving each record's
  priority/target, instead of hardcoding specific MX targets
- Shorten frontend `randomSubdomainTip` for CreateAccount and Login
  views (6 locales: zh/en/de/es/ja/pt-BR), drop Markdown backticks
  (Vue text interpolation renders them literally), and point users to
  the docs instead of embedding DNS instructions
- Trim overlap between existing `[!NOTE]` and new `[!IMPORTANT]` in
  subdomain.md
- Update CHANGELOG.md / CHANGELOG_EN.md under v1.9.0(main)

Closes #1035
Closes #1026

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
This commit is contained in:
Dream Hunter
2026-05-14 15:09:32 +08:00
committed by GitHub
co-authored by Claude Opus 4.7
parent 74c8e8f7e4
commit 8324b133fb
11 changed files with 64 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files
vitepress-docs/docs/en/guide/feature/subdomain.md
+23 -2
View File
@@ -52,9 +52,30 @@ If you want to create an address under a specific subdomain such as `team.abc.co
>
> There is currently no backend switch that globally forces random subdomains; API calls that do
> not pass `enableRandomSubdomain: true` will not randomize automatically.
> [!IMPORTANT] A wildcard MX DNS record is required for random subdomains
> The worker only generates addresses like `name@<random>.abc.com` — **whether mail actually
> arrives depends entirely on DNS / Email Routing being configured for `*.abc.com`**, and
> Cloudflare Email Routing does **not** propagate the base-domain configuration onto subdomains.
> See Cloudflare's [Email Routing — Subdomains](https://developers.cloudflare.com/email-routing/setup/subdomains/)
> documentation.
>
> It does not automatically create Cloudflare-side subdomain mail routes or DNS records for you,
> so make sure the base-domain/subdomain routing is already available first.
> There are two ways to make `*.abc.com` deliverable:
>
> 1. **DNS-only wildcard MX (simplest workaround)** — In your DNS, copy **every existing MX
> record on `abc.com`** to host `*`, preserving each record's **priority and target value**.
> This makes `*.abc.com` resolve to the same MX targets as the apex, so mail flows into the
> same Cloudflare Email Routing zone and is picked up by the apex Catch-all rule that points
> at the Worker. No extra Cloudflare-side action is needed.
> 2. **Cloudflare dashboard "Add subdomain"** — Add the specific subdomain in the Email Routing
> dashboard and configure its DNS + Catch-all routing rule separately. This only covers the
> specific subdomain you add, so it is not suitable for arbitrary random subdomains.
>
> For random subdomain mailboxes, option **(1)** is the recommended path. Without it, the
> random subdomain feature will appear to work in the UI but inbound mail will never reach the
> Worker.
>
> Reference issue: [#1035](https://github.com/dreamhunter2333/cloudflare_temp_email/issues/1035)
## Let APIs Specify Subdomains Directly