Update from support feedback: apex domain A/AAAA records#6628
Open
mintlify-development[bot] wants to merge 1 commit into
Open
Update from support feedback: apex domain A/AAAA records#6628mintlify-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
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
Multiple customers on zone-apex domains (e.g.
example.com) have asked support how to point their apex at Mintlify sinceCNAMEis not legal at the apex on most providers. Support has been handing out a specific set ofAandAAAArecords to unblock them; this documents that path incustomize/custom-domainso users can self-serve.Changes
ALIASrecords and directA/AAAArecords.A(162.159.143.13,172.66.3.9) andAAAA(2606:4700:7::2fd,2a06:98c1:58::2fd) values with a note thatTXTverification records are still required and that theCNAMEandA/AAAAapproaches are mutually exclusive.Support context
Note
Low Risk
Documentation-only change to custom-domain setup guidance; no application or infrastructure code.
Overview
Documents a self-serve path for zone-apex custom domains when DNS providers cannot use apex
CNAME/ flattening /ALIAS—a flow support was already sharing manually.The Apex domains section is restructured into two paths: CNAME flattening or
ALIAS/ANAME(unchanged intent, clearer wording) and a new A and AAAA subsection with four edge IPs (162.159.143.13,172.66.3.9, and two IPv6 targets). It states that dashboardTXTverification records stay required, thatCNAMEandA/AAAAmust not be mixed for the same hostname, and still points users without apex options to a subdomain likedocs.example.com.Reviewed by Cursor Bugbot for commit 903ebee. Bugbot is set up for automated code reviews on this repo. Configure here.