<Table> <Tr> <Th> Type </Th> <Th> Type id . ( decimal ) </Th> <Th> Defining RFC </Th> <Th> Description </Th> <Th> Function </Th> </Tr> <Tr> <Td> </Td> <Td> </Td> <Td> RFC 1035 </Td> <Td> Address record </Td> <Td> 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 . </Td> </Tr> <Tr> <Td> AAAA </Td> <Td> 28 </Td> <Td> RFC 3596 </Td> <Td> IPv6 address record </Td> <Td> Returns a 128 - bit IPv6 address , most commonly used to map hostnames to an IP address of the host . </Td> </Tr> <Tr> <Td> AFSDB </Td> <Td> 18 </Td> <Td> RFC 1183 </Td> <Td> AFS database record </Td> <Td> 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 . </Td> </Tr> <Tr> <Td> APL </Td> <Td> 42 </Td> <Td> RFC 3123 </Td> <Td> Address Prefix List </Td> <Td> Specify lists of address ranges , e.g. in CIDR format , for various address families . Experimental . </Td> </Tr> <Tr> <Td> CAA </Td> <Td> 257 </Td> <Td> RFC 6844 </Td> <Td> Certification Authority Authorization </Td> <Td> DNS Certification Authority Authorization , constraining acceptable CAs for a host / domain </Td> </Tr> <Tr> <Td> CDNSKEY </Td> <Td> 60 </Td> <Td> RFC 7344 </Td> <Td> Child DNSKEY </Td> <Td> Child copy of DNSKEY record , for transfer to parent </Td> </Tr> <Tr> <Td> CDS </Td> <Td> 59 </Td> <Td> RFC 7344 </Td> <Td> Child DS </Td> <Td> Child copy of DS record , for transfer to parent </Td> </Tr> <Tr> <Td> CERT </Td> <Td> 37 </Td> <Td> RFC 4398 </Td> <Td> Certificate record </Td> <Td> Stores PKIX , SPKI , PGP , etc . </Td> </Tr> <Tr> <Td> CNAME </Td> <Td> 5 </Td> <Td> RFC 1035 </Td> <Td> Canonical name record </Td> <Td> Alias of one name to another : the DNS lookup will continue by retrying the lookup with the new name . </Td> </Tr> <Tr> <Td> DHCID </Td> <Td> 49 </Td> <Td> RFC 4701 </Td> <Td> DHCP identifier </Td> <Td> Used in conjunction with the FQDN option to DHCP </Td> </Tr> <Tr> <Td> DLV </Td> <Td> 32769 </Td> <Td> RFC 4431 </Td> <Td> DNSSEC Lookaside Validation record </Td> <Td> 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 . </Td> </Tr> <Tr> <Td> DNAME </Td> <Td> 39 </Td> <Td> RFC 6672 </Td> <Td> </Td> <Td> 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 . </Td> </Tr> <Tr> <Td> DNSKEY </Td> <Td> 48 </Td> <Td> RFC 4034 </Td> <Td> DNS Key record </Td> <Td> The key record used in DNSSEC . Uses the same format as the KEY record . </Td> </Tr> <Tr> <Td> DS </Td> <Td> 43 </Td> <Td> RFC 4034 </Td> <Td> Delegation signer </Td> <Td> The record used to identify the DNSSEC signing key of a delegated zone </Td> </Tr> <Tr> <Td> HIP </Td> <Td> 55 </Td> <Td> RFC 8005 </Td> <Td> Host Identity Protocol </Td> <Td> Method of separating the end - point identifier and locator roles of IP addresses . </Td> </Tr> <Tr> <Td> IPSECKEY </Td> <Td> 45 </Td> <Td> RFC 4025 </Td> <Td> IPsec Key </Td> <Td> Key record that can be used with IPsec </Td> </Tr> <Tr> <Td> KEY </Td> <Td> 25 </Td> <Td> RFC 2535 and RFC 2930 </Td> <Td> Key record </Td> <Td> 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 . </Td> </Tr> <Tr> <Td> KX </Td> <Td> 36 </Td> <Td> RFC 2230 </Td> <Td> Key Exchanger record </Td> <Td> 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 . </Td> </Tr> <Tr> <Td> LOC </Td> <Td> 29 </Td> <Td> RFC
<Table> <Tr> <Th> Type </Th> <Th> Type id . ( decimal ) </Th> <Th> Defining RFC </Th> <Th> Description </Th> <Th> Function </Th> </Tr> <Tr> <Td> </Td> <Td> </Td> <Td> RFC 1035 </Td> <Td> Address record </Td> <Td> 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 . </Td> </Tr> <Tr> <Td> AAAA </Td> <Td> 28 </Td> <Td> RFC 3596 </Td> <Td> IPv6 address record </Td> <Td> Returns a 128 - bit IPv6 address , most commonly used to map hostnames to an IP address of the host . </Td> </Tr> <Tr> <Td> AFSDB </Td> <Td> 18 </Td> <Td> RFC 1183 </Td> <Td> AFS database record </Td> <Td> 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 . </Td> </Tr> <Tr> <Td> APL </Td> <Td> 42 </Td> <Td> RFC 3123 </Td> <Td> Address Prefix List </Td> <Td> Specify lists of address ranges , e.g. in CIDR format , for various address families . Experimental . </Td> </Tr> <Tr> <Td> CAA </Td> <Td> 257 </Td> <Td> RFC 6844 </Td> <Td> Certification Authority Authorization </Td> <Td> DNS Certification Authority Authorization , constraining acceptable CAs for a host / domain </Td> </Tr> <Tr> <Td> CDNSKEY </Td> <Td> 60 </Td> <Td> RFC 7344 </Td> <Td> Child DNSKEY </Td> <Td> Child copy of DNSKEY record , for transfer to parent </Td> </Tr> <Tr> <Td> CDS </Td> <Td> 59 </Td> <Td> RFC 7344 </Td> <Td> Child DS </Td> <Td> Child copy of DS record , for transfer to parent </Td> </Tr> <Tr> <Td> CERT </Td> <Td> 37 </Td> <Td> RFC 4398 </Td> <Td> Certificate record </Td> <Td> Stores PKIX , SPKI , PGP , etc . </Td> </Tr> <Tr> <Td> CNAME </Td> <Td> 5 </Td> <Td> RFC 1035 </Td> <Td> Canonical name record </Td> <Td> Alias of one name to another : the DNS lookup will continue by retrying the lookup with the new name . </Td> </Tr> <Tr> <Td> DHCID </Td> <Td> 49 </Td> <Td> RFC 4701 </Td> <Td> DHCP identifier </Td> <Td> Used in conjunction with the FQDN option to DHCP </Td> </Tr> <Tr> <Td> DLV </Td> <Td> 32769 </Td> <Td> RFC 4431 </Td> <Td> DNSSEC Lookaside Validation record </Td> <Td> 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 . </Td> </Tr> <Tr> <Td> DNAME </Td> <Td> 39 </Td> <Td> RFC 6672 </Td> <Td> </Td> <Td> 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 . </Td> </Tr> <Tr> <Td> DNSKEY </Td> <Td> 48 </Td> <Td> RFC 4034 </Td> <Td> DNS Key record </Td> <Td> The key record used in DNSSEC . Uses the same format as the KEY record . </Td> </Tr> <Tr> <Td> DS </Td> <Td> 43 </Td> <Td> RFC 4034 </Td> <Td> Delegation signer </Td> <Td> The record used to identify the DNSSEC signing key of a delegated zone </Td> </Tr> <Tr> <Td> HIP </Td> <Td> 55 </Td> <Td> RFC 8005 </Td> <Td> Host Identity Protocol </Td> <Td> Method of separating the end - point identifier and locator roles of IP addresses . </Td> </Tr> <Tr> <Td> IPSECKEY </Td> <Td> 45 </Td> <Td> RFC 4025 </Td> <Td> IPsec Key </Td> <Td> Key record that can be used with IPsec </Td> </Tr> <Tr> <Td> KEY </Td> <Td> 25 </Td> <Td> RFC 2535 and RFC 2930 </Td> <Td> Key record </Td> <Td> 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 . </Td> </Tr> <Tr> <Td> KX </Td> <Td> 36 </Td> <Td> RFC 2230 </Td> <Td> Key Exchanger record </Td> <Td> 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 . </Td> </Tr> <Tr> <Td> LOC </Td> <Td> 29 </Td> <Td> RFC
which record type on a dns server represents an ipv6 host
which record type on a dns server represents an ipv6 host
AAAA
AAAA