From 8821260cc937b3ba843cfa99037bd351a1e9e90e Mon Sep 17 00:00:00 2001 From: Chern Lee Date: Mon, 6 Aug 2001 22:50:16 +0000 Subject: [PATCH] Reworded sections of "Reasons to run a name server" and changed definition of "Origin" in DNS section. Reviewed by: murray --- .../handbook/advanced-networking/chapter.sgml | 113 ++++++++---------- 1 file changed, 49 insertions(+), 64 deletions(-) diff --git a/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml b/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml index b440520773..454acd28b5 100644 --- a/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml @@ -1,7 +1,7 @@ @@ -3023,7 +3023,8 @@ dhcp_flags="" origin - refers to the point of start for the particular zone + refers to the domain covered for the particular zone + file @@ -3106,69 +3107,53 @@ dhcp_flags="" Reasons to run a name server - - - - A machine is needed to host DNS information to the world - - - - An authoritative nameserver replies exclusively - to requests. - - - - For example, foobardomain.org is - registered and IP addresses need to be assigned to hostnames - under this domain. - - - - A slave nameserver, which replies to queries for a - domain when the primary is down or inaccessible. - - - - The above two can also be done with reverse DNS (IP - to hostname entries) - - - - - - - A machine is needed to act as a local cache of DNS information - - - - DNS traffic has been measured to be about 5% or more - of the total Internet traffic. - - - - A local DNS server may have some added benefit by - providing a local cache of DNS information. - - - - - For example, when one queries for - www.freebsd.org, - the resolver usually queries the uplink ISP's name - server, and retrieves the query. - - - - - With a local, caching DNS server, the query only has to - be made once to the outside world. Every additional - query will not have to look to the outside of the local - network, since the information is cached. - - - - + + Name servers usually come in two forms: an authoritative + name server, and a caching nameserver. + + An authoritative name server is needed when: + + + + one wants to serve DNS information to the + world, replying authoritatively to queries. + + + a domain, such as foobardomain.org, is + registered and IP addresses need to be assigned to hostnames + under it. + + + an IP address block requires reverse DNS entries (IP to + hostname). + + + a backup name server, called a slave, must reply to queries + when the primary is down or inaccessible. + + + A caching name server is needed when: + + + + a local DNS server may cache and respond more quickly + then querying an outside name server. + + + a reduction in overall network traffic is desired. (DNS + traffic has been measured to account for 5% or more of total + Internet traffic) + + + + When one queries for www.freebsd.org, the + resolver usually queries the uplink ISP's name server, and retrieves + the reply. With a local, caching DNS server, the query only has to + be made once to the outside world by the caching DNS server. Every + additional query will not have to look to the outside of the local + network, since the information is cached locally. +