Skip to content

Commit f1eeb6b

Browse files
committed
Add DNS policy partial
1 parent 6502697 commit f1eeb6b

File tree

3 files changed

+26
-23
lines changed

3 files changed

+26
-23
lines changed

src/content/docs/cloudflare-one/policies/gateway/initial-setup/dns.mdx

Lines changed: 5 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ To filter DNS requests from an individual device such as a laptop or phone:
2525

2626
1. [Install the WARP client](/cloudflare-one/connections/connect-devices/warp/deployment/) on your device.
2727
2. In the WARP client Settings, log in to your organization's <GlossaryTooltip term="team name">Zero Trust instance</GlossaryTooltip>.
28-
3. (Optional) If you want to display a [custom block page](/cloudflare-one/policies/gateway/block-page/), [install the Cloudflare root certificate](/cloudflare-one/connections/connect-devices/user-side-certificates/) on your device.
28+
3. (Optional) If you want to display a [custom block page](/cloudflare-one/policies/gateway/block-page/), [install a Cloudflare root certificate](/cloudflare-one/connections/connect-devices/user-side-certificates/) on your device.
2929

3030
### Connect DNS locations
3131

@@ -44,20 +44,16 @@ Gateway identifies locations differently depending on the DNS query protocol:
4444

4545
## 2. Verify device connectivity
4646

47+
To verify your device is connected to Zero Trust:
48+
4749
<Render
4850
file="gateway/verify-connectivity"
4951
params={{ one: "DNS", two: "queries" }}
5052
/>
5153

52-
## 3. Add recommended policies
53-
54-
To create a new DNS policy, go to **Gateway** > **Firewall policies** > **DNS** in Zero Trust. We recommend adding the following policy:
55-
56-
### Block all security categories
57-
58-
Block [known threats](/cloudflare-one/policies/gateway/domain-categories/#security-categories) such as Command & Control, Botnet and Malware based on Cloudflare's threat intelligence.
54+
## 3. Create your first DNS policy
5955

60-
<Render file="gateway/policies/block-security-categories" />
56+
<Render file="gateway/get-started/create-dns-policy" />
6157

6258
## 4. Add optional policies
6359

src/content/docs/learning-paths/secure-internet-traffic/build-dns-policies/create-policy.mdx

Lines changed: 1 addition & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -11,17 +11,4 @@ DNS policies determine how Gateway should handle a DNS request. When a user send
1111

1212
You can filter DNS traffic based on query or response parameters (such as domain, source IP, or geolocation). You can also filter by user identity if you connect your devices to Gateway with the [WARP client or Cloudflare One Agent](/learning-paths/secure-internet-traffic/connect-devices-networks/install-agent/).
1313

14-
To create a new DNS policy:
15-
16-
1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Gateway** > **Firewall policies**.
17-
2. In the **DNS** tab, select **Add a policy**.
18-
3. Name the policy.
19-
4. Under **Traffic**, build a logical expression that defines the traffic you want to allow or block.
20-
5. Choose an **Action** to take when traffic matches the logical expression. For example, we recommend adding a policy to block all [security categories](/cloudflare-one/policies/gateway/domain-categories/#security-categories):
21-
<Render
22-
file="gateway/policies/block-security-categories"
23-
product="cloudflare-one"
24-
/>
25-
6. Select **Create policy**.
26-
27-
For more information, refer to [DNS policies](/cloudflare-one/policies/gateway/dns-policies/).
14+
<Render file="gateway/get-started/create-dns-policy" product="cloudflare-one" />
Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
{}
3+
---
4+
5+
import { Render } from "~/components";
6+
7+
To create a new DNS policy:
8+
9+
1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Gateway** > **Firewall policies**.
10+
2. In the **DNS** tab, select **Add a policy**.
11+
3. Name the policy.
12+
4. Under **Traffic**, build a logical expression that defines the traffic you want to allow or block.
13+
5. Choose an **Action** to take when traffic matches the logical expression. For example, we recommend adding a policy to block all [security categories](/cloudflare-one/policies/gateway/domain-categories/#security-categories):
14+
<Render
15+
file="gateway/policies/block-security-categories"
16+
product="cloudflare-one"
17+
/>
18+
6. Select **Create policy**.
19+
20+
For more information, refer to [DNS policies](/cloudflare-one/policies/gateway/dns-policies/).

0 commit comments

Comments
 (0)