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

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

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

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

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

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

TSIG : Transaction Signature (RFC 2845)
Record that supports one set of security mechanisms for DNS. Used to secure communication between DNS resolvers and Name servers, in contrast to DNSSEC, which secures the actual DNS records from the authoritative name server.

SRV : Service locator (RFC 2782)
Generalized service location record, used for newer protocols instead of creating protocol-specific records such as MX.

CERT : Certificate record (RFC 4398)
Stores PKIX, SPKI, PGP, 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.

SOA : start of authority record (RFC 1035)
Specifies authoritative information about a DNS zone, including the primary name server, the email of the domain administrator, the domain serial number, and several timers relating to refreshing the zone.

DLV : DNSSEC Lookaside Validation record (RFC 4431)
For publishing DNSSEC trust anchors outside of the DNS delegation chain. Uses the same format as the DS record. RFC 5074 describes a way of using these records.

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.

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

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

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.

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.