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!

The whole site in one document for easy reference!
The TCP/IP Guide

Google
Web TCP/IP Guide






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 Servers and Name Resolution
                          9  DNS Name Server Concepts and Operation

Previous Topic/Section
DNS Name Server Data Storage: Resource Records and Classes
Previous Page
Pages in Current Topic/Section
1
23
Next Page
DNS Zone Management, Contacts and Zone Transfers
Next Topic/Section

DNS Name Server Types and Roles: Primary/Master, Secondary/Slave and Caching-Only Servers
(Page 1 of 3)

In the first two topics in this section, we have looked at the functions of DNS servers, with a particular eye to the important job of storing name server information. There are many thousands of DNS servers on the Internet, and not all are used in the same way. Each DNS server has a particular role in the overall operation of the name system. The different kinds of servers also interact with each other in a variety of ways that we need to understand.

Every zone needs to have at least one DNS name server that is responsible for it. These DNS name servers are called authoritative servers for the zone, because they contain the full set of resource records that describe the zone. When any device on the Internet wants to know something about a zone, it consults one of its authoritative servers.

From a strictly theoretical perspective, having one name server for each zone or domain is “sufficient” to provide name resolution services for the entire DNS name structure. From an implementation standpoint, however, having only one name server for each part of the name space is not a wise idea. Instead, each zone usually has associated with it at least two name servers: one primary or master name server, and one secondary or slave name servers. Some zones may have more than one secondary name server.

Note: The terms “primary” and “secondary” are used often in the DNS standards to refer to the roles of the two authoritative servers for a zone. However, “master” and “slave” are now the preferred terms, because “primary” and “secondary” are somewhat ambiguous and used in other contexts. You should be prepared to see both terms used.



Previous Topic/Section
DNS Name Server Data Storage: Resource Records and Classes
Previous Page
Pages in Current Topic/Section
1
23
Next Page
DNS Zone Management, Contacts and Zone Transfers
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.