DNS Firewall FAQ

Consider the answers for frequently asked questions about Cloudflare DNS Firewall.

DNS Firewall alternates between a customer's nameservers, using an algorithm that is more likely to send queries to the faster upstream nameservers than slower nameservers.

DNS Firewall sets cache longevity according to allocated memory.

As long as there is enough allocated memory, Cloudflare does not clear items from the cache forcefully, even when the TTL expires. This feature allows Cloudflare to serve stale objects from cache if your nameservers are offline.

Yes. SERVFAIL is treated like any other negative answer for caching purposes. The default TTL is 30 seconds. You can set a different negative cache TTL on your cluster in the Cloudflare dashboard, or via the API (negative_cache_ttl parameter).

Yes. Often, DNS providers want to see a client's IP via EDNS Client Subnet (ECS) (RFC 7871 ) because they serve geographically specific DNS answers based on the client's IP. With EDNS Client Subnet enabled, the DNS Firewall will forward the client's IP subnet along with the DNS query to the upstream nameserver.

When EDNS is enabled, the DNS Firewall gives out the geographically correct answer in cache based on the client IP subnet. To do this, the DNS Firewall segments its cache. For example:

1. A resolver says it is looking for an answer for client 192.0.2.0/24.
2. The DNS Firewall will proxy the request to the upstream nameserver for the answer.
3. The DNS Firewall will cache the answer from the upstream nameserver, but only for that /24.
4. 203.0.113.0/24 now asks the same DNS question and the answer is again returned from the upstream nameserver instead of the cache.

Some resolvers might not be sending any EDNS data. When you enable ECS fallback on your cluster in the Cloudflare dashboard or set the ecs_fallback parameter to true via the API DNS Firewall will forward the IP subnet of the resolver instead, only if there is no EDNS data present in the incoming DNS query.

Yes. The default TTL is 30 seconds. You can configure the negative cache TTL on your cluster in the Cloudflare dashboard, or via the API (negative_cache_ttl parameter). This will affect the TTL of responses with status REFUSED, NXDOMAIN, or SERVFAIL.

To set up PTR records for the DNS Firewall cluster IPs that point to your nameserver hostnames, use the following API endpoints:

• Show DNS Firewall Cluster Reverse DNS
• Update DNS Firewall Cluster Reverse DNS