Cloudflare DNS can describe two different DNS jobs: managing authoritative records for a website domain or providing recursive name resolution for an internet-connected device. Website owners need authoritative DNS to direct their domain toward hosting, email, and other services. Device and network users need a recursive resolver to look up domains while browsing. Choosing one does not configure the other.
What Cloudflare DNS means
The Domain Name System translates human-readable domain names into information that computers use to locate internet services. That description covers several roles, however, and the distinction matters when deciding what to configure.
Authoritative DNS stores the official records for a domain. When another system asks where a website, mail service, or other hostname should be found, the domain’s authoritative nameservers provide the relevant answer.
Recursive DNS works on behalf of a device or network. A recursive resolver receives a request for a domain, finds the necessary answer through the DNS hierarchy, and returns the result. A resolver available for general internet use is commonly called a public DNS resolver.
Cloudflare provides authoritative DNS as part of its broader web performance, security, and connectivity platform. The term Cloudflare DNS is also frequently used when discussing public recursive DNS. These services participate in the same naming system, but they serve different customers and solve different problems.
Cloudflare DNS for your website
A domain owner uses authoritative DNS to publish records that direct traffic to the appropriate destination. Those records can connect a hostname with website infrastructure, mail systems, verification services, or other resources.
Three components are important in this arrangement:
- The registrar maintains the domain registration and records which nameservers are authoritative for it.
- The authoritative DNS provider hosts the domain’s DNS zone and answers queries about its records.
- The hosting or application provider runs the website or service to which selected records point.
Cloudflare can perform the authoritative DNS role without becoming the domain’s registrar or replacing its conventional website hosting. To use Cloudflare-managed DNS, the domain must be delegated to the appropriate authoritative nameservers through its registration settings, and its required DNS records must exist in the managed zone.
Before changing that delegation, inventory the records needed by the website, email service, subdomains, and verification systems. Missing or incorrect records can make an otherwise functional service unreachable. The practical success check is that public DNS queries reach the new authoritative service and return the intended destinations for every important hostname.
Cloudflare can also proxy eligible website traffic, but authoritative DNS and reverse proxying are not identical. A record can be managed through Cloudflare DNS without necessarily sending its associated traffic through every proxy-based service. The relevant DNS and proxy configuration determines the path.
Cloudflare public DNS for browsing
A public recursive resolver serves the device side of DNS. When you enter a website name, the configured resolver obtains the DNS answer needed by the browser or operating system. An internet provider may supply a resolver automatically, while a user or network administrator may choose another public resolver.
References to Cloudflare DNS servers in device or router settings normally concern this recursive function rather than control over a website’s DNS zone. The change affects lookups originating from that device or network. It does not alter the records that everyone else receives for your domain.
This boundary prevents several common configuration mistakes. Selecting a public Cloudflare DNS server does not:
- Change a domain’s authoritative nameservers
- Transfer domain registration or DNS record ownership
- Move a website to different hosting
- Enable Cloudflare proxy or content-delivery features for a site
- Edit website, mail, or verification records
Public-resolver addresses, supported protocols, and configuration requirements are product-specific details. Use Cloudflare’s current resolver instructions before changing a device or router rather than copying an address from an undated third-party guide.
How Cloudflare DNS IPv6 settings differ
IPv6 can be involved on either side of the DNS distinction, but it means something different in each case.
For a recursive resolver, an IPv6 endpoint lets an IPv6-capable device or network send DNS queries to the resolver over IPv6. The network must have working IPv6 connectivity and a valid resolver configuration. An IPv6 resolver address does not tell browsers that a particular website has an IPv6 destination.
For authoritative website DNS, an AAAA record associates a hostname with an IPv6 address. This is distinct from an A record, which associates a hostname with an IPv4 address. Publishing an AAAA record is useful only when the destination is correctly configured to accept the relevant service traffic over IPv6.
Therefore, Cloudflare IPv6 DNS can refer either to reaching a recursive resolver over IPv6 or to publishing an IPv6 destination for a domain. One concerns the path used for DNS queries; the other concerns the answer returned for a website hostname.
Which Cloudflare DNS option fits your need
| Your goal | DNS role needed | Next action |
|---|---|---|
| Manage where your domain, website, or mail host points | Authoritative DNS | Prepare the required records and delegate the domain to the authoritative nameservers assigned for its DNS zone. |
| Change how a device or network looks up internet domains | Public recursive DNS | Follow the current resolver configuration instructions for the device or network. |
| Use Cloudflare for your domain and your own connection | Both, configured separately | Configure authoritative DNS for the domain and recursive DNS for the device or network as independent tasks. |
Consider an illustrative example in which a shop owner delegates the shop’s domain to Cloudflare’s authoritative DNS and publishes records pointing to its existing web host and email provider. The owner’s laptop might use a public recursive resolver, but visitors can use that resolver, an internet provider’s resolver, or another service. They should ultimately obtain the authoritative records for the shop regardless of which functioning recursive resolver they use.
The decision rule is simple: choose authoritative DNS when you control the answers for a domain, and choose recursive DNS when you want a device or network to find answers. Use both only when you have both needs, and treat their configurations as separate changes.
What free DNS covers
Cloudflare offers an ongoing Network and CDN Free plan for a website or application. Its paid Network and CDN plans cover broader platform requirements, but a higher website plan should not be confused with the act of choosing a recursive resolver for a device.
Cost is only one part of the domain-side decision. A website owner should also confirm that the selected plan fits the required operational features and assurances. Cloudflare complements conventional hosting for most websites, so the origin application, registration, records, monitoring, and recovery planning still require attention.
Explore more technology guides on Techistuff.
Frequently Asked Questions About Cloudflare DNS
Is Cloudflare free DNS available for websites?
Cloudflare has an ongoing Network and CDN Free plan for a website or application, and its platform provides authoritative DNS. Plan entitlements and any DNS-specific limits should be checked before relying on the free plan for a particular domain or operational requirement.
Are Cloudflare DNS servers the same as website nameservers?
Not necessarily. Authoritative nameservers answer for domains delegated to them, while recursive DNS servers look up names on behalf of devices and networks. They occupy different positions in the DNS process even when services in both categories come from the same provider.
Does changing public DNS make my website use Cloudflare?
No. Changing a device or router to a public recursive resolver affects how that device or network looks up domain names. It does not transfer a domain, change its authoritative nameservers, edit its records, enable proxying, or replace its hosting.
Can Cloudflare DNS work with IPv6?
IPv6 can appear in two separate DNS contexts. A device may contact a recursive resolver over IPv6, while a website can publish an AAAA record pointing its hostname to an IPv6 destination. Use Cloudflare’s current instructions to confirm supported resolver endpoints and domain configuration details.
