Add conditional rendering for create internal zone

Author: RebeccaTamachiro

src/content/docs/dns/internal-dns/get-started.mdx

@@ -41,16 +41,9 @@ Although there are some steps that can be achieved on the dashboard, currently t
 
 ## 1. Set up your internal DNS zone
 
-1. Use the [Create Zone](/api/resources/zones/) endpoint to create an [internal zone](/dns/internal-dns/internal-zones/). Specify your account ID and set the `type` to `internal`.
-
-<Details header="Internal zone configuration conditions">
-<Render file="internal-zones-conditions" />
-</Details>
-
-2. Add DNS records to your internal zone using your preferred option:
-- [Import](/api/resources/dns/subresources/records/methods/import/) a formatted BIND file. Refer to the [DNS records how-to](/dns/manage-dns-records/how-to/import-and-export/) for guidance.
-- Use other API endpoints, such as [`/batch`](/api/resources/dns/subresources/records/methods/batch/), to manage DNS records. Refer to [Batch record changes](/dns/manage-dns-records/how-to/batch-record-changes/#use-the-api) for details.
-3. Repeat this process for each internal zone you wish to add.
+<Render file="internal-zone-create" params={{
+	conditional: "get-started-detail"}}
+/>
 
 ### (Optional) Reference a zone from another zone
 

src/content/docs/dns/internal-dns/internal-zones/setup.mdx

@@ -17,14 +17,9 @@ When setting up internal zones, observe the following conditions:
 
 ## Create an internal zone
 
-1. Use the [Create Zone](/api/resources/zones/) endpoint to create an internal zone. Specify your account ID and set the `type` to `internal`.
-2. Add DNS records to your internal zone using your preferred option:
-- [Import](/api/resources/dns/subresources/records/methods/import/) a formatted BIND file. Refer to the [DNS records how-to](/dns/manage-dns-records/how-to/import-and-export/) for guidance.
-- Use other API endpoints, such as [`/batch`](/api/resources/dns/subresources/records/methods/batch/), to manage DNS records. Refer to [Batch record changes](/dns/manage-dns-records/how-to/batch-record-changes/#use-the-api) for details.
-3. Repeat this process for each internal zone you wish to add.
-
-Since the resolver policy configuration will require a DNS view, you must link the internal zones to at least one view to be able to use them when routing requests to Internal DNS. For a full procedure overview, refer to [get started](/dns/internal-dns/get-started/).
-
+<Render file="internal-zone-create" params={{
+	conditional: " "}}
+/>
 
 ## Other actions
 

src/content/partials/dns/internal-zone-create.mdx

@@ -0,0 +1,20 @@
+---
+params:
+  - conditional
+---
+
+import { TabItem, Tabs, Details, Example, Render, Markdown } from "~/components";
+
+1. Use the [Create Zone](/api/resources/zones/) endpoint to create an [internal zone](/dns/internal-dns/internal-zones/). Specify your account ID and set the `type` to `internal`.
+
+{ props.conditional === "get-started-detail" && (
+<Details header="Internal zone configuration conditions">
+<Render file="internal-zones-conditions" />
+</Details>
+	)
+}
+
+2. Add DNS records to your internal zone using your preferred option:
+- [Import](/api/resources/dns/subresources/records/methods/import/) a formatted BIND file. Refer to the [DNS records how-to](/dns/manage-dns-records/how-to/import-and-export/) for guidance.
+- Use other API endpoints, such as [`/batch`](/api/resources/dns/subresources/records/methods/batch/), to manage DNS records. Refer to [Batch record changes](/dns/manage-dns-records/how-to/batch-record-changes/#use-the-api) for details.
+3. Repeat this process for each internal zone you wish to add.