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.
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:
- It can be the master name server for more than
one zone. Each zone in this case has a distinct set of resource records
maintained in separate master files.
- It can be a slave name server for more than one
- It can be a slave name server for certain zones
as well as a primary for others.
Note however that a single physical
name server cannot be a primary and a secondary server for the same
well, what would be the point?
Key Concept: The master DNS server for a zone is its primary server, which maintains the master copy of DNS information. Most DNS zones also have at least one slave or secondary DNS server. These are important because they serve as backups for the primary server, and they can also help share the load of responding to requests in busy zones. Secondary name servers get their information from primary servers on a routine basis. Both master and slave servers are considered authoritative for the zones whose data they maintain.
Caching-Only Name Servers
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
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.
Key Concept: There are DNS servers that do not maintain DNS resource records of their own but solely hold recently-used information from other zones. These are called caching-only name servers and are not authoritative for any zone.
|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!|
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.