diff --git a/src/content/docs/dns/dns-firewall/faq.mdx b/src/content/docs/dns/dns-firewall/faq.mdx index f408cf77c057782..037c7a734b6a8ec 100644 --- a/src/content/docs/dns/dns-firewall/faq.mdx +++ b/src/content/docs/dns/dns-firewall/faq.mdx @@ -1,37 +1,34 @@ --- -title: FAQ +title: DNS Firewall FAQ pcx_content_type: faq description: Find answers to common questions about Cloudflare's DNS Firewall, including cache behavior, EDNS support, and setting PTR records. sidebar: order: 4 + label: FAQ head: - tag: title content: FAQs — DNS Firewall --- -import { Details, GlossaryTooltip } from "~/components"; +import { GlossaryTooltip } from "~/components"; -
+Consider the answers for frequently asked questions about Cloudflare DNS Firewall. -DNS Firewall alternates between a customer's nameservers, using an algorithm is more likely to send queries to the faster upstream nameservers than slower nameservers. +## How does DNS Firewall choose a backend nameserver to query upstream? -
+DNS Firewall alternates between a customer's nameservers, using an algorithm is more likely to send queries to the faster upstream nameservers than slower nameservers. -
+## How long does DNS Firewall cache a stale object? DNS Firewall sets cache longevity according to allocated memory. As long as there is enough allocated memory, Cloudflare does not clear items from the cache forcefully, even when the TTL expires. This feature allows Cloudflare to serve stale objects from cache if your nameservers are offline. -
- -
+## Does the DNS Firewall cache SERVFAIL? Yes. `SERVFAIL` is treated like any other negative answer for caching purposes. The default TTL is 30 seconds. You can use the [API](/api/resources/dns_firewall/methods/edit/) to set a different `negative_cache_ttl`. -
- -
+## Does DNS Firewall support EDNS Client Subnet (ECS)? Yes. Often, DNS providers want to see a client's IP via EDNS Client Subnet (ECS) ([RFC 7871](https://www.rfc-editor.org/rfc/rfc7871.html)) because they serve geographically specific DNS answers based on the client's IP. With EDNS Client Subnet enabled, the DNS Firewall will forward the client's IP subnet along with the DNS query to the upstream nameserver. @@ -50,19 +47,13 @@ EDNS limits the effectiveness of the DNS cache. Some resolvers might not be sending any EDNS data. When you set the `ecs_fallback` parameter to `true` via the [API](/api/resources/dns_firewall/methods/edit/), DNS Firewall will forward the IP subnet of the resolver instead only if there is no EDNS data present in incoming the DNS query. -
- -
+## Does DNS Firewall cache negative answers? Yes. The default TTL is 30 seconds. You can set `negative_cache_ttl` via the [API](/api/resources/dns_firewall/methods/edit/). This will affect the TTL of responses with status `REFUSED`, `NXDOMAIN`, or `SERVFAIL`. -
- -
+## How can I set PTR records for nameserver hostnames? To set up PTR records for the DNS Firewall cluster IPs that point to your nameserver hostnames, use the following API endpoints: - [Show DNS Firewall Cluster Reverse DNS](/api/resources/dns_firewall/subresources/reverse_dns/methods/get/) - [Update DNS Firewall Cluster Reverse DNS](/api/resources/dns_firewall/subresources/reverse_dns/methods/edit/) - -
diff --git a/src/content/docs/dns/dnssec/index.mdx b/src/content/docs/dns/dnssec/index.mdx index b7926b4e79dbe74..a47c4d468d1e908 100644 --- a/src/content/docs/dns/dnssec/index.mdx +++ b/src/content/docs/dns/dnssec/index.mdx @@ -18,6 +18,8 @@ import { Render } from "~/components" +Removing the DS record at your registrar starts a DNSSEC unsigning process. This is expected when you are moving authoritative DNS providers, because it allows you to update your authoritative nameservers without DNSSEC validation failures. + *** ## Enable DNSSEC diff --git a/src/content/docs/dns/faq.mdx b/src/content/docs/dns/faq.mdx new file mode 100644 index 000000000000000..dd6c25e68e26a68 --- /dev/null +++ b/src/content/docs/dns/faq.mdx @@ -0,0 +1,117 @@ +--- +pcx_content_type: faq +title: FAQ +description: Find answers to common questions about Cloudflare's authoritative DNS. +sidebar: + order: 21 +--- + +import { Render } from "~/components"; + +The sections bellow cover frequently asked questions about Cloudflare authoritative DNS. For DNS Firewall, refer to [DNS Firewall FAQ](/dns/dns-firewall/faq/). + +--- + +## Cloudflare offerings + +### Is Cloudflare a free DNS (domain nameserver) provider? + +Yes. Cloudflare offers [free DNS services](https://www.cloudflare.com/dns) 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. + +### Does Cloudflare charge for or limit DNS queries? + +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. + +### Does Cloudflare offer domain masking? + +No. Cloudflare does not offer domain masking or DNS redirect services (your hosting provider might). However, we do offer URL forwarding through [Bulk Redirects](/rules/url-forwarding/bulk-redirects/). + +### Can subdomains be added directly to Cloudflare? + +Yes. Enterprise customers can add subdomains directly to Cloudflare via [subdomain support](/dns/zone-setups/subdomain-setup/). + +--- + +## Nameservers + +### Where can I find my Cloudflare nameservers? + +Under the **DNS** app of your Cloudflare account, review the **Cloudflare Nameservers**. + +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](https://www.whatsmydns.net/): + +```sh +dig kate.ns.cloudflare.com +``` + +```sh output +kate.ns.cloudflare.com. 68675 IN A 173.245.58.124. +``` + +### Where do I change my nameservers to point to Cloudflare? + +Make the change at your registrar, which is where you registered your domain. This 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. You can use [ICANN Lookup](https://lookup.icann.org/), for example. + +:::caution + +Some country code TLDs may not be supported by ICANN Lookup. If that is the case, use a different WHOIS search tool. +::: + +Once you identify your registrar, follow the instructions in [change nameservers to Cloudflare](/dns/zone-setups/full-setup/setup/#update-your-nameservers). + +### Why have I received an email: Your Name Servers have Changed? + +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](/dns/zone-setups/reference/domain-status/) is updated from *Active* to *Moved* in the Cloudflare **Overview** app 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](/dns/zone-setups/reference/domain-status/), it will be deleted from Cloudflare. + + + +--- + +## DNS records + +### Does Cloudflare limit the number of DNS records a domain can have? + +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. + +:::note[For more DNS records] +If you are an Enterprise customer and require more DNS records, contact your account team. Cloudflare can support millions of DNS records on a single zone. +::: + +### How long does it take for a DNS change I made to push out? + +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](/dns/manage-dns-records/how-to/create-dns-records/), 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. + +### 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. + +Refer to [Deprecating the DNS ANY meta-query type](https://blog.cloudflare.com/deprecating-dns-any-meta-query-type/) for details. The decision to block `ANY` does not affect DNS Firewall customers. + + +### How do I add ANAME records on Cloudflare? + + + +### Why are Cloudflare's A or AAAA records / IP addresses for my domain's DNS responses appearing? + +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. \ No newline at end of file diff --git a/src/content/docs/dns/manage-dns-records/how-to/create-dns-records.mdx b/src/content/docs/dns/manage-dns-records/how-to/create-dns-records.mdx index f28ccbbe9af308e..e22f6ea221de731 100644 --- a/src/content/docs/dns/manage-dns-records/how-to/create-dns-records.mdx +++ b/src/content/docs/dns/manage-dns-records/how-to/create-dns-records.mdx @@ -67,6 +67,12 @@ To update part of a record with the API, use a [PATCH request](/api/resources/dn +### Update an origin IP address + +If your hosting provider changes or your origin IP address changes, update the **Content** value of the relevant DNS records (usually `A` or `AAAA` records). + +If you are not sure which IP address to use, refer to your hosting provider's documentation. + --- ## Delete DNS records diff --git a/src/content/docs/dns/manage-dns-records/reference/dns-record-types.mdx b/src/content/docs/dns/manage-dns-records/reference/dns-record-types.mdx index 9560bdcb862f55c..6b23dd72f5e8713 100644 --- a/src/content/docs/dns/manage-dns-records/reference/dns-record-types.mdx +++ b/src/content/docs/dns/manage-dns-records/reference/dns-record-types.mdx @@ -112,6 +112,10 @@ These records include the following fields: - If the **Proxy Status** is **DNS Only**, you can customize the value. - **Proxy status**: For more details, refer to [Proxied DNS records](/dns/proxy-status/). +:::note +A CNAME record does not perform an HTTP redirect. If you need to redirect visitors (for example, from one hostname to another), configure a redirect on your origin or use Cloudflare redirect features. Refer to [Redirect one domain to another](/fundamentals/manage-domains/redirect-domain/). +::: + #### Proxied CNAME records Observe the following aspects, especially before changing a CNAME record from proxied to DNS-only or vice versa: diff --git a/src/content/docs/dns/manage-dns-records/reference/ttl.mdx b/src/content/docs/dns/manage-dns-records/reference/ttl.mdx index b7f0589bd85d8e9..f2d9cde1ccdeefd 100644 --- a/src/content/docs/dns/manage-dns-records/reference/ttl.mdx +++ b/src/content/docs/dns/manage-dns-records/reference/ttl.mdx @@ -12,6 +12,10 @@ import { GlossaryTooltip } from "~/components"; Longer TTLs speed up [DNS lookups](https://www.cloudflare.com/learning/dns/what-is-dns/) by increasing the chance of cached results, but a longer TTL also means that updates to your records take longer to go into effect. +:::note +DNS results can look inconsistent across tools because recursive resolvers cache answers for the duration of the TTL. If you recently changed a record, wait for the TTL to expire or query your authoritative nameservers directly. +::: + ## Proxied records By default, all proxied records have a TTL of **Auto**, which is set to 300 seconds. This value cannot be edited. diff --git a/src/content/docs/dns/proxy-status/index.mdx b/src/content/docs/dns/proxy-status/index.mdx index a48e568ba921689..2f7ad3c08a5153e 100644 --- a/src/content/docs/dns/proxy-status/index.mdx +++ b/src/content/docs/dns/proxy-status/index.mdx @@ -4,8 +4,6 @@ title: Proxy status sidebar: order: 7 label: Overview - group: - label: Proxy status --- import { Render, Example, Details, GlossaryTooltip } from "~/components"; @@ -59,6 +57,12 @@ Since only [records used for IP address resolution](/dns/manage-dns-records/refe It may take longer than five minutes for you to actually experience record changes, as your local DNS cache may take longer to update. ::: +### Originless and redirect-only setups + +If you need a placeholder address for an originless setup, you can use the reserved IPv6 address `100::` or the reserved IPv4 address `192.0.2.0` in a proxied DNS record. + +This allows you to route requests using products such as [Redirect Rules](/rules/url-forwarding/), [Page Rules](/rules/page-rules/), or [Workers](/workers/). + ### Mix proxied and unproxied If you have multiple A or AAAA records on the same name and at least one of them is proxied, Cloudflare will treat all A or AAAA records on this name as being proxied. diff --git a/src/content/docs/dns/troubleshooting/faq.mdx b/src/content/docs/dns/troubleshooting/faq.mdx index 61fd39e352f6edc..05e83d321b41fe2 100644 --- a/src/content/docs/dns/troubleshooting/faq.mdx +++ b/src/content/docs/dns/troubleshooting/faq.mdx @@ -8,128 +8,7 @@ sidebar: import { Render, GlossaryTooltip } from "~/components"; -## Is Cloudflare a free DNS (domain nameserver) provider? -Yes. Cloudflare offers [free DNS services](https://www.cloudflare.com/dns) to customers on 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. - ---- - -## Does Cloudflare charge for or limit DNS queries? - -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. - ---- - -## Where do I change my nameservers to point to Cloudflare? - -Make the change at your registrar, which is where you registered your domain. This 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. You can use [ICANN Lookup](https://lookup.icann.org/), for example. - -:::caution - -Some country code TLDs may not be supported by ICANN Lookup. If that is the case, use a different WHOIS search tool. -::: - -Once you identify your registrar, follow the instructions in [change nameservers to Cloudflare](/dns/zone-setups/full-setup/setup/#update-your-nameservers). - ---- - -## Does Cloudflare limit the number of DNS records a domain can have? - -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. - -:::note[For more DNS records] - -If you are an Enterprise customer and require more DNS records, contact your account team. Cloudflare can support millions of DNS records on a single zone. - -::: - ---- - -## Which record types can Cloudflare proxy? - -Only `A`, `AAAA`, and `CNAME` records can be proxied. Cloudflare will not proxy any other [DNS record types](/dns/manage-dns-records/reference/dns-record-types/). - ---- - -## How do I add ANAME records on Cloudflare? - - - ---- - -## Can I CNAME a domain not on Cloudflare to a domain that is on Cloudflare? - -No. If you would like to do a redirect for a site not on Cloudflare, then set up a traditional `301` or `302` redirect on your origin web server. - -Redirecting non-Cloudflare sites via `CNAME` records would cause 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) would not know where to send the traffic to. - ---- - -## Does Cloudflare support wildcard DNS entries? - -Cloudflare supports wildcard '\*' DNS records, both proxied and unproxied, on all plans. - ---- - -## How long does it take for a DNS change I made to push out? - -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](/dns/manage-dns-records/how-to/create-dns-records/), 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. - ---- - -## Does Cloudflare offer domain masking? - -No. Cloudflare does not offer domain masking or DNS redirect services (your hosting provider might). However, we do offer URL forwarding through [Bulk Redirects](/rules/url-forwarding/bulk-redirects/). - ---- - -## 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 DNS Firewall customers. - -Read [Deprecating the DNS ANY meta-query type](https://blog.cloudflare.com/deprecating-dns-any-meta-query-type/) on the Cloudflare blog. - ---- - -## Why do I have to remove my `DS` record when signing up for Cloudflare? - - - -For more help, refer to [Enabling DNSSEC in Cloudflare](/dns/dnssec/). - ---- - -## What happens when I remove the `DS` record? - -When you remove your DS record, an invalidation process begins which results in the unsigning of your domain’s DNS records. This 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 Cloudflare can be used successfully. - ---- ## Does Cloudflare support EDNS0 (extension mechanisms for DNS)? @@ -139,39 +18,6 @@ EDNS0 is the first approved set of mechanisms for [DNS extensions](http://en.wi --- -## What should I do if I change my server IP address or hosting provider? - -After switching hosting providers or server IP addresses, update the IP addresses in your Cloudflare **DNS** app. Your new hosting provider will provide the new IP addresses that your DNS should use.  To modify DNS record content in the **DNS** app, click on the IP address, and enter the new IP address. - ---- - -## Where can I find my Cloudflare nameservers? - -Under the **DNS** app of your Cloudflare account, review the **Cloudflare Nameservers**. - -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](https://www.whatsmydns.net/): - -```sh -dig kate.ns.cloudflare.com -``` - -```sh output -kate.ns.cloudflare.com. 68675 IN A 173.245.58.124. -``` - ---- - -## Why are Cloudflare's A or AAAA records / IP addresses for my domain's DNS responses appearing? - -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. - ---- - -## Can subdomains be added directly to Cloudflare? - -Only Enterprise customers can add subdomains directly to Cloudflare via [Subdomain Support](/dns/zone-setups/subdomain-setup/). - ---- ## 403 Authentication error when creating DNS records using Terraform @@ -187,54 +33,6 @@ Error seems to be misleading, as the error was found to be in customer code synt Make sure the argument `zone_id = data.cloudflare_zones.example_com.zones[0].id`. A more detailed use case can be found in [this](https://github.com/cloudflare/terraform-provider-cloudflare/issues/913) GitHub thread. ---- - -## Why am I getting hundreds of random DNS records after adding my domain? - -This can happen when you had a wildcard `*` record configured at your previous authoritative DNS, and for some reason the wildcard record wasn't detected. You can remove these records in bulk [using the API](/api/resources/dns/subresources/records/methods/delete/). - -Alternatively, you can also: - -1. [Remove your domain](/fundamentals/manage-domains/remove-domain/) from Cloudflare. -2. Delete the wildcard record from your authoritative DNS. -3. [Re-add](/fundamentals/manage-domains/add-site/) the domain. - ---- - -## What IP should I use for parked domain / redirect-only / originless setup? - -In the case a placeholder address is needed for “originless” setups, use the IPv6 reserved address `100::` or the IPv4 reserved address `192.0.2.0` in your Cloudflare DNS to create a [proxied DNS record](/dns/proxy-status/) that can use Cloudflare [Redirect Rules](/rules/url-forwarding/), [Page Rules](/rules/page-rules/), or [Cloudflare Workers](/workers/). - ---- - -## Why are DNS queries returning incorrect results? - -Third-party tools can sometimes fail to return correct DNS results if a recursive DNS cache fails to refresh. In this circumstance, purge your public DNS cache via these methods: - -- [Purging your DNS cache at OpenDNS](http://www.opendns.com/support/cache/) -- [Purging your DNS cache at Google](https://developers.google.com/speed/public-dns/cache) -- [Purging your DNS cache locally](https://docs.cpanel.net/knowledge-base/dns/how-to-clear-your-dns-cache/) - ---- - -## Why have I received an email: Your Name Servers have Changed? - -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](/dns/zone-setups/reference/domain-status/) is updated from *Active* to *Moved* in the Cloudflare **Overview** app 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](/dns/zone-setups/reference/domain-status/), it will be deleted from Cloudflare. - - - ---- - -## Why am I getting a warning for hostname not covered even if I have a custom certificate? - -If the [custom certificate](/ssl/edge-certificates/custom-certificates/) has been in place before our new certificate management pipeline, the following warning is displayed but can be discarded. -`This hostname is not covered by a certificate.` - -The warning will be gone when you upload a new custom certificate, or start using another type of certificate for this hostname. - - --- ## I've updated my CNAME to a new SaaS provider, but I still see content from the old provider diff --git a/src/content/docs/dns/zone-setups/full-setup/setup.mdx b/src/content/docs/dns/zone-setups/full-setup/setup.mdx index ea36a57ab8206a9..73ff1d1b578e990 100644 --- a/src/content/docs/dns/zone-setups/full-setup/setup.mdx +++ b/src/content/docs/dns/zone-setups/full-setup/setup.mdx @@ -73,6 +73,12 @@ When you start using Cloudflare's nameservers for authoritative DNS and your zon +### Unexpected DNS records after import + +If you see many unexpected DNS records after adding your domain, a wildcard (`*`) record at your previous authoritative DNS provider may have been imported into Cloudflare in a way that creates additional records. + +Review your imported records and remove any records that you do not need. For more background on wildcard behavior, refer to [Wildcard DNS records](/dns/manage-dns-records/reference/wildcard-dns-records/). + ## Update your nameservers