DNS setup: tell a domain's own valid DMARC or SPF apart from a stale record #239

Closed
opened 2026-11-18 16:16:11 +00:00 by jcoffey-dev · 2 comments
Owner

Follows #236.

The DNS setup pages (ConnectDnsPage, CopyStep) mark every published record that isn't exactly the suggested one as different, in amber, with: "often an old record that hasn't expired from caches yet". A domain's own DMARC with its own report addresses, or an SPF with an extra include, is neither old nor cached. It's what the admin chose, and it's valid. Because it never counts as live, the page also never reaches "All set".

Showing the difference is right: someone may want to adopt the suggested value. But the wording and the progress shouldn't treat a valid record of the domain's own as unfinished.

Fix: use coreState from #237 (src/features/hovercards/facts.ts) for DMARC and SPF. For a valid record, show a separate mark ("your own record, valid"), count it toward "All set", and keep the amber mark and its caching note for records that really differ.

Follows #236. The DNS setup pages (`ConnectDnsPage`, `CopyStep`) mark every published record that isn't exactly the suggested one as `different`, in amber, with: "often an old record that hasn't expired from caches yet". A domain's own DMARC with its own report addresses, or an SPF with an extra include, is neither old nor cached. It's what the admin chose, and it's valid. Because it never counts as live, the page also never reaches "All set". Showing the difference is right: someone may want to adopt the suggested value. But the wording and the progress shouldn't treat a valid record of the domain's own as unfinished. **Fix:** use `coreState` from #237 (`src/features/hovercards/facts.ts`) for DMARC and SPF. For a `valid` record, show a separate mark ("your own record, valid"), count it toward "All set", and keep the amber mark and its caching note for records that really differ.
jcoffey-dev added this to the 27.1 milestone 2026-11-18 16:16:11 +00:00
jcoffey-dev added the enhancement
priority
p3
labels 2026-11-18 16:16:11 +00:00
jcoffey-dev self-assigned this 2026-11-18 16:16:11 +00:00
Author
Owner

Fixed in #240, the DNS setup side of #236 (community t/321).

On Connect DNS and the copy-by-hand step, a single well-formed DMARC or SPF of the domain's own now gets a green badge, "Your own record, valid". It counts toward the progress and "All set", and a note says it can stay. The suggested value is still shown if you'd rather use it. The amber mark and its caching note are now only for records that really differ: two SPF records, a DMARC with no policy, or an MX or DKIM key pointing elsewhere.

It ships in the next console release candidate.

Fixed in #240, the DNS setup side of #236 (community t/321). On Connect DNS and the copy-by-hand step, a single well-formed DMARC or SPF of the domain's own now gets a green badge, "Your own record, valid". It counts toward the progress and "All set", and a note says it can stay. The suggested value is still shown if you'd rather use it. The amber mark and its caching note are now only for records that really differ: two SPF records, a DMARC with no policy, or an MX or DKIM key pointing elsewhere. It ships in the next console release candidate.
Author
Owner

This is also in v2026.10.26.9 for the 2026 series (#241), so :latest has it now.

This is also in [v2026.10.26.9](https://git.coffeylabs.org/inbuxa/inbuxa-admin/releases/tag/v2026.10.26.9) for the 2026 series (#241), so `:latest` has it now.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: inbuxa/inbuxa-admin#239