search
Click on the red underlined text to get to the source
... Relative names are either taken relative to a well known origin, or to a
list of domains used as a search list. Relative names appear mostly at
the user interface, where their interpretation varies from
...
... uses the root "." as either the single origin or as one of the members
of the search list, so a multi-label relative name is often one where
the trailing dot has been omitted to save typing.
...
...
Search the available zones for the zone which is the nearest
ancestor to QNAME. If such a zone is found, go to step 3,
otherwise step 4.
...
...
This feature can be particularly important in a system which implements
naming shorthands that use search lists beacuse a popular shorthand,
which happens to require a suffix toward the end of the search ...
... search lists beacuse a popular shorthand,
which happens to require a suffix toward the end of the search list,
will generate multiple name errors whenever it is used.
...
... the QTYPE of the search request. ...
... the QCLASS of the search request. ...
... old RRs when it runs across them in the course of a
search, or discards them during periodic sweeps to
reclaim the memory consumed by old RRs. ...
... 4. Get the answer as quickly as possible.
If the search for NS RRs fails, then the resolver initializes SLIST from
...
... address RRs for the servers should be cached.
The name servers are entered in the SLIST, and the search is restarted.
If the response contains a CNAME ...
...
If the response contains a CNAME, the search is restarted at the CNAME
unless the response has the data for the canonical ...
... needed to query foreign servers and try to determine the best servers to
query. This search would look for NS RRs for the domains ...