Cloudflare is introducing Foundation DNS, a premium authoritative DNS product aimed at infrastructure teams that need high reliability, strong performance and support for complex setups.
Billing based on one metric
Enterprise DNS quotes typically require three inputs: the number of zones, monthly DNS query volume and the total record count across all zones. Some providers go further, offering pricing calculators or leaving pricing behind a "Contact Us" form, which makes budgeting for growth harder than it should be.
Foundation DNS is priced for enterprise customers on a single input: total DNS queries per month. Cloudflare's stated intent is to reduce cost and remove complexity from the DNS bill. DDoS mitigation remains unmetered, as with the rest of Cloudflare's products, and there are no hidden overage fees if nameservers are hit by a DDoS attack or query volume exceeds a quota for a month or two.
The dependencies behind a DNS lookup

DNS dates back almost to the beginning of the Internet. It was defined in RFC882 and RFC883 in 1983 to map hostnames to IP addresses; the authors already noted that the Internet "is a large system and is likely to grow much larger." Today the .com TLD alone holds almost 160 million domain names.
The system is hierarchical and highly distributed, but a user only talks directly to a resolver (1), either assigned or operated by an ISP or configured by an employer or the user. That resolver then contacts a root server (2), the responsible TLD server (3) and the domain's authoritative nameserver (4). These four parties are often run by different organizations in different regions, sometimes on different continents.

Outages such as the October 2021 Facebook incident show how much trouble a failed DNS infrastructure causes, in money and in reputation. A domain owner wants lookups answered 100% of the time and as fast as possible, yet the resolver and the root servers are outside their control, and the choice of TLD server is fixed once a domain name is chosen. The authoritative nameserver provider is the part they can change.
Cloudflare's authoritative DNS today
Authoritative DNS is one of Cloudflare's oldest products. Answers come from a global anycast network present in more than 250 cities, which provides performance and global availability, and the company's DDoS mitigation experience is applied to keeping nameservers and customer domains online.
Until the launch of Magic Transit, DNS was the path by which every Internet user was directed to Cloudflare to protect and accelerate customer applications. Slow or unavailable DNS answers meant a slow or unavailable Cloudflare, so the speed and reliability of authoritative DNS matter both to Cloudflare and to its customers. Some customers have grown their DNS footprint along with Cloudflare: the largest customer zone now holds more than 3 million records, and the top five approach almost 10 million records combined. These customers expect record updates to reach the edge in seconds rather than minutes. A dedicated DNS engineering team has been built over the years to keep the DNS stack fast and reliable.
DNSSEC and the routing problem
Cloudflare has long supported DNSSEC, which lets resolvers verify that an on-path attacker cannot hijack answers and redirect traffic. DNSSEC has been available at no charge on all plan levels and remains a no-charge option on Foundation DNS. Customers using Cloudflare as their registrar get one-click DNSSEC deployment; RFC 8078 is supported for one-click deployment on external registrars as well.
Route leaks and route hijacks can still disrupt the Internet, and they are largely outside any provider's control. DNSSEC helps against hijacks, but not every recursive resolver validates DNSSEC, and a route leak or hijack toward your nameservers still causes downtime. If every nameserver IP is affected, the domain becomes unresolvable.
With many providers, each nameserver resolves to only one IPv4 and one IPv6 address; if that address is unreachable — through congestion or a route leak, for example — the nameserver is unavailable and the domain becomes unresolvable. Some providers go further and use the same IP subnet for all their nameservers, so a problem with that subnet takes down all of them.
$ dig aws.com ns +short
ns-1500.awsdns-59.org.
ns-164.awsdns-20.com.
ns-2028.awsdns-61.co.uk.
ns-917.awsdns-50.net.
$ dig ns-1500.awsdns-59.org. +short
205.251.197.220
$ dig ns-164.awsdns-20.com. +short
205.251.192.164
$ dig ns-2028.awsdns-61.co.uk. +short
205.251.199.236
$ dig ns-917.awsdns-50.net. +short
205.251.195.149
In that example every nameserver IP sits inside 205.251.192.0/21. AWS now signs its ranges with RPKI, which makes a leak less likely — as long as the resolver's ISP validates RPKI. If it does not, and the subnet is leaked or hijacked, resolvers would be unable to reach any of the nameservers and aws.com would become unresolvable.
Cloudflare signs all of its routes and pushes the rest of the Internet toward RPKI, but it also has to keep its DNS systems resilient against route leaks while RPKI deployment catches up.
What Foundation DNS changes
On the Free, Pro, Business and Enterprise plans, a domain gets two nameservers of the form <name>.ns.cloudflare.com, where <name> is a random first name.
$ dig isbgpsafeyet.com ns +short
tom.ns.cloudflare.com.
kami.ns.cloudflare.com.
Each of these nameservers resolves to 3 anycast IPv4 and 3 anycast IPv6 addresses.
$ dig tom.ns.cloudflare.com a +short
173.245.59.147
108.162.193.147
172.64.33.147
$ dig tom.ns.cloudflare.com aaaa +short
2606:4700:58::adf5:3b93
2803:f800:50::6ca2:c193
2a06:98c1:50::ac40:2193
The important detail is that each of the 3 IPv4 and 3 IPv6 addresses comes from a different /8 IPv4 block (/45 for IPv6). For IPv4 nameservers to become unreachable, a route leak would have to hit the corresponding subnets across all three /8 blocks at once — theoretically possible, but virtually impossible in practice.
Foundation DNS customers receive a new set of advanced nameservers hosted on foundationdns.com and foundationdns.net, more resilient than the default Cloudflare nameservers. Cloudflare says it will publish more detail on how this is achieved early next year. All external Cloudflare domains, such as cloudflare.com, will move to these nameservers in the new year.
Beyond the core Foundation DNS service, Cloudflare is shipping two capabilities that have been on customers' request lists: outgoing zone transfers for Secondary DNS, and Logpush coverage for DNS query logs. Both come with Foundation DNS and are available to enterprise customers at no extra charge.
Secondary DNS gains a primary role
Enterprises that need redundancy across DNS providers have traditionally run a "multi-primary" arrangement — the same records configured on two independent platforms and synchronized by hand. Secondary DNS automates this through two mechanisms:
- DNS NOTIFY: the primary nameserver signals the secondary on every zone change, prompting the secondary to request a zone transfer and catch up.
- SOA query: the secondary polls the zone's SOA serial number at intervals; if the primary holds a newer serial than the one it has stored, it requests a transfer to pick up the changes.
In a variant known as a "hidden primary," only the secondary nameservers are authoritative — that is, registered at the registrar — while the primary stays out of public view.

Cloudflare has acted as a secondary nameserver since 2018, accepting incoming transfers from customers' primaries.

Now the reverse direction is supported: Cloudflare can serve as primary, with one or more external secondaries receiving transfers from it. As with incoming transfers, the feature covers:
- transfers over AXFR and IXFR
- automatic DNS NOTIFY messages that trigger a transfer on every change
- TSIG-signed transfers, so zone data is authenticated in transit
DNS logs via Logpush
Cloudflare's traffic volumes mean event logs are retained only for a limited window, enough to power near real-time dashboard analytics. Logpush, built in 2019, exists for customers who need or want permanent retention: it streams logs in near real time to Microsoft Azure Sentinel, Splunk, Datadog or Sumo Logic, or to any cloud storage destination with an R2-compatible API.

A new data set is now available: DNS logs. To stream them, open the Cloudflare dashboard, create a Logpush job, select DNS logs and choose the fields you need.

The developer documentation describes the new DNS log fields and explains how to configure the job through the API.
Load Balancing reaches more record types
Understanding how traffic moves through your infrastructure matters because compute, memory and server capacity are finite. Cloudflare's Load Balancing and Health Monitoring, offered since 2016, previously steered only A, AAAA and CNAME records. That left out MX traffic for mail servers, SRV records that declare ports and weights for a service, HTTPS records that keep traffic on a secure protocol regardless of port, and others.
New health monitoring methods now extend Load Balancing to MX, SRV, HTTPS and TXT records without additional configuration: create the DNS records in Cloudflare and set the Load Balancer as the destination. ICMP Ping, SMTP and UDP-ICMP methods keep visibility on server health so steering decisions can follow it.
Geo steering lets customers map regions to pools — sending, for example, requests originating in Eastern Europe to the appropriate server — but regions can be too coarse for some mappings. Country support is being added to Geo Steering, so a specific country can be mapped against pools alongside the thirteen existing regions. Country-level steering and the new health monitoring methods are expected in January 2022.
Multi-Signer DNSSEC and DNS-OARC membership
Large enterprises typically want both redundancy — multiple providers answering authoritatively — and authenticity through DNSSEC. Today's Secondary DNS supports this by having the primary sign the zone and transfer records with their signatures to the secondary, which serves them unchanged; non-standard features such as country-level steering can't survive that model. Multi-Signer DNSSEC (RFC8901) solves it: each provider knows the other's signing keys and signs online, on the fly. Work is finishing now, with rollout planned for Q1 2022.
Cloudflare is also joining DNS-OARC as a gold member, aiming to work with other researchers and operators on the hardest problems in DNS infrastructure and on implementing new standards.
"The DNS is a critical tool for management and delivery of content at the edge where consumers demand performance and reliability. Cloudflare is an important member of the DNS community, and have been a regular participant in OARC workshops for many years presenting their innovations and operational findings to our DNS-focused audience. It is a pleasure to now welcome them on-board as a full Member of our community, and we look forward to building upon their unique contributions as Gold OARC Members."- Keith Mitchell, OARC President



