DNS : Constants


DNS : Ressource Record (RR) Types

The TYPE field identifies what kind of data the record contains and how the RDATA field should be interpreted. It is one of the key fields in every DNS record. The size of Type field is 2 octets.

TYPEMS ConstantDescriptionDECHEXReferenceUsage
ADNS_TYPE_AIP4 address10x0001RFC1035Used to map hostname to an IP address of the host.
Also used for DNSBL1, storing subnet masks 
NSDNS_TYPE_NSName Server20x0002RFC1035Nameservers responsible for managing a domain’s DNS data
MDDNS_TYPE_MDMail Destination30x0003RFC1035(OBSOLETE – use MX)
MFDNS_TYPE_MFMail Forwarder40x0004RFC1035(OBSOLETE – use MX)
CNAMEDNS_TYPE_CNAMECanonical Name50x0005RFC1035Alias of one name to another.
DNS lookup will continue by retrying the lookup with the new name.
SOADNS_TYPE_SOAStart of Authority60x0006RFC1035Authoritative information of 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.
MBDNS_TYPE_MBMailbox70x0007RFC1035Experimental
MGDNS_TYPE_MGMailgroup Member80x0008RFC1035Experimental
MRDNS_TYPE_MRMail Rename90x0009RFC1035Experimental
NULLDNS_TYPE_NULLNULL100x000aRFC1035Experimental
WKSDNS_TYPE_WKSWell-known Service110x000bRFC1035Record to describe well-known services supported by a host.
Not used in practice.
PTRDNS_TYPE_PTRPointer RR120x000cRFC1035Common usage is for implementing reverse DNS lookups.
HINFODNS_TYPE_HINFOPlaceholder record, or host information130x000dRFC1035
RFC8042
Repurposed to be used while responding to ANY queries. Originally defined as “Host information”, intended to inform about host’s operating system and hardware. RFC 8482 did not obsolete this conventional meaning for explicit HINFO queries, but rather considers it rarely used.
MINFODNS_TYPE_MINFOMailbox or mail list information140x000eRFC1035Experimental
MXDNS_TYPE_MXMail exchange record150x000fRFC1035
RFC7505
List of mail exchange servers that accept email for a domain
TXTDNS_TYPE_TEXTText record160x0010RFC1035Originally 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 encryptionSender Policy FrameworkDKIMDMARCDNS-SD, etc.
RPDNS_TYPE_RPResponsible Person170x0011RFC1183Information about the responsible person(s) for the domain. Usually an email address with the @ replaced by a .
AFSDBDNS_TYPE_AFSDBAFS database record180x0012RFC1183Location 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.
X25DNS_TYPE_X25For security key190x0013RFC1183Not in current use by any notable application
ISDNDNS_TYPE_ISDNFor ISDN address200x0014RFC1183Not in current use by any notable application
RTDNS_TYPE_RTFor Route Through210x0015RFC1183Not in current use by any notable application
NSAPDNS_TYPE_NSAPFor NSAP address, NSAP style A record220x0016RFC1706DEPRECATED
NSA-PPTRDNS_TYPE_NSAPPTRFor domain name pointer, NSAP style230x0017RFC1706DEPRECATED
SIGDNS_TYPE_SIGFor security signature240x0018RFC2536
RFC2931
RFC3110
RFC4034
Signature record used in SIG(0) (RFC 2931) and TKEY (RFC 2930). RFC 3755 designated RRSIG as the replacement for SIG for use within DNSSEC
KEYDNS_TYPE_KEYFor security key250x0019RFC2536
RFC2931
RFC3110
RFC4034
Used only for SIG(0) (RFC 2931) and TKEY (RFC 2930). RFC 3445 eliminated their use for application keys and limited their use to DNSSEC. RFC 3755 designates DNSKEY as the replacement within DNSSEC. RFC 4025 designates IPSECKEY as the replacement for use with IPsec.
PXDNS_TYPE_PXX.400 mail mapping information260x001aRFC2163Not in current use by any notable application
GPOSDNS_TYPE_GPOSGeographical Position270x001bRFC1712A more limited early version of the LOC record
AAAADNS_TYPE_AAAAIP6 Address280x001cRFC3596Returns a 128-bit IPv6 address, most commonly used to map hostnames to an IP address of the host.
LOCDNS_TYPE_LOCLocation Information290x001dRFC1876Specifies a geographical location associated with a domain name
NXTDNS_TYPE_NXTNext Domain (OBSOLETE)300x001eRFC2535
RFC3755
Part of the first version of DNSSEC (RFC 2065). NXT was obsoleted by DNSSEC updates (RFC 3755). At the same time, the domain of applicability for KEY and SIG was also limited to not include DNSSEC use.
EIDDNS_TYPE_EIDEndpoint Identifier310x001fNoneDefined by the Nimrod DNS Internet Draft, but never made it to RFC status. Not in current use by any notable application.
NIMLOCDNS_TYPE_NIMLOCNimrod Locator320x0020NoneDefined by the Nimrod DNS Internet Draft, but never made it to RFC status. Not in current use by any notable application.
SRVDNS_TYPE_SRVService locator330x0021RFC2782Generalized service location record, used for newer protocols instead of creating protocol-specific records such as MX.
ATMADNS_TYPE_ATMAATM Address340x0022RFC1002Mistakes (from RFC 1002); the numbers are now assigned to NIMLOC and SRV.
NAPTRDNS_TYPE_NAPTRNaming Authority Pointer350x0023RFC3403Defined by The ATM Forum Committee
KXDNS_TYPE_KXKey Exchanger360x0024RFC2230Used 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.
CERTDNS_TYPE_CERTCertificate record370x0025RFC4398Stores digital certificates in various forms (PKIXSPKIPGP, etc).
A6DNS_TYPE_A6A6 (OBSOLETE – use AAAA)380x0026RFC2874
RFC3226
RFC6563
Defined as part of early IPv6 but downgraded to experimental by RFC 3363; later downgraded to historic by RFC 6563
DNAMEDNS_TYPE_DNAMEDelegation name record390x0027RFC6672Alias 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.
SINKDNS_TYPE_SINKSINK400x0028NoneDefined by the Kitchen Sink Internet Draft, but never made it to RFC status
OPTDNS_TYPE_OPTOption410x0029RFC3225
RFC6891
This is a pseudo-record type needed to support EDNS.
APLDNS_TYPE_APLAddress Prefix List420x002ARFC3123Specify lists of address ranges, e.g. in CIDR format, for various address families. Experimental.
DSDNS_TYPE_DSDelegation Signer430x002BRFC4034The record used to identify the DNSSEC signing key of a delegated zone
SSHFPDNS_TYPE_SSHFPSSH Public Key Fingerprint440x002CRFC4255Resource record for publishing SSH public host key fingerprints in the DNS, 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.
IPSECKEYDNS_TYPE_IPSECKEYIPsec Key450x002DRFC4025Key record that can be used with IPsec
RRSIGDNS_TYPE_RRSIGDNSSEC signature460x002ERFC4034Signature for a DNSSEC-secured record set. Uses the same format as the SIG record.
NSECDNS_TYPE_NSECNext Secure record470x002FRFC4034
RFC9077
Part of DNSSEC—used to prove a name does not exist. Uses the same format as the (obsolete) NXT record.
DNSKEYDNS_TYPE_DNSKEYDNS Key record480x0030RFC4034The key record used in DNSSEC. Uses the same format as the KEY record.
DHCIDDNS_TYPE_DHCIDDHCP identifier490x0031RFC4701Used in conjunction with the FQDN option to DHCP
NSEC3DNS_TYPE_NSEC3Next Secure record version 3500x0032RFC5155
RFC9077
An extension to DNSSEC that allows proof of nonexistence for a name without permitting zonewalking
NSEC3PARAMDNS_TYPE_NSEC3PRAMNSEC3 parameters510x0033RFC5155Parameter record for use with NSEC3
TLSADNS_TYPE_TLSATLSA certificate association520x0034RFC6698A 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'”.
SMIMEADNS_TYPE_SMIMEAS/MIME cert association530x0035RFC8162Associates an S/MIME certificate with a domain name for sender authentication.
HIPDNS_TYPE_HIPHost Identity Protocol550x0037RFC8005Method of separating the end-point identifier and locator roles of IP addresses.
NINFODNS_TYPE_NINFONINFO560x0038NoneUsed to provide status information about a zone. Requested for the IETF draft “The Zone Status (ZS) DNS Resource Record” in 2008. Expired without adoption.[36]
RKEYDNS_TYPE_RKEYRKEY570x0039NoneUsed for encryption of NAPTR records. Requested for the IETF draft “The RKEY DNS Resource Record” in 2008. Expired without adoption.[37]
TALINKDNS_TYPE_TALINKTALINK580x003ANoneDefined by the DNSSEC Trust Anchor History Service Internet Draft, but never made it to RFC status
CDSDNS_TYPE_CDSChild DS590x003BRFC7344Child copy of DS record, for transfer to parent
CDNSKEYDNS_TYPE_CDNSKEYDNSKEY(s) the Child wants reflected in DS600x003CRFC7344Child copy of DNSKEY record, for transfer to parent
OPENPGPKEYDNS_TYPE_OPENPGPKEYOpenPGP public key record610x003DRFC7929A 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.
CSYNCDNS_TYPE_CSYNCChild-To-Parent Synchronization620x003ERFC7477Specify a synchronization mechanism between a child and a parent DNS zone. Typical example is declaring the same NS records in the parent and the child zone
ZONEMDDNS_TYPE_ZONEMDMessage Digests for DNS Zones630x003FRFC8976Provides a cryptographic message digest over DNS zone data at rest.
SVCBDNS_TYPE_SVCBService Binding640x0040RFC9460This resource record provides metadata and other information that can help clients connect to the host. The HTTPS record is a specialised SVCB record to help when establishing HTTPS connections. The more general SVCB record can provide other information such as supported protocols, alternative endpoints, and some types of aliasing not supported by CNAME records.
HTTPSDNS_TYPE_HTTPSHTTPS Binding650x0041RFC9460A specialised type of SVCB record. Provides connection information required to establish a secure connection via HTTPS, which would ordinarily be obtained and negotiated during connection to the host. Obtaining the information from the DNS server instead of negotiating it with the host allows for more secure connections (e.g. by using Encrypted Client Hello) and lower latency when the connection to the host is first established.
DSYNCDNS_TYPE_DSYNCEndpoint discovery for delegation synchronization660x0042RFC9859
HHITDNS_TYPE_HHITHierarchical Host Identity Tag670x0043RFC9886
BRIDDNS_TYPE_BRIDUAS Broadcast Remote Identification680x0044RFC9886
UNECEDNS_TYPE_UNECEValue coded per a UNECE Recommendation690x0045None
ISODNS_TYPE_ISOValue coded per an ISO standard700x0046None
SPFDNS_TYPE_SPFSPF data record990x0063RFC7208Specified as part of the Sender Policy Framework protocol as an alternative to storing SPF data in TXT records, using the same format. It was discontinued in RFC 7208 due to widespread lack of support.
UINFODNS_TYPE_UINFOUINFO1000x0064NoneIANA reserved, no RFC documented them and support was removed from BIND in the early 90s.
UIDDNS_TYPE_UIDUID1010x0065NoneIANA reserved, no RFC documented them and support was removed from BIND in the early 90s.
GIDDNS_TYPE_GIDGID1020x0066NoneIANA reserved, no RFC documented them and support was removed from BIND in the early 90s.
UNSPECDNS_TYPE_UNSPECUNSPEC1030x0067NoneIANA reserved, no RFC documented them and support was removed from BIND in the early 90s.
NIDDNS_TYPE_NIDNID1040x0068RFC6742Not in use by any notable application and marked as “experimental”
L32DNS_TYPE_L32L321050x0069RFC6742Not in use by any notable application and marked as “experimental”
L64DNS_TYPE_L64L641060x006ARFC6742Not in use by any notable application and marked as “experimental”
LPDNS_TYPE_LPLP1070x006BRFC6742Not in use by any notable application and marked as “experimental”
EUI48DNS_TYPE_EUI48an EUI-48 address1080x006CRFC7043
EUI64DNS_TYPE_EUI64an EUI-64 address1090x006DRFC7043
NXNAMEDNS_TYPE_NXNAMENXDOMAIN indicator for Compact Denial of Existence1280x0080RFC9824
ADDRSDNS_TYPE_ADDRS2480x00f8
TKEYDNS_TYPE_TKEYTransaction Key2490x00f9RFC2930A method of providing keying material to be used with TSIG that is encrypted under the public key in an accompanying KEY RR
TSIGDNS_TYPE_TSIGTransaction Signature2500x00faRFC8945Can be used to authenticate dynamic updates as coming from an approved client, or to authenticate responses as coming from an approved recursive name server[23] similar to DNSSEC.
IXFRDNS_TYPE_IXFRIncremental Zone Transfer2510x00fbRFC1995Requests 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.
AXFRDNS_TYPE_AXFRTransfer of an entire zone2520x00fcRFC1035
RFC5936
Transfer entire zone file from the primary name server to secondary name servers.
MAILBDNS_TYPE_MAILBMailbox-related RRs (MB, MG or MR)2530x00fdRFC1035MB, MG, MR, and MINFO are records to publish subscriber mailing lists. MAILB is a query code which returns one of those records. The intent was for MB and MG to replace the SMTP VRFY and EXPN commands. MR was to replace the “551 User Not Local” SMTP error. Later, RFC 2505 recommended that both VRFY and EXPN be disabled, making MB and MG unnecessary. They were classified as experimental by RFC 1035.
MAILADNS_TYPE_MAILAMail agent RRs (OBSOLETE – see MX)2540x00feRFC1035Mail destination (MD) and mail forwarder (MF) records; MAILA is not an actual record type, but a query type which returns MF and/or MD records. RFC 973 replaced these records with the MX record.
*DNS_TYPE_ALL
DNS_TYPE_ANY
All cached records2550x00ffRFC1035Returns 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. Usually referred to as ANY (e.g., in dig, Windows nslookup, and Wireshark). In 2019, RFC 8482 standards-track publication led many DNS providers, including Cloudflare, to provide only minimal responses to “ANY” queries, instead of enumerating records.
URIDNS_TYPE_URIUniform Resource Identifier2560x0100RFC7553Can be used for publishing mappings from hostnames to URIs.
CAADNS_TYPE_CAACertification Authority Restriction2570x0101RFC8659DNS Certification Authority Authorization, constraining acceptable CAs for a host/domain
AVCDNS_TYPE_AVC
Application Visibility and Control
2580x0102None
DOADNS_TYPE_DOA
Digital Object Architecture
2590x0103NoneDefined by the DOA over DNS Internet Draft, but never made it to RFC status
AMTRELAYDNS_TYPE_AMTRELAYAutomatic Multicast Tunneling Relay2600x0104RFC8777
RESINFODNS_TYPE_RESINFOResolver Information as Key/Value Pairs2610x0105RFC9606
WALLETDNS_TYPE_WALLETPublic wallet address2620x0106None
CLADNS_TYPE_CLABP Convergence Layer Adapter2630x0107None
IPNDNS_TYPE_IPNBP Node Number2640x0108None
TADNS_TYPE_TADNSSEC Trust Authorities327680x8000NonePart 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.
DLVDNS_TYPE_DLVDNSSEC Lookaside Validation record327690x8001RFC8749
RFC4131
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.
WINSDNS_TYPE_WINS652810xff01
WINSRDNS_TYPE_WINSR652820xff02
  1. Domain Name System blocklist ↩︎

https://www.iana.org/assignments/dns-parameters