DNAME : delegation name ( RFC 2672)
DNAME will delegate an entire portion of the DNS tree under a new name. In contrast, the CNAME record creates an alias of a single name. Like the CNAME record, the DNS lookup will continue by retrying the lookup with the new name. |
CNAME : Canonical name record ( RFC 1035)
Alias of one name to another: the DNS lookup will continue by retrying the lookup with the new name. |
MX : mail exchange record ( RFC 1035)
Maps a domain name to a list of mail exchange servers for that domain |
TKEY : Transaction Key ( RFC 2930)
One way of providing a key to be used with TSIG |
NS : name server record ( RFC 1035)
Delegates a DNS zone to use the given authoritative name servers |
KEY : Key record ( RFC 4034)
Used only for TKEY (RFC 2930). Before RFC 3755 was published, this was also used for DNSSEC, but DNSSEC now uses DNSKEY. |
DNSKEY : DNS Key record ( RFC 4034)
The key record used in DNSSEC. Uses the same format as the KEY record. |
NSEC3 : NSEC record version 3 ( RFC 5155)
An extension to DNSSEC that allows proof of nonexistence for a name without permitting zonewalking |
PTR : 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. |
* : 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. |
TSIG : Transaction Signature ( RFC 2845)
Record that supports one set of security mechanisms for DNS. Used to secure communication between DNS resolvers and Name servers, in contrast to DNSSEC, which secures the actual DNS records from the authoritative name server. |
LOC : Location record ( RFC 1876)
Specifies a geographical location associated with a domain name |
TXT : 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, DomainKeys, DNS-SD, etc. |
AFSDB : 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. |
HIP : Host Identity Protocol ( RFC 5205)
Method of separating the end-point identifier and locator roles of IP addresses. |
CERT : Certificate record ( RFC 4398)
Stores PKIX, SPKI, PGP, etc. |
NAPTR : Naming Authority Pointer ( RFC 3403)
Allows regular expression based rewriting of domain names which can then be used as URIs, further domain names to lookups, etc. |
DLV : 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. |
