The DNS guide switched on every record type except TLSA, so it published CAA for anyone who took the defaults. A CAA record covers every name under the domain and ties it to this server's ACME account, so another ACME client there is refused at its next renewal.
CAA is now off in the guide's defaults, and its switch carries a warning. A domain that already publishes CAA still loads with it on, because the guide reads the stored list.
The server's matching default change is in inbuxa/inbuxa-server#294. This PR works on its own, since the guide sends an explicit list.
Tested: new records.test.ts, plus typecheck, lint, i18n check, full npm test, notice check and build. I didn't click through the guide in a browser.
Part of inbuxa/inbuxa-server#292.
The DNS guide switched on every record type except TLSA, so it published CAA for anyone who took the defaults. A CAA record covers every name under the domain and ties it to this server's ACME account, so another ACME client there is refused at its next renewal.
CAA is now off in the guide's defaults, and its switch carries a warning. A domain that already publishes CAA still loads with it on, because the guide reads the stored list.
The server's matching default change is in inbuxa/inbuxa-server#294. This PR works on its own, since the guide sends an explicit list.
Tested: new `records.test.ts`, plus typecheck, lint, i18n check, full `npm test`, notice check and build. I didn't click through the guide in a browser.
A CAA record covers every name under the domain and ties it to this server's
ACME account, so another ACME client there is refused at its next renewal.
The guide no longer switches it on by itself, and the switch now carries a
warning.
Part of inbuxa/inbuxa-server#292
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.
Part of inbuxa/inbuxa-server#292.
The DNS guide switched on every record type except TLSA, so it published CAA for anyone who took the defaults. A CAA record covers every name under the domain and ties it to this server's ACME account, so another ACME client there is refused at its next renewal.
CAA is now off in the guide's defaults, and its switch carries a warning. A domain that already publishes CAA still loads with it on, because the guide reads the stored list.
The server's matching default change is in inbuxa/inbuxa-server#294. This PR works on its own, since the guide sends an explicit list.
Tested: new
records.test.ts, plus typecheck, lint, i18n check, fullnpm test, notice check and build. I didn't click through the guide in a browser.