DNS Firewall
resource cloudflare_dns_firewall
required
optional
This setting controls how long DNS Firewall should cache negative responses (e.g., NXDOMAIN) from the upstream servers.
This setting does not affect the TTL value in the DNS response Cloudflare returns to clients. Cloudflare will always forward the TTL value received from upstream nameservers.
Ratelimit in queries per second per datacenter (applies to DNS queries sent to the upstream nameservers configured on the cluster)
By default, Cloudflare attempts to cache responses for as long as indicated by the TTL received from upstream nameservers. This setting sets an upper bound on this duration. For caching purposes, higher TTLs will be decreased to the maximum value defined by this setting.
This setting does not affect the TTL value in the DNS response Cloudflare returns to clients. Cloudflare will always forward the TTL value received from upstream nameservers.
By default, Cloudflare attempts to cache responses for as long as indicated by the TTL received from upstream nameservers. This setting sets a lower bound on this duration. For caching purposes, lower TTLs will be increased to the minimum value defined by this setting.
This setting does not affect the TTL value in the DNS response Cloudflare returns to clients. Cloudflare will always forward the TTL value received from upstream nameservers.
Note that, even with this setting, there is no guarantee that a response will be cached for at least the specified duration. Cached responses may be removed earlier for capacity or other operational reasons.
cloudflare_dns_firewall
resource "cloudflare_dns_firewall" "example_dns_firewall" {
account_id = "023e105f4ecef8ad9ca31a8372d0c353"
name = "My Awesome DNS Firewall cluster"
upstream_ips = ["192.0.2.1", "198.51.100.1", "2001:DB8:100::CF"]
attack_mitigation = {
enabled = true
only_when_upstream_unhealthy = false
}
deprecate_any_requests = true
ecs_fallback = false
maximum_cache_ttl = 900
minimum_cache_ttl = 60
negative_cache_ttl = 900
ratelimit = 600
retries = 2
}
data cloudflare_dns_firewall
computed
By default, Cloudflare attempts to cache responses for as long as indicated by the TTL received from upstream nameservers. This setting sets an upper bound on this duration. For caching purposes, higher TTLs will be decreased to the maximum value defined by this setting.
This setting does not affect the TTL value in the DNS response Cloudflare returns to clients. Cloudflare will always forward the TTL value received from upstream nameservers.
By default, Cloudflare attempts to cache responses for as long as indicated by the TTL received from upstream nameservers. This setting sets a lower bound on this duration. For caching purposes, lower TTLs will be increased to the minimum value defined by this setting.
This setting does not affect the TTL value in the DNS response Cloudflare returns to clients. Cloudflare will always forward the TTL value received from upstream nameservers.
Note that, even with this setting, there is no guarantee that a response will be cached for at least the specified duration. Cached responses may be removed earlier for capacity or other operational reasons.
This setting controls how long DNS Firewall should cache negative responses (e.g., NXDOMAIN) from the upstream servers.
This setting does not affect the TTL value in the DNS response Cloudflare returns to clients. Cloudflare will always forward the TTL value received from upstream nameservers.
Ratelimit in queries per second per datacenter (applies to DNS queries sent to the upstream nameservers configured on the cluster)
cloudflare_dns_firewall
data "cloudflare_dns_firewall" "example_dns_firewall" {
account_id = "023e105f4ecef8ad9ca31a8372d0c353"
dns_firewall_id = "023e105f4ecef8ad9ca31a8372d0c353"
}