-
Notifications
You must be signed in to change notification settings - Fork 744
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
Check on Zone definition #4
Comments
Thanks @shoonyathaa, I don't know much about DNS other than this course so if you want to provide adjustments with a pull request I can merge it in. |
A DNS zone is a portion of the DNS namespace that is managed by a specific organization or administrator. All the information about a zone is stored in a plain text file called a zone file. This file is stored on the zone's nameserver(s) and contains an actual representation of the zone and contains all the records for every domain within the zone. A DNS zone refers to a certain portion or administrative space within the global Domain Name System (DNS). Each DNS zone represents a boundary of authority subject to management by certain entities. The total of all DNS zones, which are organized in a hierarchical tree-like order of cascading lower-level domains, form the DNS namespace. -- NTCHosting The authority over each DNS zone is delegated to a legal entity or organization (i.e. a country-code top-level domain registry) or a company/individual registered to use a certain sub-domain within the system. Depending on the administrative rights delegated to a certain entity, DNS zones may consist of only one domain, or of many domains and sub-domains. Further authority over a sub-space could be delegated to other parties, if necessary. -- NTCHosting A hosted zone is an Amazon Route 53 concept. A hosted zone is analogous to a traditional DNS zone file; it represents a collection of records that can be managed together, belonging to a single parent domain name. All resource record sets within a hosted zone must have the hosted zone’s domain name as a suffix. For example, the amazon.com hosted zone may contain records named www.amazon.com, and www.aws.amazon.com, but not a record named www.amazon.ca. You can use the Route 53 Management Console or API to create, inspect, modify, and delete hosted zones. -- Amazon |
Sorry for the late reply. Just saw your email and it has been long time
since I commented! Happy to contribute where required.
…On Wed, 23 Dec 2020, 8:27 am alozano-77, ***@***.***> wrote:
Thanks @shoonyathaa <https://github.com/shoonyathaa>, I don't know much
about DNS other than this course so if you want to provide adjustments with
a pull request I can merge it in.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#4 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFLM5BPPUR67BKEQRG3DOMDSWEMLTANCNFSM4PNJ2FTA>
.
|
"Zone: A part of the DNS database
This would be www.amazon.com"
My take is Zone is a logical construct which is part of the Domain Name System.
"amazon.com" is the Zone and "www.amazon.com" is a record/recordset which
is hosted in the zonefile. Let me know if this makes sense.
The text was updated successfully, but these errors were encountered: