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.

The Book is Here... and Now On Sale!

Read offline with no ads or diagram watermarks!
The TCP/IP Guide

Custom Search







Table Of Contents  The TCP/IP Guide
 9  TCP/IP Application Layer Protocols, Services and Applications (OSI Layers 5, 6 and 7)
      9  Name Systems and TCP/IP Name Registration and Name Resolution
           9  TCP/IP Name Systems: Host Tables and Domain Name System (DNS)
                9  TCP/IP Domain Name System (DNS)
                     9  DNS Name Registration, Public Administration, Zones and Authorities

Previous Topic/Section
DNS Public Registration Disputes (Conflicts, Cybersquatting, "Deceptive Naming", Etc.) and Dispute Resolution
Previous Page
Pages in Current Topic/Section
1
23
Next Page
DNS Private Name Registration
Next Topic/Section

DNS Name Space Administrative Hierarchy Partitioning: DNS Zones of Authority
(Page 1 of 3)

I explained earlier in this topic that the DNS name space is arranged in a hierarchy, and that there is also a hierarchy of authorities that is related to that hierarchical name structure. However, the two hierarchies are not exactly the same. The reason is that if they were the same, this would mean we needed a separate authority for every domain at every level of the tree, and that's something we are very unlikely to want to have everywhere in the structure.

At the very top levels of the DNS tree, it seems reasonable that we might want to designate a separate authority at each level of the structure. Consider the geopolitical name hierarchy; IANA/ICANN manages the “root” domain, but each of the ccTLDs is managed by a distinct national authority

The Need For Authority Hierarchy Partitioning

However, when you get to the lower levels of the structure, it is often inconvenient or downright impossible to have each level correspond to a separate authority. As an example, let's suppose you are in charge of the Googleplex University IT department, which runs its own DNS servers for the “googleplex.edu” domain. Suppose there were only two schools at this university, teaching Fine Arts and Computer Science. Suppose also that the name space for the computers were divided into three subdomains: “finearts.googleplex.edu”, “compsci.googleplex.edu”, and “admin.googleplex.edu” (for central administrative functions, including the IT department itself).

Most likely, you don't want or need the Fine Arts department running its own DNS servers, and they probably don't want to, either. The same is likely true of the administration machines. However, it's possible that the Computer Science department does want to run its own DNS servers, because they probably have many more computers than the other departments, and they might use running a DNS server as part of their curriculum. In this case, you might want yourself, the administrator for “googleplex.edu”, to maintain authority for the “finearts.googleplex.edu” and “admin.googleplex.edu” subdomains and everything within them, while delegating authority for “compsci.googleplex.edu” to whomever in the Computer Science department is designated for the task.


Previous Topic/Section
DNS Public Registration Disputes (Conflicts, Cybersquatting, "Deceptive Naming", Etc.) and Dispute Resolution
Previous Page
Pages in Current Topic/Section
1
23
Next Page
DNS Private Name Registration
Next Topic/Section

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!
Donate $2
Donate $5
Donate $10
Donate $20
Donate $30
Donate: $



Home - 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.