FAQ
The sections below cover frequently asked questions about Cloudflare authoritative DNS. For DNS Firewall, refer to DNS Firewall FAQ.
Yes. Cloudflare offers free DNS services ↗ to customers on all plans. Note that:
- You do not need to change your hosting provider to use Cloudflare.
- 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.
Cloudflare never limits or caps DNS queries, but the pricing depends on your plan level.
For customers on Free, Pro, or Business plans, Cloudflare does not charge for DNS queries. For customers on Enterprise plans, Cloudflare uses the number of monthly DNS queries as a pricing input to generate a custom quote.
No. Cloudflare does not offer domain masking or DNS redirect services (your hosting provider might). However, we do offer URL forwarding through Bulk Redirects.
Yes. Enterprise customers can add subdomains directly to Cloudflare via subdomain support.
Yes, EDNS0 is a building block for modern DNS implementations and is enabled for all Cloudflare customers. EDNS0 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 ↗.
On the DNS Records page, locate the Cloudflare Nameservers card.
Go to RecordsAlso, the IP address associated with a specific Cloudflare nameserver can be retrieved via a dig command or a third-party DNS lookup tool hosted online such as whatsmydns.net ↗:
dig kate.ns.cloudflare.comkate.ns.cloudflare.com. 68675 IN A 173.245.58.124.Make the change at your registrar, which is where you registered your domain. This may or may not be your hosting provider - refer to Update nameservers for further context.
If you do not know who your registrar is for the domain, a WHOIS search can help. You can use ICANN Lookup ↗, for example.
Once you identify your registrar, follow their instructions.
Provider-specific instructions
This is not an exhaustive list of provider-specific instructions, but the following links may be helpful:
- Ionos ↗
- 101Domain ↗
- Amazon ↗
- Blacknight ↗
- BlueHost ↗
- DirectNIC ↗
- DNSMadeEasy ↗
- Domain.com ↗
- Dotster ↗
- DreamHost ↗
- EasyDNS ↗
- Enom ↗
- Fast Domain ↗
- FlokiNET ↗
- Gandi ↗
- GoDaddy ↗
- HostGator ↗
- Hostico ↗
- HostMonster ↗
- Hover ↗
- Internetdbs ↗
- iPage ↗
- MelbourneIT ↗
- Moniker ↗
- Name.com ↗
- Namecheap ↗
- Network Solutions ↗
- OVH ↗
- Porkbun ↗
- Rackspace ↗
- Register ↗
- Squarespace ↗
- Site5 ↗
- Softlayer ↗
- Yola ↗
For domains where Cloudflare hosts the DNS, Cloudflare continuously checks whether the domain uses Cloudflare's nameservers for DNS resolution. If Cloudflare's nameservers are not used, the domain status is updated from Active to Moved and an email is sent to the customer.
This is important because, if a domain is in a Moved state for a long enough period of time, it will be deleted from Cloudflare.
To recover a deleted domain, re-add it in Cloudflare just like you would for a new domain.
Yes. All customers have a limit on the number of DNS records they can create.
- Free: 200
- Pro: 3,500
- Business: 3,500
- Enterprise: 3,500
Free zones created before 2024-09-01 00:00:00 UTC have an increased limit of 1,000.
By default, any changes or additions you make to your Cloudflare zone file will take effect globally within 5 minutes, usually much less.
Depending on the Time-to-Live (TTL) set on the previous DNS record, old data may still remain cached until the TTL expires. Proxied records expire after 5 minutes ("Automatic"), but the TTL for unproxied records can be customized.
If changes to records with large TTLs are anticipated, it may make sense to reduce the TTL ahead of time so that the change takes effect as quickly as possible.
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.
Refer to Deprecating the DNS ANY meta-query type ↗ for details. The decision to block ANY does not affect DNS Firewall customers.
ANAME or ALIAS are DNS records used by specific DNS providers. If your previous provider was using ANAME or ALIAS, you can recreate these records on Cloudflare as CNAME records. Cloudflare's CNAME flattening1 allows you to create CNAME records at your zone apex, removing the need for those other record types.
-
A process in which Cloudflare returns an IP address instead of the target hostname that a CNAME record points to. ↩
For DNS records proxied to Cloudflare, Cloudflare's IP addresses are returned in DNS queries instead of your original server IP address. This allows Cloudflare to optimize, cache, and protect all requests for your website.
Was this helpful?
- Resources
- API
- New to Cloudflare?
- Directory
- Sponsorships
- Open Source
- Support
- Help Center
- System Status
- Compliance
- GDPR
- Company
- cloudflare.com
- Our team
- Careers
- © 2026 Cloudflare, Inc.
- Privacy Policy
- Terms of Use
- Report Security Issues
- Trademark
-