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.

A : address record (RFC 1035)
Returns a 32-bit IPv4 address, most commonly used to map hostnames to an IP address of the host, but also used for DNSBLs, storing subnet masks in RFC 1101, etc.

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

AAAA : IPv6 address record (RFC 3596)
Returns a 128-bit IPv6 address, most commonly used to map hostnames to an IP address of the host.

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

DHCID : DHCP identifier (RFC 4701)
Used in conjunction with the FQDN option to DHCP

TKEY : Transaction Key (RFC 2930)
One way of providing a key to be used with TSIG

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.

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.

TA : DNSSEC Trust Authorities (None)
Part of a deployment proposal for DNSSEC without a signed DNS root. See the IANA database and Weiler Spec] for details. Uses the same format as the DS record.

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.

DNSKEY : DNS Key record (RFC 4034)
The key record used in DNSSEC. Uses the same format as the KEY record.

NSEC3PARAM : NSEC3 parameters (RFC 5155)
Parameter record for use with NSEC3

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.

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

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.

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.

DS : Delegation signer (RFC 4034)
The record used to identify the DNSSEC signing key of a delegated zone