Skip to content

[iDNS] Call out Local Domain Fallback interference with Internal DNS #26343

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

Merged
merged 1 commit into from
Nov 7, 2025
Merged

[iDNS] Call out Local Domain Fallback interference with Internal DNS #26343

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
9 changes: 7 additions & 2 deletions src/content/docs/dns/internal-dns/get-started.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,12 +16,17 @@ import {

Follow this guide to get started with Internal DNS.

## Before you begin

<Render file="internal-dns-beta-note" product="dns" />

## Before you begin

- Make sure you have an Enterprise account with access to [Gateway resolver policies](/cloudflare-one/traffic-policies/resolver-policies/) and [Internal DNS](/dns/internal-dns/).
- Consider the different ways in which you can [connect to Gateway resolver](/dns/internal-dns/connectivity/).

:::caution
If using WARP, make sure your internal DNS zones or their TLDs are not listed in your [Local Domain Fallback configuration](/cloudflare-one/team-and-resources/devices/warp/configure-warp/route-traffic/local-domains/). Otherwise, DNS queries for a matching domain will be sent to the local DNS server specified in the fallback, instead of being sent to Cloudflare.
:::

- If you will be using an API token for authentication, make sure you have the following permissions:

<Details header="API token configuration">
Expand Down