Update from support feedback: custom domain day-2 operations#6432
Closed
mintlify-development[bot] wants to merge 1 commit into
Closed
Update from support feedback: custom domain day-2 operations#6432mintlify-development[bot] wants to merge 1 commit into
mintlify-development[bot] wants to merge 1 commit into
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
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
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
Adds a "Manage an existing custom domain" section to the custom domain page covering post-setup operations that support has been repeatedly asked about.
Changes
_acme-challengeand_cf-custom-hostnameTXTvalues can be regenerated by the dashboard and that users must always paste the currently displayed values.Context
Recurring resolved support conversations show that
/customize/custom-domaincovers first-time setup well but does not address day-2 operations (swap domain, re-verification when TXT values change, multi-domain/subpath serving, decommissioning).Note
Low Risk
Documentation-only change with no application, auth, or deployment code impact.
Overview
Adds a Manage an existing custom domain section to
customize/custom-domain.mdxfor post-setup operations that support sees often, placed before Set a canonical URL.It documents changing or replacing a primary domain (remove, add new, DNS cleanup, optional zero-downtime handoff and redirects) and notes the one primary custom domain per project limit with a pointer to multi-hostname options.
Re-verify when TXT values change explains when
_acme-challengeand_cf-custom-hostnamevalues can be regenerated and instructs users to use only the values currently shown in the dashboard, with steps to replace stale DNS records and recover after remove/re-add.Serve documentation across multiple domains covers 301 redirects to the primary domain, Enterprise multi-repository deployments, and external reverse-proxy patterns with links to Cloudflare, Vercel, and custom reverse-proxy docs.
Release a custom domain covers dashboard removal, DNS cleanup, and that Mintlify stops serving and renewing TLS for that hostname.
Reviewed by Cursor Bugbot for commit 38764ea. Bugbot is set up for automated code reviews on this repo. Configure here.