Returns a 32-bit IPv4 address, most commonly used to map hostnames to an IP address of the host, but it is also used for DNSBLs, storing subnet masks in RFC 1101, etc.
Returns a 128-bit IPv6 address, most commonly used to map hostnames to an IP address of the host.
Location of database servers of an AFS cell. This record is commonly used by AFS clients to contact AFS cells outside their local domain. A subtype of this record is used by the obsolete DCE/DFS file system.
Specify lists of address ranges, e.g. in CIDR format, for various address families. Experimental.
DNS Certification Authority Authorization, constraining acceptable CAs for a host/domain
Child copy of DNSKEY record, for transfer to parent
Child copy of DS record, for transfer to parent
Stores PKIX, SPKI, PGP, etc.
Alias of one name to another: the DNS lookup will continue by retrying the lookup with the new name.
Used in conjunction with the FQDN option to DHCP
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.
Alias for a name and all its subnames, unlike CNAME, which is an alias for only the exact name. Like a CNAME record, the DNS lookup will continue by retrying the lookup with the new name.
The key record used in DNSSEC. Uses the same format as the KEY record.
The record used to identify the DNSSEC signing key of a delegated zone
Method of separating the end-point identifier and locator roles of IP addresses.
Key record that can be used with IPsec
Used only for SIG(0) (RFC 2931) and TKEY (RFC 2930).[5]RFC 3445 eliminated their use for application keys and limited their use to DNSSEC.[6]RFC 3755 designates DNSKEY as the replacement within DNSSEC.[7]RFC 4025 designates IPSECKEY as the replacement for use with IPsec.[8]
Used with some cryptographic systems (not including DNSSEC) to identify a key management agent for the associated domain-name.  Note that this has nothing to do with DNS Security.  It is Informational status, rather than being on the IETF standards-track.  It has always had limited deployment, but is still in use.
Specifies a geographical location associated with a domain name
Maps a domain name to a list of message transfer agents for that domain
Allows regular-expression-based rewriting of domain names which can then be used as URIs, further domain names to lookups, etc.
Delegates a DNS zone to use the given authoritative name servers
Part of DNSSEC—used to prove a name does not exist. Uses the same format as the (obsolete) NXT record.
An extension to DNSSEC that allows proof of nonexistence for a name without permitting zonewalking
Parameter record for use with NSEC3
A DNS-based Authentication of Named Entities (DANE) method for publishing and locating OpenPGP public keys in DNS for a specific email address using an OPENPGPKEY DNS resource record.
Pointer to a canonical name. Unlike a CNAME, DNS processing stops and just the name is returned.  The most common use is for implementing reverse DNS lookups, but other uses include such things as DNS-SD.
Signature for a DNSSEC-secured record set. Uses the same format as the SIG record.
Information about the responsible person(s) for the domain. Usually an email address with the @ replaced by a .
Signature record used in SIG(0) (RFC 2931) and TKEY (RFC 2930).[7]RFC 3755 designated RRSIG as the replacement for SIG for use within DNSSEC.[7]
Associates an S/MIME certificate with a domain name for sender authentication.
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.
Generalized service location record, used for newer protocols instead of creating protocol-specific records such as MX.
Resource record for publishing SSH public host key fingerprints in the DNS System, in order to aid in verifying the authenticity of the host. RFC 6594 defines ECC SSH keys and SHA-256 hashes. See the IANA SSHFP RR parameters registry for details.
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.
A method of providing keying material to be used with TSIG that is encrypted under the public key in an accompanying KEY RR.[12]
A record for DANE. RFC 6698 defines "The TLSA DNS resource record is used to associate a TLS server certificate or public key with the domain name where the record is found, thus forming a 'TLSA certificate association'".
Can be used to authenticate dynamic updates as coming from an approved client, or to authenticate responses as coming from an approved recursive name server[13] similar to DNSSEC.
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, DKIM, DMARC, DNS-SD, etc.
Can be used for publishing mappings from hostnames to URIs.