RFC 3597:Handling of Unknown DNS Resource Record (...
RFC-Ref

class


Click on the red underlined text to get to the source

... In the case of a type whose RDATA format is class specific, an RR is considered to be of unknown type when the RDATA format ...
... considered to be of unknown type when the RDATA format for that combination of type and class is not known. ...


... domain names embedded in the RDATA of types that are class-specific or not well- known. This requirement was stated in [RFC1123 ...


... represented by the word "TYPE" immediately followed by the decimal RR type number, with no intervening whitespace. In the "class" field, an unknown class is similarly represented as the word "CLASS ...
... type number, with no intervening whitespace. In the "class" field, an unknown class is similarly represented as the word "CLASS" immediately followed by the decimal class number ...
... class" field, an unknown class is similarly represented as the word "CLASS" immediately followed by the decimal class number. ...
... class is similarly represented as the word "CLASS" immediately followed by the decimal class number. This convention allows types and classes ...
... class number. This convention allows types and classes to be distinguished from each other and from TTL values, allowing the "[<TTL ...
... each other and from TTL values, allowing the "[<TTL>] [<class>] <type> <RDATA>" and "[<class ...
... class>] <type> <RDATA>" and "[<class>] [<TTL>] <type> <RDATA>" forms of ...
... An implementation MAY also choose to represent some RRs of known type using the above generic representations for the type, class and/or RDATA, which carries the benefit of making the resulting master file ...



Google
Web
RFC-Ref