List of DNS record types

Table columns:
Type
Type id. (decimal)
Defining RFC
Description
Function

Table rows:
cells: A
1
RFC 1035[1]
Address record
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.
cells: AAAA
28
RFC 3596[2]
IPv6 address record
Returns a 128-bit IPv6 address, most commonly used to map hostnames to an IP address of the host.
cells: AFSDB
18
RFC 1183
AFS database record
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.
cells: APL
42
RFC 3123
Address Prefix List
Specify lists of address ranges, e.g. in CIDR format, for various address families. Experimental.
cells: CAA
257
RFC 6844
Certification Authority Authorization
DNS Certification Authority Authorization, constraining acceptable CAs for a host/domain
cells: CDNSKEY
60
RFC 7344
Child DNSKEY
Child copy of DNSKEY record, for transfer to parent
cells: CDS
59
RFC 7344
Child DS
Child copy of DS record, for transfer to parent
cells: CERT
37
RFC 4398
Certificate record
Stores PKIX, SPKI, PGP, etc.
cells: CNAME
5
RFC 1035[1]
Canonical name record
Alias of one name to another: the DNS lookup will continue by retrying the lookup with the new name.
cells: DHCID
49
RFC 4701
DHCP identifier
Used in conjunction with the FQDN option to DHCP
cells: DLV
32769
RFC 4431
DNSSEC Lookaside Validation record
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.
cells: DNAME
39
RFC 6672
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.
cells: DNSKEY
48
RFC 4034
DNS Key record
The key record used in DNSSEC. Uses the same format as the KEY record.
cells: DS
43
RFC 4034
Delegation signer
The record used to identify the DNSSEC signing key of a delegated zone
cells: HIP
55
RFC 8005
Host Identity Protocol
Method of separating the end-point identifier and locator roles of IP addresses.
cells: IPSECKEY
45
RFC 4025
IPsec Key
Key record that can be used with IPsec
cells: KEY
25
RFC 2535[3] and RFC 2930[4]
Key record
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]
cells: KX
36
RFC 2230
Key Exchanger record
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.
cells: LOC
29
RFC 1876
Location record
Specifies a geographical location associated with a domain name
cells: MX
15
RFC 1035[1] and RFC 7505
Mail exchange record
Maps a domain name to a list of message transfer agents for that domain
cells: NAPTR
35
RFC 3403
Naming Authority Pointer
Allows regular-expression-based rewriting of domain names which can then be used as URIs, further domain names to lookups, etc.
cells: NS
2
RFC 1035[1]
Name server record
Delegates a DNS zone to use the given authoritative name servers
cells: NSEC
47
RFC 4034
Next Secure record
Part of DNSSEC—used to prove a name does not exist. Uses the same format as the (obsolete) NXT record.
cells: NSEC3
50
RFC 5155
Next Secure record version 3
An extension to DNSSEC that allows proof of nonexistence for a name without permitting zonewalking
cells: NSEC3PARAM
51
RFC 5155
NSEC3 parameters
Parameter record for use with NSEC3
cells: OPENPGPKEY
61
RFC 7929
OpenPGP public key record
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.
cells: PTR
12
RFC 1035[1]
Pointer 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.
cells: RRSIG
46
RFC 4034
DNSSEC signature
Signature for a DNSSEC-secured record set. Uses the same format as the SIG record.
cells: RP
17
RFC 1183
Responsible Person
Information about the responsible person(s) for the domain. Usually an email address with the @ replaced by a .
cells: SIG
24
RFC 2535
Signature
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]
cells: SOA
6
RFC 1035[1] and RFC 2308[9]
Start of [a zone of] authority record
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.
cells: SRV
33
RFC 2782
Service locator
Generalized service location record, used for newer protocols instead of creating protocol-specific records such as MX.
cells: SSHFP
44
RFC 4255
SSH Public Key Fingerprint
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.
cells: TA
32768
N/A
DNSSEC Trust Authorities
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.
cells: TKEY
249
RFC 2930
Transaction Key record
A method of providing keying material to be used with TSIG that is encrypted under the public key in an accompanying KEY RR.[10]
cells: TLSA
52
RFC 6698
TLSA certificate association
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'".
cells: TSIG
250
RFC 2845
Transaction Signature
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[11] similar to DNSSEC.
cells: TXT
16
RFC 1035[1]
Text record
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.
cells: URI
256
RFC 7553
Uniform Resource Identifier
Can be used for publishing mappings from hostnames to URIs.

Questions about this table:
originalText: which record type on a dns server represents an ipv6 host
answer: answerTexts: AAAA