{"id":"69cc59f04999c6cf141a53d7","title":"2026 04 01 Mx Records","path":"how-to/committee/release-notes/2026-04-01-mx-records","contentMarkdown":"# 01-Apr-2026 — add MX record management for subdomain email routing([#207](https://github.com/nbarrett/ngx-ramblers/issues/207))\n\n## [build 573](https://github.com/nbarrett/ngx-ramblers/actions/runs/23868774282) — [commit # 4549a14](https://github.com/nbarrett/ngx-ramblers/commit/4549a142dff928cd8522e2e6c8d7966cd50d81bb)\n_____\n\n## What's New\n\n### MX Record Status on Mail Settings Page\n\nThe **Senders** tab on the Mail Settings page (`/admin/mail-settings?tab=senders`)\nnow includes an **MX Records** section that shows:\n\n- Whether the required Cloudflare MX records are configured for your environment's domain\n- A status table listing each required mail server with a check or cross indicator\n- An **Add Missing MX Records** button that appears when records are missing,\n allowing you to fix the configuration with a single click\n\nThis makes it easy for site administrators to diagnose and resolve email delivery\nissues without needing direct access to Cloudflare.\n\n### Automatic MX Records for New Environments\n\nWhen a new environment is provisioned via the environment setup workflow, the\nrequired MX records are now created automatically alongside the existing A and\nAAAA DNS records. This prevents the email routing gap that previously affected\nall new subdomain deployments.\n\n### Background\n\nEmails sent to `*.ngx-ramblers.org.uk` subdomain addresses were bouncing with\nerror `5.4.0 (network or routing status)` because no MX records existed to tell\nsending mail servers where to deliver email. The root domain and all custom\ndomains (e.g. `ekwg.co.uk`) had correct MX records, but subdomains like\n`kent.ngx-ramblers.org.uk` were missing them entirely.\n\nThe three required MX records point to Cloudflare's email routing servers:\n- `route1.mx.cloudflare.net` (priority 16)\n- `route2.mx.cloudflare.net` (priority 99)\n- `route3.mx.cloudflare.net` (priority 2)\n\n---\n\n## Technical Details\n\n### Server-side changes\n\n- **`server/lib/cloudflare/cloudflare.model.ts`** — Added `priority` field to\n `DnsRecord` and `DnsRecordResult` interfaces. Added `MxRecordDetail` and\n `MxRecordStatus` interfaces for the status API response.\n\n- **`server/lib/cloudflare/cloudflare-dns.ts`** — Updated `createDnsRecord()` to\n conditionally include `priority` in the Cloudflare API POST body when present\n (required for MX record creation).\n\n- **`server/lib/cloudflare/cloudflare-email-routing-routes.ts`** — Added two new\n authenticated API endpoints:\n - `GET /api/cloudflare/email-routing/mx-records` — returns MX record status\n for the current environment's subdomain\n - `POST /api/cloudflare/email-routing/mx-records` — creates any missing MX\n records and returns updated status\n\n- **`server/lib/cli/commands/subdomain.ts`** — Updated\n `setupSubdomainForEnvironment()` to create MX records after A/AAAA records,\n with duplicate detection matching the existing pattern.\n\n### Client-side changes\n\n- **`projects/ngx-ramblers/src/app/models/cloudflare-email-routing.model.ts`** —\n Added `MxRecordStatus`, `MxRecordDetail`, and `MxExistingRecord` interfaces.\n\n- **`projects/ngx-ramblers/src/app/services/cloudflare/cloudflare-email-routing.service.ts`** —\n Added `queryMxRecordStatus()` and `createMissingMxRecords()` service methods.\n\n- **`projects/ngx-ramblers/src/app/pages/admin/system-settings/mail/mail-senders-list.ts`** —\n Added MX record status section to the template with status badge, record table,\n error display, and create button. Added `loadMxRecordStatus()` and\n `createMissingMxRecords()` component methods.","contentHtml":"

01-Apr-2026 — add MX record management for subdomain email routing(#207)

\n

build 573 — commit # 4549a14

\n
\n

What's New

\n

MX Record Status on Mail Settings Page

\n

The Senders tab on the Mail Settings page (/admin/mail-settings?tab=senders)\nnow includes an MX Records section that shows:

\n\n

This makes it easy for site administrators to diagnose and resolve email delivery\nissues without needing direct access to Cloudflare.

\n

Automatic MX Records for New Environments

\n

When a new environment is provisioned via the environment setup workflow, the\nrequired MX records are now created automatically alongside the existing A and\nAAAA DNS records. This prevents the email routing gap that previously affected\nall new subdomain deployments.

\n

Background

\n

Emails sent to *.ngx-ramblers.org.uk subdomain addresses were bouncing with\nerror 5.4.0 (network or routing status) because no MX records existed to tell\nsending mail servers where to deliver email. The root domain and all custom\ndomains (e.g. ekwg.co.uk) had correct MX records, but subdomains like\nkent.ngx-ramblers.org.uk were missing them entirely.

\n

The three required MX records point to Cloudflare's email routing servers:

\n\n
\n

Technical Details

\n

Server-side changes

\n\n

Client-side changes

\n\n"}