Skip to content

Commit e48bbb5

Browse files
Update index.mdx (#27079)
Co-authored-by: Max Phillips <[email protected]>
1 parent 0a7e6aa commit e48bbb5

File tree

1 file changed

+10
-0
lines changed
  • src/content/docs/cloudflare-one/traffic-policies/dns-policies

1 file changed

+10
-0
lines changed

src/content/docs/cloudflare-one/traffic-policies/dns-policies/index.mdx

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -491,3 +491,13 @@ Use this selector to apply policies to the source internal IP address of a DNS q
491491
### Magic WAN forwarding
492492

493493
To apply DNS policies to queries forwarded through [Magic WAN](/magic-wan/zero-trust/cloudflare-gateway/), you can either point your organization's DNS resolver to an IPv6, DoH, or DoT endpoint or request a dedicated resolver IPv4 address. For more information, refer to [DNS resolver IPs and hostnames](/cloudflare-one/networks/resolvers-and-proxies/dns/locations/dns-resolver-ips/).
494+
495+
### Fallback DNS
496+
497+
Some apps, such as WhatsApp and Android Studio, use hard-coded fallback DNS servers. Fallback DNS can cause unexpected behavior with Gateway DNS policies. For example, if you have a Block DNS policy, Gateway will initially block DNS queries from those apps, but the queries can resolve correctly afterward using the fallback DNS. To mitigate this behavior, you create a [Gateway Network policy](/cloudflare-one/traffic-policies/network-policies/) to block outbound DNS traffic on TCP/UDP port `53` to the fallback DNS servers. For example, to block Google's fallback DNS servers:
498+
499+
| Selector | Operator | Value | Logic | Action |
500+
| ---------------- | -------- | -------------------- | ----- | ------ |
501+
| Protocol | in | _TCP_, _UDP_ | And | Block |
502+
| Destination Port | in | `53` | And | |
503+
| Destination IP | in | `8.8.8.8`, `8.8.4.4` | | |

0 commit comments

Comments
 (0)