[ZT] RDP DNS record edits

[ranbel]

No description provided.

[hyperlint-ai]

Howdy and thanks for contributing to our repo. The Cloudflare team reviews new, external PRs within two (2) weeks. If it's been two weeks or longer without any movement, please tag the PR Assignees in a comment.

We review internal PRs within 1 week. If it's something urgent or has been sitting without a comment, start a thread in the Developer Docs space internally.

---

PR Change Summary

Updated the RDP documentation to include DNS record creation instructions and clarified existing content.

• Added a section on creating DNS records for RDP targets.
• Clarified the requirements for enabling browser-based RDP.
• Removed redundant information about DNS records from a previous section.

Modified Files

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

---

How can I customize these reviews?

Check out the Hyperlint AI Reviewer docs for more information on how to customize the review.

If you just want to ignore it on this PR, you can add the hyperlint-ignore label to the PR. Future changes won't trigger a Hyperlint review.

Note specifically for link checks, we only check the first 30 links in a file and we cache the results for several hours (for instance, if you just added a page, you might experience this). Our recommendation is to add hyperlint-ignore to the PR to ignore the link check for this PR.

[github-actions]

This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:

Pattern	Owners
/src/content/docs/cloudflare-one/connections/connect-networks/	@ranbel, @cloudflare/pcx-technical-writing

[github-actions]

Preview URL: https://ede365d5.preview.developers.cloudflare.com
Preview Branch URL: https://ranbel-rdp-dns-record.preview.developers.cloudflare.com

Files with changes (up to 15)

Original Link	Updated Link
https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/use-cases/rdp/rdp-browser/	https://ranbel-rdp-dns-record.preview.developers.cloudflare.com/cloudflare-one/connections/connect-networks/use-cases/rdp/rdp-browser/

[deadlypants1973]

Suggested change

	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).
	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 (refer to step 4).

[deadlypants1973]

I believe "targets" is ZTIA language meaning "machine being accessed by users"? We discussed the same about SSH. In my understanding, targets is not an industry term but rather something CF came up with to describe how to use us. If I am correct in my understanding, we should get clear on this definition and add it to the CF1 glossary to avoid confusion

cc @asamborski

[deadlypants1973]

Suggested change

	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.
	The DNS record does not need to point to an active destination IP address or hostname; the DNS record just needs to be valid. Cloudflare's RDP proxy will handle the routing to the correct RDP target.