Cloudflare DNS FAQ

Get help with common issues related to the Cloudflare DNS app.

Frequently asked questions about Cloudflare DNS


Is Cloudflare a free DNS (domain nameserver) provider?

Cloudflare offers free DNS services to customers in all plans. Note that:

1. You do not need to change your hosting provider to use Cloudflare.

2. You do not need to move away from your registrar. The only change you make with your registrar is to point the authoritative nameservers to the Cloudflare nameservers.

As of October 2018, you can transfer your domain to Cloudflare Registrar.


Does Cloudflare charge for or limit DNS queries?

Cloudflare's authoritative DNS services are free of charge and Cloudflare does not limit DNS queries for a domain on the Cloudflare network.


How fast is Cloudflare's free DNS service?

Cloudflare is the fastest DNS provider in the world, with the fastest speed overall for any DNS provider.


How many DNS records can I have per domain?

The limit per domain is 3,500 records. If you’d like to add more than the limit for a domain, contact us describing the use case and the need for more record types.


Where do I change my nameservers to point to Cloudflare?

Make the change at your registrar, which may or may not be your hosting provider. If you don't know who your registrar is for the domain, you can find this by doing a WHOis search.


Can I use Cloudflare without changing my nameservers to Cloudflare?

Changing your nameservers to Cloudflare is what allows us to fully proxy and provision a site. If you can't change to our nameservers, you have two options:

1. Activate Cloudflare through one of our certified hosting partners.

2 Ask for a CNAME setup.


How long does it take for a DNS change I made to push out?

The Cloudflare DNS default Time-To-Live (TTL) is 300 seconds (5 minutes). Any changes or additions you make to your Cloudflare zone file will push out in 5 minutes or less. Note that your local DNS cache may take longer to update; as such, propagation everywhere might take longer than 5 minutes.


Does Cloudflare support IPv6 DNS entries?

IPv6 needs to be added as an AAAA record, not an A record, in your DNS app settings.

See also:


Can I use Cloudflare with a Blogger.com domain?

You can use Cloudflare with any custom domain (yoursitename.com) for which you have control over managing its authoritative DNS.


Does Cloudflare offer domain masking?

Cloudflare does not offer domain masking services (your hosting provider might). We only offer URL forwarding through Page Rules.


Can I CNAME a domain not on Cloudflare to a domain that is on Cloudflare?

Using a CNAME to redirect traffic for a domain not on Cloudflare to a domain that is on Cloudflare creates a DNS resolution error. Since Cloudflare is a reverse proxy for the domain that is on Cloudflare, the CNAME redirect for the domain (not on Cloudflare) wouldn't know where to send the traffic to.

If you would still like to do a redirect for the site not on Cloudflare, then you should establish a traditional 301 or 302 redirect on your origin web server.


Can I use add-on domains with Cloudflare?

Add-on domains are technically different domains that point to another "main" domain server.

From a Cloudflare perspective, however, the domains are looked at as unique entities, which means that you would have to add each domain separately.

Cloudflare treats each of the following as a separate domain:

  • example1.com
  • example2.com
  • example3.com

Each domain needs to be added separately to your Cloudflare account, and may have a separate plan level, from Free to Enterprise. There's no limit on the number of domains in a Cloudflare account. If you have hundreds or thousands, as some customers do, you'll want to know how to use the Cloudflare API v4.

All subdomains are included, so these would all be considered one domain for Cloudflare plans:

  • example1.com
  • www.example1.com
  • blog.example1.com
  • Store.example1.com

Does Cloudflare support wildcard DNS entries?

Cloudflare supports the wildcard '*' record for DNS management in all customer plan. Enterprise customers get full proxy support for wildcard records.

Free, Pro and Business plans

Cloudflare does not proxy wildcard records; therefore, wildcard subdomains are served directly without any Cloudflare performance, security, or apps. As a result, Wildcard domains get no cloud (orange or grey) in the Cloudflare DNS app. If you are adding a `*` CNAME or A Record, you need to make sure the record is grey clouded in order for the record to be created.

To get Cloudflare protection on a wildcard subdomain (for example: www), you need to define that record explicitly in your Cloudflare DNS settings. First, log into your Cloudflare account and click the DNSapp. In this example, you would add "www" as its own CNAME record on your Cloudflare DNS settings and toggle the cloud to orange so the Cloudflare's proxy is enabled.

Cloudflare Enterprise customers can proxy wildcard records. To learn more about the Enterprise plan, contact us.

Wildcards are only valid in the left-most subdomain label. For example, it's not possible to add sub.*.example.com, but it's possible to add *.sub.example.com.


Why can't I make ANY queries to Cloudflare DNS servers?

ANY queries are special and often misunderstood. They are usually used to get all record types available on a DNS name, but what they return is just any type in the cache of recursive resolvers. This can cause confusion when they are used for debugging.

Because of Cloudflare's many advanced DNS features like CNAME flattening, it can be complex and even impossible to give correct answers to ANY queries. For example, when DNS records dynamically come and go or are stored remotely, it can be taxing or even impossible to get all the results at the same time.

ANY is rarely used in production, but is often used in DNS reflection attacks, taking advantage of the lengthy answer returned by ANY.

Instead of using ANY queries to list records, Cloudflare customers can get a better overview of their DNS records by logging in and checking their DNS app settings.

The decision to block ANY queries was implemented for all Authoritative DNS customers in September 2015, and does not affect Virtual DNS customers.

Read Deprecating the DNS ANY meta-query type in the Cloudflare blog.


Why do I have to remove my DS record when signing up for Cloudflare?

Cloudflare supports DNSSEC If a DS record is present at your registrar while using Cloudflare, you will run into connectivity errors such as SERVFAIL when using a validating resolver like Google and noErrrorfrom non-validating ones.

    Here is an example of what an error would look like:
    ╰─➤ dig dnssec-failed.org @8.8.8.8
     <<>> DiG 9.8.3-P1 <<>> dnssec-failed.org @8.8.8.8
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 5531
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION:
    ;dnssec-failed.org. IN A
    

With DNSSEC support, Cloudflare provides the DS record that must be uploaded to your parent when you enable DNSSEC for your domain.


What happens when I remove the DS record?

When you remove your DS record, an invalidation process begins which results in the unsigning your domain’s DNS records. This will chain of events that will allow your authoritative nameservers to be changed. If you are an existing customer, this will not affect your ability to use Cloudflare. New customers will need to complete this step before starting to use you can successfully start using Cloudflare


Does Cloudflare support EDNS0 (extension mechanisms for DNS)?

Yes, Cloudflare DNS supports EDNS0. EDNS0 is enabled for all Cloudflare customers. It is a building block for modern DNS implementations that adds support for signaling if the DNS Resolver (recursive DNS provider) supports larger message sizes and DNSSEC.

EDNS0 is the first approved set of mechanisms for DNS extensions, originally published as RFC 2671.

Not finding what you need?

95% of questions can be answered using the search tool. This is the quickest way to get a response.

Powered by Zendesk