rdp dns record

Author: ranbel

src/content/docs/cloudflare-one/connections/connect-networks/use-cases/rdp/rdp-browser.mdx

@@ -8,7 +8,7 @@ sidebar:
     text: Beta
 ---
 
-import { Render, GlossaryTooltip  } from "~/components"
+import { Render, GlossaryTooltip, Details  } from "~/components"
 
 Users can connect to an RDP server without installing an RDP client or the [WARP client](/cloudflare-one/connections/connect-devices/warp/) on their device. Browser-based RDP leverages [Cloudflare Tunnel](/cloudflare-one/connections/connect-networks/), which creates a secure, outbound-only connection from your RDP server to Cloudflare's global network. Setup involves running the `cloudflared` daemon on the RDP server (or any other host machine within the private network) and routing RDP traffic over a public hostname.
 
@@ -36,25 +36,43 @@ Browser-based RDP can be used in conjunction with [routing over WARP](/cloudflar
 
 ## 3. Create a DNS record
 
-To connect to your RDP targets (i.e., your Windows machines), configure a DNS record (including the subdomain) that users will use for RDP connections. This domain will be used to access any targets that are available to users through your Access application (see Step 4).
+To make your RDP targets (that is, your Windows machines) available through the browser, you will need a [Cloudflare DNS record](/dns/manage-dns-records/how-to/create-dns-records/) for the domain and subdomain that users will connect to.  This domain will be used to access any targets that are available to users through your Access application (see Step 4).
 
-For example, if your Access application is configured with `rdp.example.com`, you must have an "A" or "AAAA" DNS record for `rdp.example.com` created.
+For example, if want users to connect to targets on `rdp.example.com`, [create a DNS record](/dns/manage-dns-records/how-to/create-dns-records/#create-dns-records) for `rdp.example.com`. You can create either an `A`, `AAAA`, or `CNAME` record:
 
-To do this, go to the [Cloudflare dashboard](https://dash.cloudflare.com/login), select your domain, go to **DNS** > **Records** and verify that a [DNS record](/dns/manage-dns-records/how-to/create-dns-records/) exists for your desired RDP domain.
+<Details header="A record" open={false}>
+The following DNS record points your public subdomain (`rdp`) to the default IPv4 address range:
 
-If you do not already have a DNS record, [create a new DNS record](/dns/manage-dns-records/how-to/create-dns-records/#create-dns-records). Using `rdp.example.com` for demonstration, create an `AAAA` record that points your public subdomain (`rdp`) to the IPv6 [discard address range](https://www.rfc-editor.org/rfc/rfc6666.html):
+- **Type**: _A_
+- **Name**: `rdp`
+- **IPv4 address**: `0.0.0.0`
+- **Proxy status**: On
+
+</Details>
+
+<Details header="AAAA record" open={false}>
+The following DNS record points your public subdomain (`rdp`) to the IPv6 [discard address range](https://www.rfc-editor.org/rfc/rfc6666.html):
 
 - **Type**: _AAAA_
 - **Name**: `rdp`
 - **IPv6 address**: `100::`
 - **Proxy status**: On
 
-The IP address does not require active use; it just needs to be valid. Cloudflare's RDP proxy will handle the routing to the correct target.
+</Details>
 
-:::note
-		If you choose to create a _CNAME_ DNS record instead, *the Target field must be a fully qualified domain name.* It is *NOT* the target ID that you created in step (2). Using the example above, `rdp` would be the record Name and the Target field would be `www.rdp.example.com`. Proxy status would also need to be set to "On."
-:::
+<Details header="CNAME record" open={false}>
+The following `CNAME` record points your public subdomain (`rdp`) to a fully qualified domain name.
+
+- **Type**: _CNAME_
+- **Name**: `rdp`
+- **Target**: `www.rdp.example.com`
+- **Proxy status**: On
+
+The CNAME **Target** field is unrelated to the RDP targets configured in Step 2.
+
+</Details>
 
+The DNS record does not need to point to an active destination IP address or hostname; the record just needs to be valid. Cloudflare's RDP proxy will handle the routing to the correct RDP target.
 
 ## 4. Create an Access application
 
@@ -69,7 +87,7 @@ The IP address does not require active use; it just needs to be valid. Cloudflar
 7. <Render file="access/self-hosted-app/choose-domain" product="cloudflare-one" />
 
 		:::note
-		You can only enable browser-based RDP on domains and subdomains, not for specific paths.
+		You can only enable browser-based RDP on domains and subdomains, not for specific paths. The selected domain and subdomain must also have a corresponding DNS record (refer to [Step 3](#3-create-a-dns-record)).
 		:::
 
 8. Expand **Browser rendering settings**. In the **Browser rendering** dropdown, select _RDP_.