diff --git a/public/__redirects b/public/__redirects
index b2654a029e939e6..def5b7a3e391822 100644
--- a/public/__redirects
+++ b/public/__redirects
@@ -625,6 +625,7 @@
/fundamentals/concepts/what-is-cloudflare/ https://www.cloudflare.com/learning/what-is-cloudflare/ 301
/fundamentals/concepts/the-internet/ https://www.cloudflare.com/learning/network-layer/how-does-the-internet-work/ 301
/fundamentals/concepts/free-plan/ /fundamentals/subscriptions-and-billing/free-plan/ 301
+/fundamentals/setup/manage-domains/connect-your-domain/ /fundamentals/setup/manage-domains/add-site/ 301
# gateway
/gateway/about/ /cloudflare-one/policies/gateway/ 301
diff --git a/src/content/docs/dns/concepts.mdx b/src/content/docs/dns/concepts.mdx
index cf629bd138f8bb8..6395fdc0063a2ab 100644
--- a/src/content/docs/dns/concepts.mdx
+++ b/src/content/docs/dns/concepts.mdx
@@ -59,7 +59,7 @@ DNS zone is an administrative concept used for delegating control over a given d
For the purpose of this documentation, keep in mind that each domain added to a Cloudflare account is listed in the account home page as a zone. The exact properties and behaviors of your zone depend on its [DNS setup](/dns/zone-setups/).
-Also, different Cloudflare products and features are configurable at the zone level. Refer to [Fundamentals](/fundamentals/setup/manage-domains/connect-your-domain/#domain-configurations) for details.
+Also, different Cloudflare products and features are configurable at the zone level. Refer to [Fundamentals](/fundamentals/setup/manage-domains/add-site/) for details.
### Zone apex
diff --git a/src/content/docs/dns/proxy-status/index.mdx b/src/content/docs/dns/proxy-status/index.mdx
index 91643df18072929..23ebdedba14fda8 100644
--- a/src/content/docs/dns/proxy-status/index.mdx
+++ b/src/content/docs/dns/proxy-status/index.mdx
@@ -25,7 +25,7 @@ Proxying is on by default when you onboard a domain via the dashboard.
When you set a DNS record to **Proxied** (also known as orange-clouded), Cloudflare can:
- Protect your origin server from [DDoS attacks](https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/).
-- [Optimize, cache, and protect](/fundamentals/setup/manage-domains/connect-your-domain/#domain-configurations) all requests to your application.
+- [Optimize, cache, and protect](/fundamentals/setup/manage-domains/add-site/) all requests to your application.
- Apply your configurations for a variety of Cloudflare products.
:::caution
diff --git a/src/content/docs/dns/zone-setups/reference/domain-status.mdx b/src/content/docs/dns/zone-setups/reference/domain-status.mdx
index bb3f02646714d1d..70e350d2e7ddc7d 100644
--- a/src/content/docs/dns/zone-setups/reference/domain-status.mdx
+++ b/src/content/docs/dns/zone-setups/reference/domain-status.mdx
@@ -6,7 +6,7 @@ title: Zone status
Review information on the different statuses that your [zone](/dns/concepts/#zone) can have after you [add your website or application](/fundamentals/setup/manage-domains/add-site/) to Cloudflare.
-Zone status is also referred to as domain status. An **active** domain status is a requirement for your [application services configurations](/fundamentals/setup/manage-domains/connect-your-domain/#domain-configurations) to be applied. Refer to [How Cloudflare works](/fundamentals/concepts/how-cloudflare-works/) for details.
+Zone status is also referred to as domain status. An **active** domain status is a requirement for your [application services configurations](/fundamentals/setup/manage-domains/add-site/) to be applied. Refer to [How Cloudflare works](/fundamentals/concepts/how-cloudflare-works/) for details.
If your zone status changes, you will receive an email at the address associated with your account.
@@ -76,7 +76,7 @@ For Enterprise zones, if you want to adjust settings before zone activation, Log
## Active
-Cloudflare has authenticated your [nameserver changes](/dns/nameservers/update-nameservers/) or [verification TXT record](/dns/zone-setups/partial-setup/setup/#2-verify-ownership-for-your-domain) and you can proxy domain traffic through Cloudflare. For more details refer to [How Cloudflare works](/fundamentals/concepts/how-cloudflare-works/) and [Domain configurations](/fundamentals/setup/manage-domains/connect-your-domain/#domain-configurations).
+Cloudflare has authenticated your [nameserver changes](/dns/nameservers/update-nameservers/) or [verification TXT record](/dns/zone-setups/partial-setup/setup/#2-verify-ownership-for-your-domain) and you can proxy domain traffic through Cloudflare. For more details refer to [How Cloudflare works](/fundamentals/concepts/how-cloudflare-works/) and [Domain configurations](/fundamentals/setup/manage-domains/add-site/).
## Moved
diff --git a/src/content/docs/fundamentals/setup/manage-domains/add-site.mdx b/src/content/docs/fundamentals/setup/manage-domains/add-site.mdx
index 74cdd53192d2ea8..2e9de7c5f2a3a1d 100644
--- a/src/content/docs/fundamentals/setup/manage-domains/add-site.mdx
+++ b/src/content/docs/fundamentals/setup/manage-domains/add-site.mdx
@@ -6,25 +6,17 @@ pcx_content_type: tutorial
import { Render } from "~/components"
-Follow these steps to onboard your website or application to Cloudflare. Once your domain is [active](/dns/zone-setups/reference/domain-status/#active), your web traffic will [proxy through Cloudflare](/fundamentals/concepts/how-cloudflare-works/#cloudflare-as-a-reverse-proxy), which speeds up and protects websites and services on your domain.
+If you purchased your domain from a different provider, you can still connect the domain to Cloudflare. After you connect your domain to Cloudflare, Cloudflare will act as the [reverse proxy](/fundamentals/concepts/how-cloudflare-works/#cloudflare-as-a-reverse-proxy) and [DNS provider](/fundamentals/concepts/how-cloudflare-works/#cloudflare-as-a-dns-provider) for your site.
-Cloudflare will become the primary [DNS provider](/fundamentals/concepts/how-cloudflare-works/#cloudflare-as-a-dns-provider) for your domain, meaning your [DNS records](/dns/concepts/#dns-records) are managed at Cloudflare, and we authoritatively answer all DNS queries.
+The information below applies to a [full DNS setup](/dns/zone-setups/full-setup) which is the most common configuration.
:::note
-
-
-These instructions are tailored to customers using a [full DNS setup](/dns/zone-setups/full-setup) (the most common configuration). If you are using a [partial setup](/dns/zone-setups/partial-setup/) or [secondary setup](/dns/zone-setups/zone-transfers/), your onboarding process will be different.
-
-
+To use Cloudflare as a reverse proxy but maintain your DNS provider, refer to [partial setup](/dns/zone-setups/partial-setup/). To use one or more DNS providers, refer to or [DNS Zone transfers](/dns/zone-setups/zone-transfers/).
:::
## Prerequisites
-To onboard a website or application to Cloudflare, you need to own the domain name (`example.com`).
-
-If you do not already own a domain and plan to use Cloudflare for your [authoritative DNS](/dns/zone-setups/full-setup/), we highly recommend purchasing your domain name through [Cloudflare Registrar](/registrar/get-started/register-domain/). This simplifies your setup process by automatically using Cloudflare for authoritative DNS.
-
-
+[Disable DNSSEC](/dns/dnssec/#disable-dnssec) at the registrar where you purchased your domain name to avoid connectivity errors when you change your nameservers.
## 1. Add site in Cloudflare
@@ -36,8 +28,6 @@ If you do not already own a domain and plan to use Cloudflare for your [authorit
## 3. Complete SSL/TLS setup
-To prevent insecure connections and visitor browser errors, [make sure you have SSL/TLS protection](/ssl/get-started/).
-
-Many Cloudflare services will automatically protect and speed up your web traffic once your nameservers are updated.
+To prevent insecure connections and visitor browser errors, [enable SSL/TLS protection](/ssl/get-started/). Many Cloudflare services will automatically protect and speed up your web traffic after your nameservers are updated.
-To get more out of Cloudflare, refer to the [Security](/fundamentals/security/) and [Performance](/fundamentals/performance/) tasks.
+If you encounter unexpected results when changing your nameservers, refer to the [DNS Full Setup troubleshooting](/dns/zone-setups/full-setup/troubleshooting/).
diff --git a/src/content/docs/fundamentals/setup/manage-domains/connect-your-domain.mdx b/src/content/docs/fundamentals/setup/manage-domains/connect-your-domain.mdx
deleted file mode 100644
index ad63a14100a9d56..000000000000000
--- a/src/content/docs/fundamentals/setup/manage-domains/connect-your-domain.mdx
+++ /dev/null
@@ -1,58 +0,0 @@
----
-pcx_content_type: how-to
-title: Connect your domain
-
----
-
-Many of our layer 7 services depend on your domain using Cloudflare as a [reverse proxy](https://www.cloudflare.com/learning/cdn/glossary/reverse-proxy/) for its `HTTP/HTTPS` traffic.
-
-To get started with Cloudflare as a reverse proxy, you must first create an account and [connect your domain](/fundamentals/setup/manage-domains/connect-your-domain/). After creating your account, select **Add site** and follow the [step-by-step tutorial](/fundamentals/setup/manage-domains/add-site/) to configure your [DNS records](/dns/manage-dns-records/), which informs Cloudflare where to forward requests.
-
-Your domain is always in your control - connecting your domain to Cloudflare does not mean that you are relinquishing ownership. If you decide to [transfer your domain registration](/registrar/get-started/transfer-domain-to-cloudflare/) to be managed at Cloudflare, you will still retain full ownership.
-
-:::note
-
-For a domain purchased through [Cloudflare Registrar](/registrar/), we take care of the connection process on your behalf.
-:::
-
-## Domain configurations
-
-When you connect your domain to Cloudflare, a set of default configurations is generated for our [application services](/products/?product-group=Application+performance%2CApplication+security%2CCloudflare+essentials), based on the domain [plan](https://www.cloudflare.com/plans/). These services determine how Cloudflare treats traffic for your domain.
-
-Your configurations will only affect live traffic (that is, when your domain's status is [**active**](/fundamentals/setup/manage-domains/connect-your-domain/#activating-your-domain) and its traffic is [**proxied**](/dns/proxy-status/)). Notably, your configurations can be altered prior to activating or enabling the proxy status on the DNS records for the hostnames you want to proxy.
-
-Use the Cloudflare dashboard or [API](/api/) to modify, test, or [version](/version-management/) your configuration.
-
-:::note[Account-level configurations]
-
-Some configurations can be set at the account-level (if available in your plan), which can be applied to all domains under your account.
-
-Account-level configurations are applied to incoming traffic before your domain-level configurations. Refer to [traffic sequence](https://blog.cloudflare.com/traffic-sequence-which-product-runs-first) to learn more.
-:::
-
-## Activating your domain
-
-In a [full setup](/dns/zone-setups/full-setup/), your domain will be pending until you update its nameservers at your domain registrar with the assigned Cloudflare nameservers. This step is essential for two reasons:
-
-* First, to inform DNS resolvers that your traffic should route through Cloudflare
-* And second, to verify that you are the domain's owner. Only the owner or administrator of a domain can access its registrar and change its nameservers.
-
-:::note
-
-
-The activation process involves different steps if you are using a [secondary DNS](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/) or [partial (CNAME) setup](/dns/zone-setups/partial-setup/).
-
-
-:::
-
-Registrars take up to 24 hours to process nameserver changes (quicker in most cases). You will receive an email when your domain becomes active. While your domain is pending, your `HTTP/HTTPS` traffic is not proxied through Cloudflare, but Cloudflare will respond to DNS queries on your assigned nameservers.
-
-By activating your domain on a full setup, your traffic will immediately start using [Cloudflare's DNS services](/fundamentals/concepts/how-cloudflare-works/#cloudflare-as-a-dns-provider), so it is important to review how to [avoid downtime](/fundamentals/setup/manage-domains/connect-your-domain/#avoiding-downtime) and what [proxying traffic](/fundamentals/concepts/how-cloudflare-works/) means.
-
-## Avoiding downtime
-
-In a full setup, it is essential that your domains DNS table has all your DNS records configured properly *before* activating your domain. In addition, you may need to:
-
-* [Disable DNSSEC](/dns/dnssec/). DNSSEC is a security extension that ensures all DNS answers can be trusted. If nameservers are changed before disabling DNSSEC, their cryptographic signatures will no longer match and DNS resolution will fail. After your domain is successfully activated, you should enable DNSSEC again.
-* [Accept Cloudflare traffic](/fundamentals/concepts/cloudflare-ip-addresses/). If you are proxying traffic to your origin, you need to ensure that your origin will accept connections from Cloudflare. One way to do this is to allow traffic originating from Cloudflare IPs. You can harden the connection between Cloudflare and your origin by using Authenticated Origin Pulls ([mTLS](/ssl/origin-configuration/authenticated-origin-pull/)). An alternative approach to proxy traffic to your origin is to [configure a Cloudflare Tunnel](/cloudflare-one/connections/connect-networks/).
-* [Configure SSL/TLS](/ssl/edge-certificates/). The first thing Cloudflare does when it receives a `HTTP/HTTPS` request is decryption.
diff --git a/src/content/partials/fundamentals/add-site.mdx b/src/content/partials/fundamentals/add-site.mdx
index d0b09fdfa223d13..c401cf259f9dc2d 100644
--- a/src/content/partials/fundamentals/add-site.mdx
+++ b/src/content/partials/fundamentals/add-site.mdx
@@ -14,7 +14,7 @@ import { GlossaryTooltip, Render } from "~/components";
:::
4. Select a [plan](https://www.cloudflare.com/plans/#compare-features).
-5. Make sure we have all of your [DNS records](/dns/manage-dns-records/).
+5. [Review your DNS records](/dns/zone-setups/full-setup/setup/#review-dns-records) to ensure none are missing. Your DNS records must accurate for your domain to work properly.
diff --git a/src/content/partials/fundamentals/update-nameservers.mdx b/src/content/partials/fundamentals/update-nameservers.mdx
index 5b7b0d19f97fd9e..cbc978f36a5d65b 100644
--- a/src/content/partials/fundamentals/update-nameservers.mdx
+++ b/src/content/partials/fundamentals/update-nameservers.mdx
@@ -7,6 +7,6 @@ import { Render } from "~/components"
-Before your domain can begin using Cloudflare for DNS resolution, you need to [add these nameservers](/dns/zone-setups/full-setup/setup/#update-your-nameservers) at your registrar. Make sure DNSSEC **is disabled** at this point.
+Before your domain can begin using Cloudflare for DNS resolution, you need to [add these nameservers](/dns/zone-setups/full-setup/setup/#update-your-nameservers) at your registrar. DNSSEC should still be **disabled** at this point.