docs(dns): require Direct CNAME for custom domains (no orange-cloud) - #19
Merged
Merged
Conversation
A Proxied (orange-cloud) CNAME to another Cloudflare customer's hostname triggers Cloudflare Cross-User Banned (Error 1014). Spell out Direct CNAME (DNS only) for docs.cortex.foundation (Mintlify), status.cortex.foundation, the FernDesk Connect domain, and the software./releases. R2 custom domains owned by CortexLM/backend. Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
Contributor
Author
|
@greptileai review |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Operator docs in this repository now state that every Cortex custom domain
that CNAMEs to a third-party hostname uses a Direct CNAME (DNS only).
README.mdgains a Custom-domain DNS section listing the affectednames:
docs.cortex.foundation(Mintlify),status.cortex.foundation(status page), the FernDesk Connect domain, and the
software.cortex.foundation/releases.cortex.foundationR2 customdomains owned by
CortexLM/backend.scripts/FERNDESK.mdrepeats the rule where the FernDesk Connect domainis described, and points back at the README.
Why
A Proxied (orange-cloud) CNAME to a hostname that belongs to another
Cloudflare customer triggers Cloudflare Cross-User Banned (Error 1014)
and the hostname stops serving. Nothing in these docs said which side of the
toggle to pick, so an operator following them could pick Proxied.
Explicit wording added:
Test plan
No navigation, chrome, or public MDX page changed; both files are
repository/operator docs, not Mintlify pages.