A Comprehensive List of DNS Record Types

Let's break down the different types of DNS records that help your website or app communicate with the world.

There are several types of DNS records, but the most common ones are A, AAAA, and CNAME records.

A records are used to map a domain name to an IP address, which is like a street address for your website. This is the most basic type of DNS record.

AAAA records are similar to A records but are used for IPv6 addresses, which are the newer version of internet addresses.

CNAME records, on the other hand, are used to map a domain name to another domain name, which is like a nickname for your website.

If this caught your attention, see: Aaaa Record

A and AAAA Records are essential for connecting domain names to IP addresses. They allow users to access websites and online services by mapping domain names to the corresponding IP addresses.

A records connect domain names to IPv4 addresses, but IPv4 addresses are running out, making IPv6 addresses more common. IPv6 addresses have more numerals than IPv4 addresses.

AAAA records, on the other hand, exclusively store IPv6 addresses connected to domain names. They function like A records, but with IPv6 addresses instead.

Related reading: What Is a Web Domain Names

A Records are used to connect domain names to IPv4 addresses, which are the older internet protocol addresses that were widely used before IPv6 became more prevalent.

They function similarly to AAAA records, but store IPv4 addresses instead of IPv6 addresses.

A Records are an essential part of the DNS system, allowing users to access websites and online services by typing in a domain name rather than a complex IP address.

They can be used to point a domain name to a specific server or IP address, making it easier to manage and maintain your online presence.

The use of A Records is still common today, especially for websites and online services that don't require IPv6 connectivity.

Worth a look: IP Address Management

AAAA records are used to connect domain names to IPv6 addresses. IPv6 addresses have more numerals than IPv4 addresses and are becoming more common.

These records function like A records, but instead of storing IPv4 addresses, they exclusively store IPv6 addresses connected to domain names.

AAAA records point to an IPv6 address for a specific hostname or domain. They have a type of AAAA and a TTL (time to live) that determines how long the record is cached.

Here are some key details about AAAA records:

CNAME records point a domain name, or alias, to another domain, which is known as the canonical name. The alias doesn't point to an IP address, but rather to the canonical name.

An example of a CNAME record is the subdomain ng.example.com pointing to example.com. The canonical name, example.com, then points to the actual IP address using an A record.

A CNAME record is used to point to a different domain, not an IP address.

Here's a brief overview of the key elements of a CNAME record:

Nameserver, or NS records, show which DNS server is acting as the authoritative nameserver for a domain. This is crucial for users to access a website.

An NS record specifies which server is authoritative for the DNS records of a given domain. Domains should have multiple NS records pointing to different nameservers to provide redundancy and ensure high availability.

Expand your knowledge: Record Ns

CNAME records are a type of DNS record that point a domain name or hostname (alias) to another domain name or hostname (canonical name). They do not point to an IP address.

You can add only one CNAME record per hostname, making them a convenient option for linking subdomains to a domain's A or AAAA record. This prevents having to create an extra A or AAAA record for each subdomain.

For example, instead of creating separate A records for www.example.com and product.example.com, you could link product.example.com to a CNAME record that is then linked to an A record for example.com.

A CNAME record contains the following elements: domain name (alias), record type (CNAME), value (canonical name), and TTL (time to live). The TTL determines how long DNS resolvers cache a DNS record before refreshing it.

Here's a breakdown of the elements of a CNAME record:

It's not recommended to have CNAME records pointing to other CNAME records, as this creates unnecessary steps in the DNS lookup process.

For your interest: CNAME Record

NS Records are a crucial part of the DNS system, specifying the authoritative DNS server for a domain.

An NS record points to where internet applications like a web browser can find the IP address for a domain name.

Multiple nameservers are usually specified for a domain, providing redundancy and ensuring high availability.

A nameserver is a DNS server containing authoritative DNS records for one or more domains.

The elements of an NS record include the domain name, record type, value, and TTL (Time To Live).

Here's a breakdown of these elements:

Without NS records, users will not be able to access your website, as they won't know where to find the IP address for your domain.

Mail servers are crucial for directing emails to the right place. You can set up individual email accounts with MX records, which are linked to your domain.

There are specific records related to mailbox information that are no longer commonly used, including MB, MG, MINFO, and MR records. These records were used for mailbox management and mail forwarding in DNS.

For example, the MB record specifies the host responsible for a particular mailbox, while the MG record lists members of a mail group. MINFO provides information about a mailbox, including pointers to the administrator's mailbox and an error-handling mailbox. MR records specify the new address for a renamed mailbox.

Here's a quick rundown of some other record types:

Mail servers also have backup servers, which is where multiple MX records come in. You can have multiple MX records for the same domain, with the Priority attribute routing traffic to the primary and backup mail servers.

Related reading: Nordvpn Dns Server

Resource Records are used to map a domain name to the IP address of a mail server. This is crucial for email delivery.

MX records are a type of Resource Record that specify the mail server responsible for receiving email for a domain. There are multiple MX records for a domain, and they are prioritized.

Consider reading: All Types of Email

The Mail Exchanger (MX) record format is a specific type of Resource Record that contains the mail server's IP address and a preference value. The preference value determines the order in which mail servers are tried.

A mail server can have multiple IP addresses, which is why multiple A records are often used to map a domain name to its IP addresses. This ensures that email can be delivered even if one IP address becomes unavailable.

The mail server's IP address is referenced by its A record, which is a type of Resource Record.

Additional reading: Resource Records of Dns

The DNS protocol has a few other record types that don't quite fit into the standard categories. The "*" record type, for example, returns all records of all types known to the name server.

The "*" record type is also known as "ANY" and is usually referred to as such in tools like dig, Windows nslookup, and Wireshark. It's worth noting that in 2019, many DNS providers, including Cloudflare, started providing only minimal responses to "ANY" queries instead of enumerating all records.

The AXFR record type is used for Authoritative Zone Transfer, which transfers the entire zone file from the primary name server to secondary name servers. This is a critical process for maintaining DNS records across a network.

IXFR is another record type, which stands for Incremental Zone Transfer. It requests a zone transfer of the given zone but only includes differences from a previous serial number. This can be useful for keeping DNS records up-to-date without having to transfer the entire zone file.

The OPT record type is a pseudo-record type needed to support EDNS, which is a protocol extension for DNS. It's used to negotiate the use of EDNS in a DNS query.

The ALIAS, ANAME, and apex CNAME record types are all pseudo-record types that serve as alternatives to CNAMEs. These types are not standardized in RFCs, but are commonly used in DNS software. They allow for the creation of synthetic A and AAAA records that automatically update if the destination changes.

Check this out: Message Transfer Agent

MX records are a crucial part of directing emails to your domain's mail server. They're like a roadmap for email traffic, showing where emails should be routed.

An MX record can only point to an email server's name, which means each referenced email server must also have a valid A record specifying its IP address. This is important for ensuring that emails can be delivered to the correct server.

You can have multiple MX records for a single domain name, which allows you to have backup email servers. This is handy in case your primary server is unavailable or fails to send emails.

The priority attribute routes traffic to the primary and backup mail servers. For example, an MX record with priority 10 will be the primary mail server, while the secondary server will only be used when the primary server is unavailable.

Here's an example of what an MX record might look like:

In this example, the MX record with priority 10 will be the primary mail server, while the secondary server will only be used when the primary server is unavailable. The lower the priority value, the higher the actual priority.

SPF records are used to identify the mail servers that can send emails through your domain. This helps prevent your domain from being used by spammers or for malicious purposes by letting email receivers know that what they are receiving has been authorized.

SPF records are a crucial part of email security, and they can be configured to specify which mail servers are allowed to send emails on behalf of your domain.

On a similar theme: Different Types of Email

Security and Authority Records are crucial for domain owners to control who can issue certificates for their domain. CAA Records, short for Certification Authority Authorization Records, allow domain owners to specify which certificate authorities (CAs) are authorized to issue certificates.

A CAA Record typically contains the following elements: Domain name, Record type, Flag, Tag, and CA. The Flag can be either 0 (non-critical) or 1 (critical), specifying whether the CA must understand and comply with the CAA record.

Here's an interesting read: DNS Certification Authority Authorization

Here's a breakdown of the elements in a CAA Record:

CAA records are a type of DNS record that allows domain owners to specify which certificate authorities can issue certificates for their domain.

A CAA record can set policy for the entire domain or for specific hostnames, and it's inherited by subdomains, meaning a record set on domain.com will also apply to subdomain.domain.com.

If no CAA record exists, any CA can issue certificates for the domain, but this can be a security risk.

A CAA record typically contains five elements: Domain name, Record type, Flag, Tag, and CA.

Here's a breakdown of these elements:

The flag can be either 0 or 1, with 0 indicating a non-critical flag and 1 indicating a critical flag.

DNSSEC records are a crucial part of securing your DNS, and they're based on public key cryptography. They ensure that the data you receive from a DNS server is genuine and hasn't been tampered with.

DNSSEC uses a pair of keys, one public and one private, to authenticate the DNS data. The private key is kept secret, while the public key is shared openly.

To set up DNSSEC, you need to generate a pair of keys and then create a DNSKEY record that holds the public key. This record is used to authenticate the DNS data.

A DNSKEY record is a type of DNS record that contains the public key used for DNSSEC authentication. It's an important record that helps ensure the integrity of your DNS data.

The DNSKEY record is stored in the DNS zone file, and it's used to verify the authenticity of the DNS data. The record is usually stored in the zone file with a TTL (time to live) of 1 hour or less.

You can also use a DNSKEY record to delegate DNSSEC authentication to a third-party service. This can be useful if you don't want to manage the keys yourself.

To delegate DNSSEC authentication, you need to create a DNSKEY record that points to the third-party service. This record is called a DS (delegation signer) record.

You might like: DNS Hosting Service

A DS record is a type of DNS record that contains a hash of the public key used for DNSSEC authentication. It's used to delegate DNSSEC authentication to a third-party service.

The DS record is stored in the parent zone, which is the DNS zone that contains the records for the top-level domain (TLD). The record is usually stored with a TTL of 1 hour or less.

By using a DS record to delegate DNSSEC authentication, you can ensure that your DNS data is secure and trustworthy.

See what others are reading: Zone File

PTR records are used to connect an IP address with a domain name, which is the opposite of how A records work. They help detect spam by checking if IP addresses and associated email addresses are used by legitimate email servers.

PTR records store IP addresses in reverse, which is a bit counterintuitive. For IPv4 addresses, this means the octets are saved in reverse order. For IPv6 addresses, it means the nibbles (each 4-bit section of the hexadecimal address) are saved in reverse order.

PTR records must be set up by the server host, so it's an important task to remember. They're essential for specific network configurations and functionalities, even if they're not used as frequently as other DNS records.

Broaden your view: Reverse Domain Name Notation

PTR records are used to connect an IP address with a domain name, instead of a domain name with an IP address.

PTR records must be set up by the server host.

PTR records are the inverse of A or AAAA records, mapping IP addresses back to domain names and facilitating reverse DNS lookups.

PTR records store IP addresses in reverse, with IPv4 addresses saved with their octets in reverse order and IPv6 addresses saved in reverse order of their nibbles.

Here's a breakdown of how PTR records store IP addresses:

PTR records are essential for specific network configurations and functionalities, although they are not in use as frequently as other DNS records.

SRV records are used to identify a host and port for specific services, such as messaging, for a domain. They're like digital signs pointing to where a particular service can be found.

SRV records store essential information about host and port details for specific internet services. This information includes the service name, protocol, and port number.

For more insights, see: SRV Record

SRV records hold a lot of details, including the symbolic name of the service, the protocol used (TCP or UDP), and the domain name associated with the service. They also include the TTL (time to live), class, priority, weight, and target host information.

Here's a breakdown of the key components of an SRV record:

Text and miscellaneous records are a crucial part of DNS records, allowing you to store textual information about your domain name.

TXT records, in particular, store arbitrary text data, which can be used for domain verification, sender policy framework (SPF), DKIM, or other forms of authentication. They're also used to store email verification records.

A typical TXT record consists of four elements: domain name, record type, value, and TTL. The domain name specifies the domain name, the record type indicates that it's a TXT record, the value stores a user-defined text string, and the TTL shows how long DNS resolvers cache a DNS record before refreshing it.

Discover more: TXT Record

Here's a breakdown of a typical TXT record:

TXT records have a maximum length of 255 characters for individual text strings, but multiple strings can be concatenated to exceed this limit.

Some text records are just that - text. They can be emails, letters, or even social media posts.

These records can be incredibly valuable for research purposes, especially if they're related to a specific event or time period.

A great example of this is a company's internal email communication, which can provide insight into the company's culture and decision-making processes.

Text records can also be useful for verifying facts or getting a sense of how a particular issue was handled in the past.

For instance, a public official's email records can reveal how they responded to a crisis or controversy.

In some cases, text records can even be used as evidence in court cases.

Related reading: Dns Email Records

TXT records store textual information related to domains and subdomains, allowing for the storage of SPF records and email verification records.

They're used alongside other record types to provide additional information, such as domain verification, sender policy framework (SPF), DKIM, or other forms of authentication.

TXT records contain four key elements: domain name, record type, value, and TTL.

The domain name specifies the domain name, and in a DNS zone file, the @ symbol is often used instead of the full domain name to represent the root domain.

The record type indicates that this is a TXT record.

The value stores a user-defined text string, with a maximum length of 255 characters.

Multiple strings can be concatenated to exceed this limit.

TXT records can be used for things such as email validation, site and ownership verification, framework policies, etc.

They don't require specific formatting, making them a flexible option for administrators.

Here are the key elements of a TXT record: