Truy cập clientless tới DNS private qua Cloudflare Access Access a web application via its private hostname without the Cloudflare One Client

With Cloudflare Browser Isolation and resolver policies, users can connect to private web-based applications via their private hostnames without needing to install the Cloudflare One Client. By the end of this tutorial, users who pass your Gateway DNS and network policies will be able to access your private application at https://<your-team-name>.cloudflareaccess.com/browser/https://internalrecord.com.

Make sure you have:

• Cloudflare Browser Isolation enabled on your account
• Resolver policies enabled on your account
• An HTTP or HTTPS application that users access through a browser

First, install cloudflared on a server in your private network:

1. Log in to the Cloudflare dashboard ↗ and go to Zero Trust \> Networks \> Connectors \> Cloudflare Tunnels.
2. Select Create a tunnel.
3. Choose Cloudflared for the connector type and select Next.
4. Enter a name for your tunnel. We suggest choosing a name that reflects the type of resources you want to connect through this tunnel (for example, enterprise-VPC-01).
5. Select Save tunnel.
6. Next, you will need to install cloudflared and run it. To do so, check that the environment under Choose an environment reflects the operating system on your machine, then copy the command in the box below and paste it into a terminal window. Run the command.
7. Once the command has finished running, your connector will appear in Cloudflare One.

1. Select Next.

1. In the CIDR tab, add the following IP addresses:

Private IP/CIDR of your application server (for example, 10.128.0.175/32) Private IP/CIDR of your DNS server

1. Select Save tunnel.

The application and DNS server are now connected to Cloudflare.

1. In Cloudflare One ↗, go to Browser isolation \> Browser isolation settings.
2. Turn on Allow users to open a remote browser without the device client.
3. For Permissions, select Manage.
4. Select Add a rule.
5. Create an expression that defines who can open the Clientless Web Isolation browser. For example,

| Rule action | Rule type | Selector | Value | Action | | ----------- | --------- | ---------------- | ------------ | ---------------- | | Allow | Include | Emails ending in | @example.com | Select Save. |

To test, open a browser and go to https://<team-name>.cloudflareaccess.com/browser/https://<private-IP-of-application>.

1. Go to Traffic policies \> Resolver policies.
2. Select Add a policy.
3. Create an expression to match against the private domain or hostname of the application:

| Selector | Operator | Value | | -------- | -------- | ------------------ | | Domain | in | internalrecord.com |

1. In Select DNS resolver, select Configure custom DNS resolvers.
2. Enter the private IP address of your DNS server.
3. In the dropdown menu, select <IP-address> - Private.
4. (Optional) Enter a custom port.
5. Select Create policy.

To test, open a browser and go to https://<team-name>.cloudflareaccess.com/browser/https://internalrecord.com.

1. Go to Traffic policies \> Firewall policies \> Network.
2. Add a network policy that targets the private IP address of your application. You can optionally include any ports or protocols relevant for application access. For example,

| Selector | Operator | Value | Logic | Action | | ---------------- | ------------- | -------------- | ----- | ------ | | Destination IP | in | 10.128.0.175 | And | Allow | | Destination Port | in | 80 | Or | | | User Email | matches regex | .\*example.com | | |

Device posture checks are not supported because they require the Cloudflare One Client.

For best practices on securing private applications, refer to Build secure access policies.

Users can now access the application at the following URL:

https://<team-name>.cloudflareaccess.com/browser/https://internalrecord.com

The application will load in an isolated browser. You can optionally configure remote browser controls such as disabling copy/paste, printing, or keyboard input.

{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"item":{"@id":"/directory/","name":"Directory"}},{"@type":"ListItem","position":2,"item":{"@id":"/cloudflare-one/","name":"Cloudflare One"}},{"@type":"ListItem","position":3,"item":{"@id":"/cloudflare-one/tutorials/","name":"Tutorials"}},{"@type":"ListItem","position":4,"item":{"@id":"/cloudflare-one/tutorials/clientless-access-private-dns/","name":"Access a web application via its private hostname without the Cloudflare One Client"}}]}