From 7d76805b2031601ffdc8efbb782cf6953c15c296 Mon Sep 17 00:00:00 2001 From: Ariel Barreiro Date: Tue, 3 Dec 2024 12:13:23 -0300 Subject: [PATCH 1/2] refactor: improve visibility of TXT affecting apex domain --- sites/platform/src/domains/steps/subdomains.md | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/sites/platform/src/domains/steps/subdomains.md b/sites/platform/src/domains/steps/subdomains.md index 276a1bf8a4..64c225b0fa 100644 --- a/sites/platform/src/domains/steps/subdomains.md +++ b/sites/platform/src/domains/steps/subdomains.md @@ -19,6 +19,15 @@ You need to add a DNS record to make it clear you explicitly allow multiple proj ## Enable subdomains across multiple projects +{{< note theme="warning" title="Apex domain cannot be re-added" >}} + +With the `TXT` record, restrictions apply on the apex domain. +For example, you can't add the apex domain to another project until you remove the `TXT` record. + +You can see an error like `'{{}}' is a root domain`. + +{{< /note >}} + To ensure multiple projects can use subdomains of the same apex domain, add a specific `TXT` DNS record for your apex domain. @@ -36,9 +45,6 @@ This ensures no other users can possibly add a subdomain of your domain to their Even if you don’t remove the record, your DNS records should prevent others from using a subdomain as long as you don’t use wildcards records pointing at {{% vendor/name %}}. -However, if you don't remove the `TXT` record, restrictions apply on the apex domain. -For example, you can't add the apex domain to another project until you remove the `TXT` record. - ## Bypass locked domains In certain cases (such as if your domain was added manually by {{% vendor/name %}} support), From e09d1391b425c2b42f26d6a45f025fc55ed6d050 Mon Sep 17 00:00:00 2001 From: Chad Carlson Date: Mon, 9 Dec 2024 12:26:40 -0500 Subject: [PATCH 2/2] Update subdomains.md --- sites/platform/src/domains/steps/subdomains.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/sites/platform/src/domains/steps/subdomains.md b/sites/platform/src/domains/steps/subdomains.md index 64c225b0fa..7b347b578e 100644 --- a/sites/platform/src/domains/steps/subdomains.md +++ b/sites/platform/src/domains/steps/subdomains.md @@ -19,15 +19,6 @@ You need to add a DNS record to make it clear you explicitly allow multiple proj ## Enable subdomains across multiple projects -{{< note theme="warning" title="Apex domain cannot be re-added" >}} - -With the `TXT` record, restrictions apply on the apex domain. -For example, you can't add the apex domain to another project until you remove the `TXT` record. - -You can see an error like `'{{}}' is a root domain`. - -{{< /note >}} - To ensure multiple projects can use subdomains of the same apex domain, add a specific `TXT` DNS record for your apex domain. @@ -45,6 +36,15 @@ This ensures no other users can possibly add a subdomain of your domain to their Even if you don’t remove the record, your DNS records should prevent others from using a subdomain as long as you don’t use wildcards records pointing at {{% vendor/name %}}. +{{< note theme="info" title="Apex domain cannot be re-added" >}} + +If you don't remove the `TXT` record, restrictions apply on the apex domain. +For example, you can't add the apex domain to another project until you remove the `TXT` record. + +You can see an error like `YOUR_APEX_DOMAIN is a root domain`. + +{{< /note >}} + ## Bypass locked domains In certain cases (such as if your domain was added manually by {{% vendor/name %}} support),