Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Gateway] Internal DNS in resolver policies #21237

Merged
merged 4 commits into from
Mar 31, 2025
Merged

[Gateway] Internal DNS in resolver policies #21237

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
573fe14
Add internal DNS use case
maxvp Mar 28, 2025
d2b5542
Add more context
maxvp Mar 28, 2025
c37c97b
Add additional policy context
maxvp Mar 31, 2025
b128323
Make more succint
maxvp Mar 31, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion src/content/docs/cloudflare-one/policies/gateway/resolver-policies.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ head:
content: Resolver policies
---

import { Render } from "~/components";
import { Render, Badge } from "~/components";

:::note
Only available on Enterprise plans.
Expand Down Expand Up @@ -42,6 +42,14 @@ Gateway will route user traffic to your configured DNS resolver based on the mat

You may use resolver policies if you require access to non-publicly routed domains, such as private network services or internal resources. You may also use resolver policies if you need to access a protected DNS service or want to simplify DNS management for multiple locations.

### Internal DNS <Badge text="Beta" variant="caution" size="small" />

[Cloudflare Internal DNS](/dns/internal-dns/) allows you to manage DNS records for internal resources on a private network. DNS zones configured in Internal DNS can only be queried by the Gateway resolver. With resolver policies, you can determine how Gateway resolves your organization's DNS queries to resolve to internal resources based on the context of the query, such as known source IPs for a geographic location.

To get started with resolving internal DNS queries with resolver policies, refer to [Get started](/dns/internal-dns/get-started/).

### Local Domain Fallback

If your resolver is only reachable by a client device and not by Gateway via a Cloudflare tunnel, Magic WAN tunnel, or other public Internet connections, you should configure [Local Domain Fallback](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/local-domains/) for your device. If both Local Domain Fallback and resolver policies are configured for the same device, Cloudflare will apply your client-side Local Domain Fallback rules first. If you onboard DNS queries to Gateway with the WARP client and route them with resolver policies, the source IP of the queries will be the IP address assigned by the WARP client.

## Resolver connections
Expand Down
Loading