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!

Enjoy The TCP/IP Guide? Get the complete PDF!
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 Space, Architecture and Terminology

Previous Topic/Section
DNS Name Space, Architecture and Terminology
Previous Page
Pages in Current Topic/Section
1
23
Next Page
DNS Structural Elements and Terminology: Domains, Subdomains, and Nodes; Roots, Leaves and Branches; Parents, Children and Siblings
Next Topic/Section

DNS Domains and the DNS Hierarchical Name Architecture
(Page 1 of 3)

The most important element of a name system's name space is its name architecture, which describes how names are constructed and interpreted. The architecture of the Domain Name System is, unsurprisingly, based on the concept of an abstraction called a domain. This is obviously a good place to start in explaining how DNS works. Unfortunately, it's not the easiest concept to explain from scratch, so as usual, I'll do my best and ask for your patience. J

The Essential Concept in the DNS Name Space: Domains

Dictionary definitions of the word “domain” generally convey the notion of a sphere of influence, or area of control or rulership. An essential concept is that in many different contexts, control or authority can be exerted at many different levels. One sphere of influence may contain smaller ones, which can in turn contain smaller ones still. This means that such domains are naturally arranged in a hierarchy.

An obvious example would be geopolitical domains. We have no centralized “world government” on earth, but we do have the United Nations, which deals with world-wide issues. At the next level down, we have individual countries. Some of these countries have divisions such as states and provinces. Still lower levels have counties, municipalities, neighborhoods and individual residences or businesses. The “domains” are inherently hierarchical in organization.

The Domain Name System uses the word domain in a manner very similar to this, and employs a hierarchical structure that works in much the same way as the geopolitical example. In DNS, a domain is defined as either a single object or a set of objects that have been collected together based on some type of commonality. Usually in DNS that commonality is that they are all administered by the same organization or authority, which makes the name hierarchy tightly linked to the notion of the DNS hierarchical authority structure.

Note: The term “domain” is also used in other contexts in the world of networking. The most notable example of this is the use of the term in Microsoft networking, where it too is used to represent the notion of a collection of objects under common authority. However, the two types of domain are completely different and not related beyond this conceptual level.



Previous Topic/Section
DNS Name Space, Architecture and Terminology
Previous Page
Pages in Current Topic/Section
1
23
Next Page
DNS Structural Elements and Terminology: Domains, Subdomains, and Nodes; Roots, Leaves and Branches; Parents, Children and Siblings
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.