public Class DnsRecordType

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.

IPv6 address record RFC 3596 Returns a 128-bit IPv6 address, most commonly used to map hostnames to an IP address of the host.

AFS database record RFC 1183 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.

All cached records RFC 1035 Returns 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. Sometimes referred to as ANY, for example in Windows nslookup and Wireshark.

Address Prefix List record RFC 3123 Specify lists of address ranges, e.g. in CIDR format, for various address families. Experimental.

Authoritative Zone Transfer record RFC 1035 Transfer entire zone file from the master name server to secondary name servers.

Certification Authority Authorization record RFC 6844 CA pinning, constraining acceptable CAs for a host/domain.

Certificate record RFC 4398 Stores PKIX, SPKI, PGP, etc.

Canonical name record RFC 1035 Alias of one name to another: the DNS lookup will continue by retrying the lookup with the new name.

DHCP identifier record RFC 4701 Used in conjunction with the FQDN option to DHCP.

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.

Delegation name record RFC 2672 DNAME creates an alias for a name and all its subnames, unlike CNAME, which aliases only the exact name in its label. Like the CNAME record, the DNS lookup will continue by retrying the lookup with the new name.

DNS Key record RFC 4034 The key record used in DNSSEC. Uses the same format as the KEY record.

Delegation signer record RFC 4034 The record used to identify the DNSSEC signing key of a delegated zone.

Host Identity Protocol record RFC 5205 Method of separating the end-point identifier and locator roles of IP addresses.

IPsec Key record RFC 4025 Key record that can be used with IPsec.

Incremental Zone Transfer record RFC 1996 Requests 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.

key record RFC 2535 and RFC 2930 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.

Key eXchanger record RFC 2230 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.

Location record RFC 1876 Specifies a geographical location associated with a domain name.

Mail exchange record RFC 1035 Maps a domain name to a list of message transfer agents for that domain.

Naming Authority Pointer record RFC 3403 Allows regular expression based rewriting of domain names which can then be used as URIs, further domain names to lookups, etc.

Name server record RFC 1035 Delegates a DNS zone to use the given authoritative name servers

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.

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

NSEC3 parameters record RFC 5155 Parameter record for use with NSEC3.

Option record RFC 2671 This is a pseudo DNS record type needed to support EDNS.

Pointer record RFC 1035 Pointer to a canonical name. Unlike a CNAME, DNS processing does NOT proceed, just the name is returned. The most common use is for implementing reverse DNS lookups, but other uses include such things as DNS-SD.

Responsible person record RFC 1183 Information about the responsible person(s) for the domain. Usually an email address with the @ replaced by a .

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

Signature record RFC 2535 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.

Start of [a zone of] authority record RFC 1035 and RFC 2308 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.

Sender Policy Framework record RFC 4408 Specified as part of the SPF protocol as an alternative to of storing SPF data in TXT records. Uses the same format as the earlier TXT record.

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

SSH Public Key Fingerprint record 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. RFC 6594 defines ECC SSH keys and SHA-256 hashes. See the IANA SSHFP RR parameters registry for details.

DNSSEC Trust Authorities record N/A 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.

Secret key record RFC 2930 A method of providing keying material to be used with TSIG that is encrypted under the public key in an accompanying KEY RR..

TLSA certificate association record RFC 6698 A record for DNS-based Authentication of Named Entities (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'.

Transaction Signature record RFC 2845 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 similar to DNSSEC.

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, DKIM, DMARC DNS-SD, etc.