The DNS setup pages (Connect DNS's Go live step and the copy-by-hand step) marked any record that wasn't exactly the suggested value as different, in amber, with "often an old record that hasn't expired from caches yet", and never reached "All set". A DMARC with the domain's own report addresses, or an SPF with an extra include, is the admin's choice and valid.
DMARC and SPF are judged with coreState from #237: a single well-formed record of the domain's own is valid.
valid gets a green badge ("Your own record, valid"), counts toward the progress ring and "All set", and a note says it can stay; the suggested value is still shown for anyone who wants it.
The amber mark and caching note stay for records that really differ: two SPF records, a DMARC with no policy, MX or DKIM elsewhere.
Tests: src/features/dns/recordState.test.ts. Ran typecheck, lint, i18n:check, test (1119 passed), the three shell tests, build and notice-check locally.
Fixes #239. Follows #236/#237 (community t/321).
The DNS setup pages (Connect DNS's Go live step and the copy-by-hand step) marked any record that wasn't exactly the suggested value as different, in amber, with "often an old record that hasn't expired from caches yet", and never reached "All set". A DMARC with the domain's own report addresses, or an SPF with an extra include, is the admin's choice and valid.
- DMARC and SPF are judged with `coreState` from #237: a single well-formed record of the domain's own is `valid`.
- `valid` gets a green badge ("Your own record, valid"), counts toward the progress ring and "All set", and a note says it can stay; the suggested value is still shown for anyone who wants it.
- The amber mark and caching note stay for records that really differ: two SPF records, a DMARC with no policy, MX or DKIM elsewhere.
Tests: `src/features/dns/recordState.test.ts`. Ran typecheck, lint, i18n:check, test (1119 passed), the three shell tests, build and notice-check locally.
The DNS setup pages marked every published record that wasn't exactly
the suggested one as different, in amber, with a note about old records
in caches, and never reached "All set". A DMARC with the domain's own
report addresses, or an SPF with an extra include, is neither: the
admin chose it and it's valid.
The pages now judge DMARC and SPF with coreState from #237. A single
well-formed record of the domain's own gets a green badge ("Your own
record, valid"), counts toward the progress and "All set", and a note
says it can stay. The amber mark and its caching note stay for records
that really differ: two SPF records, a DMARC with no policy, an MX or
DKIM key elsewhere.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Fixes #239. Follows #236/#237 (community t/321).
The DNS setup pages (Connect DNS's Go live step and the copy-by-hand step) marked any record that wasn't exactly the suggested value as different, in amber, with "often an old record that hasn't expired from caches yet", and never reached "All set". A DMARC with the domain's own report addresses, or an SPF with an extra include, is the admin's choice and valid.
coreStatefrom #237: a single well-formed record of the domain's own isvalid.validgets a green badge ("Your own record, valid"), counts toward the progress ring and "All set", and a note says it can stay; the suggested value is still shown for anyone who wants it.Tests:
src/features/dns/recordState.test.ts. Ran typecheck, lint, i18n:check, test (1119 passed), the three shell tests, build and notice-check locally.