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

alias


Click on the red underlined text to get to the source

... identifies the canonical name of an alias ...
... Aliases and canonical names ...
... Most of these systems have a notion that one of the equivalent set of names is the canonical or primary name and all others are aliases. ...
... RR. A CNAME RR identifies its owner name as an alias, and specifies the corresponding canonical name in the RDATA ...
... node, no other data should be present; this ensures that the data for a canonical name and its aliases cannot be different. This rule also insures that a cached CNAME can be ...
... Domain names in RRs which point at another name should always point at the primary name and not the alias. This avoids extra indirections in accessing information. For example, the address to name RR ...


... CNAME RRs that specify aliases encountered on the way to an answer. ...
... RRs that indicate that the original query name was an alias for a name which does not exist. ...


... Aliases ...
... While attempting to resolve a particular request, the resolver may find that the name in question is an alias. For example, the resolver might find that the name given for host name to address ...
... find that the name given for host name to address translation is an alias when it finds the CNAME RR. If possible, the alias ...
... alias when it finds the CNAME RR. If possible, the alias condition should be signalled back from the resolver to the client. ...
... it encounters a CNAME. However, when performing the general function, the resolver should not pursue aliases when the CNAME RR matches the ...
... matches the query type. This allows queries which ask whether an alias is present. For example, if the query type is CNAME ...
... Several special conditions can occur with aliases. Multiple levels of aliases should be avoided due to their lack of efficiency, but should not be signalled as an error. ...
... Several special conditions can occur with aliases. Multiple levels of aliases should be avoided due to their lack of efficiency, but should not be signalled as an error. Alias loops and aliases ...
... . Multiple levels of aliases should be avoided due to their lack of efficiency, but should not be signalled as an error. Alias loops and aliases which point to non-existent names should be caught and an error condition ...
... aliases should be avoided due to their lack of efficiency, but should not be signalled as an error. Alias loops and aliases which point to non-existent names should be caught and an error condition passed back ...


... This reply contains an authoritative reply for the alias USC-ISIC.ARPA, plus a referral to the name servers for ISI.EDU. This sort of reply ...
... query is for the host name of the name server being asked, but would be common for other aliases. ...



Google
Web
RFC-Ref