diff --git a/public/__redirects b/public/__redirects index ab887a6116f0418..2b04c18251609d0 100644 --- a/public/__redirects +++ b/public/__redirects @@ -499,7 +499,9 @@ /dns/manage-dns-records/how-to/dns-load-balancing/ /dns/manage-dns-records/how-to/round-robin-dns/ 301 /dns/manage-dns-records/how-to/create-root-domain/ /dns/manage-dns-records/how-to/create-zone-apex/ 301 /dns/manage-dns-records/reference/proxied-dns-records/ /dns/proxy-status/ 301 +/dns/manage-dns-records/troubleshooting/acme-challenge-txt-record/ /dns/manage-dns-records/troubleshooting/unexpected-dns-records/#acme_challenge-txt-records 301 /dns/reference/troubleshooting/ /dns/reference/recommended-third-party-tools/ 301 +/dns/troubleshooting/faq/ /dns/faq/ 301 /dns/zone-setups/partial-setup/convert-partial-to-full/ /dns/zone-setups/conversions/convert-partial-to-full/ 301 /dns/zone-setups/partial-setup/convert-partial-to-secondary/ /dns/zone-setups/conversions/convert-partial-to-secondary/ 301 /dns/zone-setups/reference/nameserver-assignment/ /dns/nameservers/nameserver-options/#assignment-method 301 diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/troubleshooting.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/troubleshooting.mdx index ee25ba619d2a658..45b86736845e638 100644 --- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/troubleshooting.mdx +++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/troubleshooting.mdx @@ -42,6 +42,17 @@ If you encounter other 1XXX errors, refer to [Troubleshooting Cloudflare 1XXX Er --- +## Old SaaS provider content after updating a CNAME + +When switching SaaS providers, an older configuration can take precedence if the old provider provisioned a specific custom hostname and the new provider provisioned a wildcard custom hostname. This is expected as per the [certificate and hostname priority](https://developers.cloudflare.com/ssl/reference/certificate-and-hostname-priority/#hostname-priority). + +In this case there are two ways forward: + +- (Recommended) Ask the new SaaS provider to provision a specific custom hostname for you instead of the wildcard - `mystore.example.com` instead of `*.example.com`. +- Ask the Super Administrator of your account to contact [Cloudflare Support](/support/contacting-cloudflare-support/) to request an update of the SaaS configuration. + +--- + ## Custom hostname in Moved status To move a custom hostname back to an Active status, send a [PATCH request](/api/resources/custom_hostnames/methods/edit/) to restart the hostname validation. A Custom Hostname in a Moved status is deleted after 7 days. diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/worker-as-origin.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/worker-as-origin.mdx index 0a4ce6c34a43562..8dfaa57ee0fd59b 100644 --- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/worker-as-origin.mdx +++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/worker-as-origin.mdx @@ -32,7 +32,7 @@ You do not need to add individual Worker routes for each custom hostname. The wi ## Set up a Worker as your fallback origin -1. In your SaaS zone, [create and set a fallback origin](/cloudflare-for-platforms/cloudflare-for-saas/start/getting-started/#1-create-fallback-origin). Ensure the fallback origin only has an [originless DNS record](/dns/troubleshooting/faq/#what-ip-should-i-use-for-parked-domain--redirect-only--originless-setup): +1. In your SaaS zone, [create and set a fallback origin](/cloudflare-for-platforms/cloudflare-for-saas/start/getting-started/#1-create-fallback-origin). Ensure the fallback origin only has an [originless DNS record](/dns/manage-dns-records/how-to/create-dns-records/#originless-setups): - **Example**: `service.example.com AAAA 100::` 2. In that same zone, navigate to **Workers Routes**. 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/faq.mdx b/src/content/docs/dns/faq.mdx new file mode 100644 index 000000000000000..a935f0be84b16d2 --- /dev/null +++ b/src/content/docs/dns/faq.mdx @@ -0,0 +1,129 @@ +--- +pcx_content_type: faq +title: FAQ +description: Find answers to common questions about Cloudflare's authoritative DNS. +sidebar: + order: 21 +--- + +import { Render, DashButton } 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/). + +### Does Cloudflare support EDNS0 (extension mechanisms for DNS)? + +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](http://en.wikipedia.org/wiki/Extension_mechanisms_for_DNS), originally published as [RFC 2671](https://www.rfc-editor.org/rfc/rfc2671.html). + +--- + +## Nameservers + +### Where can I find my Cloudflare nameservers? + +On the **DNS Records** page, locate the **Cloudflare Nameservers** card. + + + +Also, 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 - refer to [Update nameservers](/dns/nameservers/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](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 their instructions. + + + +### Why have I received an email: (mydomain) stopped using Cloudflare's nameservers? + +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** 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..bf8d374e63c0468 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 @@ -5,7 +5,7 @@ sidebar: order: 2 --- -import { GlossaryTooltip, Render, TabItem, Tabs, Details, DashButton } from "~/components"; +import { GlossaryTooltip, Render, TabItem, Tabs, Details, DashButton, DirectoryListing } from "~/components"; Consider the sections below for step-by-step instructions on managing DNS records at Cloudflare. @@ -15,7 +15,11 @@ To better understand what DNS records are, refer to [Overview](/dns/manage-dns-r If your domain is added to Cloudflare by a hosting partner, manage your DNS records via the hosting partner. ::: -## Create DNS records +--- + +## Basic operations + +### Create DNS records @@ -43,9 +47,7 @@ For specific API examples, refer to [DNS record types](/dns/manage-dns-records/r ---- - -## Edit DNS records +### Edit DNS records @@ -67,9 +69,7 @@ To update part of a record with the API, use a [PATCH request](/api/resources/dn ---- - -## Delete DNS records +### Delete DNS records @@ -93,6 +93,22 @@ To delete records with the API, use a [DELETE request](/api/resources/dns/subres --- -## Batch record changes +## Use cases + +### 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. + +### Originless setups + +If you need a placeholder address for an originless setup (also referred to as parked domain or redirect-only), 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/). + +--- + +## Further guidance -For guidance on how to apply several changes to your zone records in just one action, refer to [Batch record changes](/dns/manage-dns-records/how-to/batch-record-changes/). \ No newline at end of file + \ No newline at end of file diff --git a/src/content/docs/dns/manage-dns-records/troubleshooting/acme-challenge-txt-record.mdx b/src/content/docs/dns/manage-dns-records/troubleshooting/unexpected-dns-records.mdx similarity index 52% rename from src/content/docs/dns/manage-dns-records/troubleshooting/acme-challenge-txt-record.mdx rename to src/content/docs/dns/manage-dns-records/troubleshooting/unexpected-dns-records.mdx index aea592732498c4d..26f358720f6af55 100644 --- a/src/content/docs/dns/manage-dns-records/troubleshooting/acme-challenge-txt-record.mdx +++ b/src/content/docs/dns/manage-dns-records/troubleshooting/unexpected-dns-records.mdx @@ -1,20 +1,44 @@ --- -title: Unexpected _acme-challenge TXT records +title: Unexpected DNS records pcx_content_type: troubleshooting sidebar: order: 11 - label: Unexpected TXT records + label: Unexpected DNS records --- import { GlossaryTooltip } from "~/components" +## Additional records after import + +You find several unexpected DNS records after adding your domain to Cloudflare. + +### Cause + +A wildcard (`*`) record at your previous authoritative DNS provider may have been imported into Cloudflare in a way that creates additional records. + +### Solution + +To solve this issue, you can do one of the following: + +- [Delete records in bulk](/dns/manage-dns-records/how-to/batch-record-changes/#delete-records-in-bulk). + +- Remove and re-add your domain: + + 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. + +--- + +## acme_challenge TXT records + You might notice TXT records like `_acme-challenge.` are returned by your domain but cannot be found on the DNS tab of your Cloudflare dashboard. -## Causes +### Cause These records are automatically created to allow Cloudflare edge certificates ([universal](/ssl/edge-certificates/universal-ssl/), [advanced](/ssl/edge-certificates/advanced-certificate-manager/), and [backup](/ssl/edge-certificates/backup-certificates/)) to be provisioned. `_acme-challenge` records are required by certificate authorities (CAs) so that they can verify your domain ownership before issuing the SSL/TLS certificate. For details, refer to [Domain control validation (DCV)](/ssl/edge-certificates/changing-dcv-method/). -## Solution +### Solution As these records are tied to the certificates, they cannot be deleted from the DNS tab of your Cloudflare dashboard. @@ -25,4 +49,20 @@ If you want to remove these records: * [Disable Universal SSL](/ssl/edge-certificates/universal-ssl/disable-universal-ssl/) to remove the records related to universal and backup certificates. * [Delete advanced certificates](/ssl/edge-certificates/advanced-certificate-manager/manage-certificates/#delete-a-certificate) to remove the records related to advanced certificates. +--- + +## Incorrect results for DNS queries + +You notice DNS queries returning incorrect results even after you waited for the [TTL](/dns/manage-dns-records/reference/ttl/) to expire. + +### Cause + +Third-party tools can sometimes fail to return correct DNS results if a recursive DNS cache fails to refresh. + +### Solution + +In this circumstance, purge your public DNS cache via these methods: +- [Purge your DNS cache at OpenDNS](http://www.opendns.com/support/cache/) +- [Purge your DNS cache at Google](https://developers.google.com/speed/public-dns/cache) +- [Purge your DNS cache locally](https://docs.cpanel.net/knowledge-base/dns/how-to-clear-your-dns-cache/) \ No newline at end of file diff --git a/src/content/docs/dns/proxy-status/index.mdx b/src/content/docs/dns/proxy-status/index.mdx index a48e568ba921689..cb7a6855ab6ff4f 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"; diff --git a/src/content/docs/dns/troubleshooting/faq.mdx b/src/content/docs/dns/troubleshooting/faq.mdx deleted file mode 100644 index 61fd39e352f6edc..000000000000000 --- a/src/content/docs/dns/troubleshooting/faq.mdx +++ /dev/null @@ -1,250 +0,0 @@ ---- -pcx_content_type: faq -source: https://support.cloudflare.com/hc/en-us/articles/360017421192-Cloudflare-DNS-FAQ -title: General FAQ -sidebar: - order: 1 ---- - -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)? - -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](http://en.wikipedia.org/wiki/Extension_mechanisms_for_DNS), originally published as [RFC 2671](https://datatracker.ietf.org/doc/html/rfc2671). - ---- - -## 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 - -**Problem Description** - -`Error: failed to create DNS record: HTTP status 403: Authentication error (10000)` is returned when using Terraform with Cloudflare API. - -**Root Cause** - -Error seems to be misleading, as the error was found to be in customer code syntax, specifically: zone_id = data.cloudflare_zones.example_com.id - -**Solution** - -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 - -When a SaaS provider is leveraging our [Cloudflare for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/) solution, they create a [Custom Hostname](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/) on their Cloudflare zone. -Then a [CNAME record needs to be created](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works/) on the client zone, to point to the SaaS provider service. -When changing SaaS providers, if the old SaaS provider provisioned a specific custom hostname for the record (`mystore.example.com`) and the new SaaS provider provisioned a wildcard custom hostname (`*.example.com`), the old custom hostname will still take precedence. -This is expected as per the [Certificate and hostname priority](https://developers.cloudflare.com/ssl/reference/certificate-and-hostname-priority/#hostname-priority). - -In this case there are 2 ways forward: -- (*Recommended*) Ask the new SaaS provider to provision a specific custom hostname for you instead of the wildcard (`mystore.example.com` instead of `*.example.com`). -- Ask the Super Administrator of your account to contact [Cloudflare Support](/support/contacting-cloudflare-support/) to request an update of the SaaS configuration. - diff --git a/src/content/docs/fundamentals/reference/troubleshooting.mdx b/src/content/docs/fundamentals/reference/troubleshooting.mdx index b69e7b6493eac14..5a1623f508b4e92 100644 --- a/src/content/docs/fundamentals/reference/troubleshooting.mdx +++ b/src/content/docs/fundamentals/reference/troubleshooting.mdx @@ -40,7 +40,7 @@ When you [set up Cloudflare](/fundamentals/account/), you may experience the fol ## General resources -* [DNS FAQ](/dns/troubleshooting/faq/) +* [DNS FAQ](/dns/faq/) * [SSL/TLS FAQ](/ssl/troubleshooting/faq/) ## Is Cloudflare attacking me diff --git a/src/content/docs/terraform/troubleshooting/authentication-error-dns-records.mdx b/src/content/docs/terraform/troubleshooting/authentication-error-dns-records.mdx new file mode 100644 index 000000000000000..7f70d8235425904 --- /dev/null +++ b/src/content/docs/terraform/troubleshooting/authentication-error-dns-records.mdx @@ -0,0 +1,24 @@ +--- +pcx_content_type: troubleshooting +title: 403 Authentication error when creating DNS records +sidebar: + label: Create DNS records error +--- + +When creating DNS records using Terraform, the API returns the following error: + +`Error: failed to create DNS record: HTTP status 403: Authentication error (10000)` + +This is caused by an error in your code syntax, when your are not using index `[0]` for the zones. Find an example below and a more detailed thread on [GitHub](https://github.com/cloudflare/terraform-provider-cloudflare/issues/913). + +Instead of this: + +```txt +zone_id = data.cloudflare_zones.example_com.id +``` + +Use this: + +```txt "zones[0]" +zone_id = data.cloudflare_zones.example_com.zones[0].id` +``` \ No newline at end of file diff --git a/src/content/partials/registrar/before-you-begin.mdx b/src/content/partials/registrar/before-you-begin.mdx index 72dec09f95e1d5d..99c90e6696e537e 100644 --- a/src/content/partials/registrar/before-you-begin.mdx +++ b/src/content/partials/registrar/before-you-begin.mdx @@ -23,7 +23,7 @@ import { Render, Details, GlossaryTooltip } from "~/components" If you are onboarding an existing domain to Cloudflare, make sure DNSSEC **is disabled** at your registrar. Otherwise, your domain will experience connectivity errors when you change your nameservers. 1. Take note of the TTL value for the DS record at your current registrar. -2. Remove DS records at your current registrar. +2. Remove DS records at your current registrar[^1]. 3. Wait at least the time corresponding to the DS record TTL. It is usually 24 hours, but refer to the value you got in step 1. 4. Follow the steps to [transfer your domain](/registrar/get-started/transfer-domain-to-cloudflare/#set-up-a-domain-transfer) to Cloudflare Registrar. @@ -32,3 +32,5 @@ If you are onboarding an existing domain to Cloudflare, make sure DNSSEC **is di
+ +[^1]: 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. \ No newline at end of file