Skip to content

Commit 5e036fb

Browse files
Update get-started to match Gateway resolver UI text
1 parent cc353db commit 5e036fb

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -109,7 +109,7 @@ Besides selecting an internal DNS view when setting up your resolver policies, y
109109
1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Gateway** > **Resolver policies**.
110110
2. Select **Add a policy** and enter a name and description.
111111
3. Create an expression for the traffic you wish to route. For guidance about selectors, operators, and values, refer to [Gateway](/cloudflare-one/policies/gateway/resolver-policies/#selectors).
112-
4. Select **Use DNS view**. In the dropdown, choose the view that queries matching the expression should be sent to.
112+
4. Select **Use Internal DNS**. In the dropdown, choose the view that queries matching the expression should be sent to.
113113
5. (Optional) Adjust the option to **fallback through public DNS** according to your use case.
114114
- Off: Gateway DNS resolver returns the response as-is to the client.
115115
- On: In case the response from the internal zone is REFUSED, NXDOMAIN, or a response with a CNAME type, Gateway DNS resolver sends the query to Cloudflare 1.1.1.1 public resolver and tries to resolve the query via public DNS.

0 commit comments

Comments
 (0)