CNAME : Canonical name record (RFC 1035)
Alias of one name to another: the DNS lookup will continue by retrying the lookup with the new name.

OPT : Option (RFC 2671)
This is a 'pseudo DNS record type' needed to support EDNS

SSHFP : SSH Public Key Fingerprint (RFC 4255)
Resource record for publishing SSH public host key fingerprints in the DNS System, in order to aid in verifying the authenticity of the host.

NAPTR : Naming Authority Pointer (RFC 3403)
Allows regular expression based rewriting of domain names which can then be used as URIs, further domain names to lookups, etc.

DNAME : delegation name (RFC 2672)
DNAME will delegate an entire portion of the DNS tree under a new name. In contrast, the CNAME record creates an alias of a single name. Like the CNAME record, the DNS lookup will continue by retrying the lookup with the new name.

LOC : Location record (RFC 1876)
Specifies a geographical location associated with a domain name

NS : name server record (RFC 1035)
Delegates a DNS zone to use the given authoritative name servers

RRSIG : DNSSEC signature (RFC 4034)
Signature for a DNSSEC-secured record set. Uses the same format as the SIG record.

NSEC3 : NSEC record version 3 (RFC 5155)
An extension to DNSSEC that allows proof of nonexistence for a name without permitting zonewalking

NSEC : Next-Secure record (RFC 4034)
Part of DNSSEC—used to prove a name does not exist. Uses the same format as the (obsolete) NXT record.

CERT : Certificate record (RFC 4398)
Stores PKIX, SPKI, PGP, etc.

TXT : Text record (RFC 1035)
Originally for arbitrary human-readable text in a DNS record. Since the early 1990s, however, this record more often carries machine-readable data, such as specified by RFC 1464, opportunistic encryption, Sender Policy Framework, DomainKeys, DNS-SD, etc.

KEY : Key record (RFC 4034)
Used only for TKEY (RFC 2930). Before RFC 3755 was published, this was also used for DNSSEC, but DNSSEC now uses DNSKEY.

* : All cached records (RFC 1035)
Returns all records of all types known to the name server. If the name server does not have any information on the name, the request will be forwarded on. The records returned may not be complete. For example, if there is both an A and an MX for a name, but the name server has only the A record cached, only the A record will be returned.

SPF : SPF record (RFC 4408)
Specified as part of the SPF protocol, as an alternative to storing SPF data in TXT records. Uses the same format as the TXT record.

IXFR : Incremental Zone Transfer (RFC 1995)
Requests a zone transfer of the given zone but only differences from a previous serial number. This request may be ignored and a full (AXFR) sent in response if the authoritative server is unable to fulfill the request due to configuration or lack of required deltas.

IPSECKEY : IPSEC Key (RFC 4025)
Key record that can be used with IPSEC

HIP : Host Identity Protocol (RFC 5205)
Method of separating the end-point identifier and locator roles of IP addresses.