dido:public:ra:xapend:xapend.b_stds:tech:ietf:1035
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:ra:xapend:xapend.b_stds:tech:ietf:1035 [2019/06/03 19:53] nick |
dido:public:ra:xapend:xapend.b_stds:tech:ietf:1035 [2021/08/17 13:25] (current) murphy |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ======== RFC1035 - Domain Names - Implementation and Specification ========= | + | ===== RFC1035 - Domain Names - Implementation and Specification ===== |
| - | [[dido:public:stds:tech:ietf | return to the IETF Standards ]] | + | [[dido:public:ra:xapend:xapend.b_stds:tech:ietf:start| return to the IETF Standards ]] |
| <table> | <table> | ||
| Line 12: | Line 12: | ||
| </table> | </table> | ||
| - | : **Note**: The following is an excerpt from the official IETF RFC. It is provided here as a connivence and is not authoritative. Refer to the original document as the authoritative reference. | + | : **Note**: The following is an excerpt from the official IETF RFC. It is provided here as a convenience and is not authoritative. Refer to the original document as the authoritative reference. |
| - | + | ==== Introduction ==== | |
| - | ====== Introduction ====== | + | : //The [[dido:public:ra:xapend:xapend.a_glossary:g:goal|goal]] of domain names is to provide a mechanism for naming resources |
| - | : //The goal of domain names is to provide a mechanism for naming resources | + | |
| in such a way that the names are usable in different hosts, networks, | in such a way that the names are usable in different hosts, networks, | ||
| protocol families, internets, and administrative organizations.// | protocol families, internets, and administrative organizations.// | ||
| Line 27: | Line 26: | ||
| query type is passed to the resolver with the domain name. To the user, | query type is passed to the resolver with the domain name. To the user, | ||
| the domain tree is a single information space; the resolver is | the domain tree is a single information space; the resolver is | ||
| - | responsible for hiding the distribution of data among name servers from | + | responsible for hiding the distribution of data among name [[dido:public:ra:xapend:xapend.a_glossary:s:server|servers]] from |
| the user.// | the user.// | ||
| Line 50: | Line 49: | ||
| from master files stored locally or in another name server. The second | from master files stored locally or in another name server. The second | ||
| kind of data is cached data which was acquired by a local resolver. | kind of data is cached data which was acquired by a local resolver. | ||
| - | This data may be incomplete, but improves the performance of the | + | This data may be incomplete, but improves the [[dido:public:ra:xapend:xapend.a_glossary:p:performance|performance]] of the |
| retrieval process when non-local data is repeatedly accessed. Cached | retrieval process when non-local data is repeatedly accessed. Cached | ||
| data is eventually discarded by a timeout mechanism.// | data is eventually discarded by a timeout mechanism.// | ||
| - | : //This functional structure isolates the problems of user interface, | + | : //This functional structure isolates the problems of user [[dido:public:ra:xapend:xapend.a_glossary:i:interface|interface]], |
| failure recovery, and distribution in the resolvers and isolates the | failure recovery, and distribution in the resolvers and isolates the | ||
| database update and refresh problems in the name servers.// | database update and refresh problems in the name servers.// | ||
| + | |||
| + | /**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | ||
| + | /* To add a discussion page to this page, comment out the line that says | ||
| + | ~~DISCUSSION:off~~ | ||
| + | */ | ||
| + | ~~DISCUSSION:on|Outstanding Issues~~ | ||
| + | ~~DISCUSSION:off~~ | ||
dido/public/ra/xapend/xapend.b_stds/tech/ietf/1035.1559606030.txt.gz · Last modified: 2019/06/03 19:53 by nick
