| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
DNS Name Server Types and Roles: Primary/Master, Secondary/Slave and Caching-Only Servers (Page 3 of 3) Name Server Roles The master and slave roles for a zone are logical and do not always correspond to individual physical hardware devices. A single physical name server can play multiple roles in the following cases:
Note however that a single physical name server cannot be a primary and a secondary server for the same zone, since well, what would be the point?
We'll see later in this section that for efficiency reasons, all DNS servers perform caching of DNS information so it can be used again if requested in the near future. This includes both master and slave name servers. The importance of caching is so significant that there are some servers that are set up only to cache information from other DNS servers. Unsurprisingly, these are called caching-only name servers. These name servers are not authoritative for any zone or domain, and don't maintain any resource records of their own. They can only answer name resolution requests by contacting other name servers that are authoritative and then relaying the information. They then store the information for future requests. Why bother? The reason is performance. Through strategic placement, a caching-only server can increase DNS resolution performance substantially in some networks by cutting down on requests to authoritative servers.
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. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||