Please Whitelist This Site?
I know everyone hates ads. But please understand that I am providing premium content for free that takes hundreds of hours of time to research and write. I don't want to go to a pay-only model like some sites, but when more and more people block ads, I end up working for free. And I have a family to support, just like you. :)
If you like The TCP/IP Guide, please consider the download version. It's priced very economically and you can read all of it in a convenient format without ads.
If you want to use this site for free, I'd be grateful if you could add the site to the whitelist for Adblock. To do so, just open the Adblock menu and select "Disable on tcpipguide.com". Or go to the Tools menu and select "Adblock Plus Preferences...". Then click "Add Filter..." at the bottom, and add this string: "@@||tcpipguide.com^$document". Then just click OK.
Thanks for your understanding!
Sincerely, Charles Kozierok
Author and Publisher, The TCP/IP Guide
NOTE: Using software to mass-download the site degrades the server and is prohibited.
If you want to read The TCP/IP Guide offline, please consider licensing it. Thank you.
DNS Name Registration, Public Administration, Zones and Authorities
name space consists of a hierarchy of
domains and subdomains. From the root we have a number of top-level
domains, then second-level domains below them, and still lower-level
domains below that. The obvious questions then become: how do we determine
the shape and structure of the name space, and who will manage it? More
specifically, who will control the root of the tree and decide what
the top-level domains will be called? How will we then subdivide control
over the rest of the name space? How do we ensure there are no conflicts
in choosing the names of sibling subdomains within a domain?
DNS can be used on private networks
controlled by a single organization, and if so, the answer to my questions
above is obviously, that organization. We'll discuss private
naming, but in reality, it's just not that interesting. The vast majority
of DNS use occurs on the public Internet. Here, we have a much greater
challenge, because we have to construct a name space that spans the
globe and covers millions of machines managed by different organizations.
For this, we need a very capable name registration process and
administration methods to support it.
In this section I describe the process
of name registration and how authorities are managed within the Domain
Name System, focusing on the public Internet. I begin with a description
of the DNS hierarchical authority structure and how it relates to the
hierarchical name space, and a discussion of the concepts behind the
DNS distributed name database. I describe the Internet's organizational
and geopolitical top-level domains, and how they are administered by
various authorities. I then discuss how authority is delegated to the
second-level and lower-level domains, and how public registration of
domain names works, including how public registration issues and problems
are resolved. I explain how the DNS name space is partitioned into administrative
zones of authority, and conclude with a brief discussion of private
DNS name registration.
|If you find The TCP/IP Guide useful, please consider making a small Paypal donation to help the site, using one of the buttons below. You can also donate a custom amount using the far right button (not less than $1 please, or PayPal gets most/all of your money!) In lieu of a larger donation, you may wish to consider purchasing a download license of The TCP/IP Guide. Thanks for your support!|
Table Of Contents - Contact Us
The TCP/IP Guide (http://www.TCPIPGuide.com)
Version 3.0 - Version Date: September 20, 2005
© Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved.
Not responsible for any loss resulting from the use of this site.