📄 00000005.htm
字号:
the user. <BR> <BR>From the resolver's point of view, the database that makes up the domain <BR>space is distributed among various name servers. Different parts of the <BR>domain space are stored in different name servers, although a particular <BR>data item will be stored redundantly in two or more name servers. The <BR>resolver starts with knowledge of at least one name server. When the <BR>resolver processes a user query it asks a known name server for the <BR>information; in return, the resolver either receives the desired <BR>information or a referral to another name server. Using these <BR>referrals, resolvers learn the identities and contents of other name <BR>servers. Resolvers are responsible for dealing with the distribution of <BR>the domain space and dealing with the effects of name server failure by <BR>consulting redundant databases in other servers. <BR> <BR>Name servers manage two kinds of data. The first kind of data held in <BR>sets called zones; each zone is the complete database for a particular <BR>"pruned" subtree of the domain space. This data is called <BR>authoritative. A name server periodically checks to make sure that its <BR>zones are up to date, and if not, obtains a new copy of updated zones <BR> <BR> <BR> <BR>Mockapetris [Page 3] <BR> <BR>RFC 1035 Domain Implementation and Specification November 1987 <BR> <BR> <BR>from master files stored locally or in another name server. The second <BR>kind of data is cached data which was acquired by a local resolver. <BR>This data may be incomplete, but improves the performance of the <BR>retrieval process when non-local data is repeatedly accessed. Cached <BR>data is eventually discarded by a timeout mechanism. <BR> <BR>This functional structure isolates the problems of user interface, <BR>failure recovery, and distribution in the resolvers and isolates the <BR>database update and refresh problems in the name servers. <BR> <BR>2.2. Common configurations <BR> <BR>A host can participate in the domain name system in a number of ways, <BR>depending on whether the host runs programs that retrieve information <BR>from the domain system, name servers that answer queries from other <BR>hosts, or various combinations of both functions. The simplest, and <BR>perhaps most typical, configuration is shown below: <BR> <BR> Local Host | Foreign <BR> | <BR> +---------+ +----------+ | +--------+ <BR> | | user queries | |queries | | | <BR> | User |-------------->| |---------|->|Foreign | <BR> | Program | | Resolver | | | Name | <BR> | |<--------------| |<--------|--| Server | <BR> | | user responses| |responses| | | <BR> +---------+ +----------+ | +--------+ <BR> | A | <BR> cache additions | | references | <BR> V | | <BR> +----------+ | <BR> | cache | | <BR> +----------+ | <BR> <BR>User programs interact with the domain name space through resolvers; the <BR>format of user queries and user responses is specific to the host and <BR>its operating system. User queries will typically be operating system <BR>calls, and the resolver and its cache will be part of the host operating <BR>system. Less capable hosts may choose to implement the resolver as a <BR>subroutine to be linked in with every program that needs its services. <BR>Resolvers answer user queries with information they acquire via queries <BR>to foreign name servers and the local cache. <BR> <BR>Note that the resolver may have to make several queries to several <BR>different foreign name servers to answer a particular user query, and <BR>hence the resolution of a user query may involve several network <BR>accesses and an arbitrary amount of time. The queries to foreign name <BR>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -