RFC 1034:DOMAIN NAMES - CONCEPTS AND FACILITIES
RFC-Ref

start


Click on the red underlined text to get to the source

... a character string that represents the starting labels of a domain name which is incomplete, and should be completed by ...
... The labels must follow the rules for ARPANET host names. They must start with a letter, end with a letter or digit, and have as interior characters only letters, digits, and hyphen. There are also some restrictions on the length. Labels must be 63 characters or less. ...
... identifies the start of a zone of authority] ...
... The start of the line gives the owner of the RR. If a line begins with a blank, then the owner is assumed to be the same as that of the ...


... Start matching down, label by label, in the zone. The matching process can terminate several ways: ...
... Start matching down in the cache. If QNAME is found in the cache ...
... algorithm, special treatment was given to RRs with owner names starting with the label "*". Such RRs are called wildcards. ...


... general strategy is to look for locally-available name server RRs, starting at SNAME, then the parent domain name of SNAME, the grandparent, and so on toward the root ...
... be the case that the addresses are not available. The resolver has many choices here; the best is to start parallel resolver processes looking for the addresses ...
... 1. Bound the amount of work (packets sent, parallel processes started) so that a request can't get into an infinite loop or start off a chain reaction of requests or queries with other implementations EVEN IF SOMEONE HAS INCORRECTLY CONFIGURED ...


... single line entries; the sole exception here is the SOA RR, which uses "(" to start a multi-line RR and ")" to show the end of a multi-line RR. ...
... The following examples illustrate the operations a resolver must perform for its client. We assume that the resolver is starting without a cache, as might be the case after system boot. We further assume that the system is not one of the ...
... A.ISI.EDU appears on this list as well as the previous one, but that is purely coincidental. The resolver would again start transmitting and waiting for responses. Eventually it would get an answer: ...



Google
Web
RFC-Ref