Free Trial

Safari Books Online is a digital library providing on-demand subscription access to thousands of learning resources.

Share this Page URL
Help

4.4 Case Study: The Internet Domain Name... > 4.4.3 Other Features of DNS - Pg. 181

4.4 Case Study: The Internet Domain Name System (DNS) 181 address of the pedantic.edu name server. Now, if Pedantic University wants to add a record, for example, for an Internet address that it wishes to name archimedes. pedantic.edu , its administrator can do so without asking permission of anyone else. A request to resolve the name archimedes.pedantic.edu can arrive at any domain name server in the Internet; that request will eventually arrive at the name server for the pedantic.edu domain, where it can be answered correctly. Similarly, a network administrator at the Institute for Scholarly Studies can install a name record for an Internet address named archimedes.Scholarly.edu on its own authority. Although both institutions have chosen the name archimedes for one of their com- puters, because the path names of the domains are distinct there was no need for their administrators to coordinate their name assignments. Put another way, their nam- ing authorities can act independently. Continuing this method of decentralization, any organization that manages a name server can create lower-level naming domains. For example, the Computer Science and Engineering Department of Pedantic University may have so many computers that it is convenient for the department to manage the names of those computers itself. All that is necessary is for the department to deploy a name server for a lower-level domain (named, for example, cse.pedantic.edu ) and convince the administrator of the