-
Notifications
You must be signed in to change notification settings - Fork 5.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[DNS] More intro details on different DNS setups #18526
Merged
+35
−18
Merged
Changes from 6 commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
dcb1098
Move Concepts higher in get-started and add placeholder entry
RebeccaTamachiro 1193b29
Merge branch 'production'
RebeccaTamachiro 2adc2ee
Add Auth DNS and review concepts for Domain, Registrar, and Zone
RebeccaTamachiro 88b2769
Move nameserver def higher and solve overlap with Auth DNS
RebeccaTamachiro c2c18e9
Fill in DNS setups concept, applying Primary more prominently
RebeccaTamachiro 1b10bd5
Review concepts and missing link to partial-setup
RebeccaTamachiro f1ad7b0
Fix typo
RebeccaTamachiro 9c6cdcf
Update zone-setups page title to align with concepts and Dash
RebeccaTamachiro 182968e
Link out to domain-configurations as per Abby suggestion
RebeccaTamachiro 46c2b99
Process suggestions from PCX review
RebeccaTamachiro File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
|
@@ -9,29 +9,47 @@ head: | |||||
|
||||||
--- | ||||||
|
||||||
This page defines and articulates key concepts that are relevant to the Cloudflare DNS service and are used in this documentation. For more concepts and broader descriptions, check out the [Cloudflare Learning Center](https://www.cloudflare.com/learning/dns/what-is-dns/). | ||||||
This page defines and articulates key concepts that are relevant to the Cloudflare DNS service and are used in this documentation. For more concepts and broader descriptions, consider the [Cloudflare Learning Center](https://www.cloudflare.com/learning/dns/what-is-dns/). | ||||||
|
||||||
## Domain | ||||||
|
||||||
Also known as domain name, a domain is the string of text that identifies a specific website, such as `google.com` or `facebook.com`. Every time you access a website from your web browser, a DNS query takes place and the domain name is mapped to the actual IP address where the website is hosted. | ||||||
Also known as domain name, a domain is the string of text that identifies a specific website, such as `google.com` or `facebook.com`. Every time you access a website from your web browser, a DNS query takes place and the domain name is mapped to the actual IP address where the website is [hosted](/fundamentals/setup/manage-domains/). | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
Second sentence is in passive voice. Would be worth changing it to "the DNS service maps the domain name is mapped to the actual IP addres where..." |
||||||
|
||||||
## Registrar | ||||||
|
||||||
Before you can start using the Cloudflare DNS service, you must first have a domain. This is achieved by using a service called registrar. As explained in our [Learning Center](https://www.cloudflare.com/learning/dns/glossary/what-is-a-domain-name-registrar/), a registrar handles the reservation of domain names as well as the assignment of IP addresses for those domains. | ||||||
Before you can start using the Cloudflare DNS service, you must first have a domain. This is achieved by using a service called registrar. As explained in our [Learning Center](https://www.cloudflare.com/learning/dns/glossary/what-is-a-domain-name-registrar/), a registrar handles the reservation of domain names. | ||||||
|
||||||
Cloudflare offers at-cost domain registration through [Cloudflare Registrar](/registrar/). | ||||||
Very often the same company that offers domain registration also offers web hosting and DNS management. | ||||||
|
||||||
## Zone | ||||||
You can register a domain name at coast through [Cloudflare Registrar](/registrar/). Every domain acquired through Cloudflare Registrar must also use Cloudflare as [primary authoritative DNS](#authoritative-dns). | ||||||
RebeccaTamachiro marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
|
||||||
## Nameserver | ||||||
|
||||||
DNS zone is an administrative concept used for delegating control over DNS settings for different domains, subdomains or a set of both. You can read more about this in the [specific Learning Center article](https://www.cloudflare.com/learning/dns/glossary/dns-zone/). | ||||||
Although the resolution of a DNS query involves a number of different servers, in this documentation nameserver usually refers to the Cloudflare authoritative nameservers. As explained in the [article about DNS server types](https://www.cloudflare.com/learning/dns/dns-server-types/), the authoritative nameserver is the last stop in the resolution of a DNS query. | ||||||
|
||||||
For the purpose of this documentation, keep in mind that each site added to a Cloudflare account is listed in the account home page as a zone. The exact properties and behaviors of your zone depend on its [setup option](/dns/zone-setups/). | ||||||
Refer to [Nameservers](/dns/nameservers/) for details on the different nameserver offerings. | ||||||
|
||||||
## Nameserver | ||||||
## Authoritative DNS | ||||||
|
||||||
Authoritative DNS refers to the service whose nameservers provide the final information mapping a hostname (such as `example.com` or `blog.example.com`) to the IP address that hosts the corresponding content or resources. | ||||||
|
||||||
This is important because the performance of such authoritative DNS services determine how available, resilient, and performant your website or application is. Cloudflare DNS is an authoritative DNS service leveraging Cloudflare's global network. Refer to [How Cloudflare works](/fundamentals/concepts/how-cloudflare-works/) for details. | ||||||
|
||||||
## DNS setups | ||||||
|
||||||
It is also possible that one same company will use more than one DNS provider. Usually, this relates to making a domain more resilient - if one provider faces an outage, the nameservers operated by the other DNS provider will most likely still be available. | ||||||
|
||||||
In this context, you can have a primary DNS setup, when you use Cloudflare to manage your DNS records, or a [secondary DNS setup](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/), when your DNS records are managed on a different provider and Cloudflare simply receives zone transfers containing your DNS records. | ||||||
|
||||||
When you have a primary DNS setup, you can either use only Cloudflare (also known as [Full setup](/dns/zone-setups/full-setup/)), or you can use Cloudflare and another provider, where the other provider is the one to receive [outgoing zone transfers](/dns/zone-setups/zone-transfers/cloudflare-as-primary/) from Cloudflare. | ||||||
|
||||||
Finally, as Cloudflare also works as a [reverse proxy](/fundamentals/concepts/how-cloudflare-works/#how-cloudflare-works-as-a-reverse-proxy), [partial (CNAME) setups](/dns/zone-setups/partial-setup/) can be used when you do not want Cloudflare to be [authoritative](#authoritative-dns) for your domain but you still want to proxy individual subdomains through Cloudflare. | ||||||
|
||||||
## Zone | ||||||
|
||||||
Although the resolution of a DNS query involves a number of different servers, in this documentation nameserver usually refers to the Cloudflare authoritative nameservers. As explained in the [article about DNS server types](https://www.cloudflare.com/learning/dns/dns-server-types/), the authoritative nameserver is the last stop in the query, the server that returns the IP address for the requested domain. | ||||||
DNS zone is an administrative concept used for delegating control over DNS settings for different domains. You can read more about this in the [specific Learning Center article](https://www.cloudflare.com/learning/dns/glossary/dns-zone/). | ||||||
|
||||||
When you have a domain using a [full setup](/dns/zone-setups/full-setup/), Cloudflare provides the authoritative nameservers for your domain. Refer to [Nameservers](/dns/nameservers/) for details on the different nameserver offerings. | ||||||
For the purpose of this documentation, keep in mind that each domain added to a Cloudflare account is listed in the account home page as a zone. The exact properties and behaviors of your zone depend on its [DNS setup](/dns/zone-setups/). | ||||||
|
||||||
## DNS records | ||||||
|
||||||
|
@@ -43,4 +61,4 @@ For more details about using DNS records within Cloudflare, refer to [Manage DNS | |||||
|
||||||
DNSSEC stands for DNS Security Extensions. It increases security by adding cryptographic signatures to DNS records. These signatures can then be checked to verify that a record came from the correct DNS server, preventing anyone else from issuing false DNS records on your behalf and redirecting traffic intended for your domain. You can read more about it in the [article about DNS security](https://www.cloudflare.com/learning/dns/dns-security/). | ||||||
|
||||||
For help setting up DNSSEC in Cloudflare, refer to [Enable DNSSEC](/dns/dnssec/). | ||||||
For help setting up DNSSEC in Cloudflare, refer to [Enable DNSSEC](/dns/dnssec/). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.