Top 8 Most Common Types of DNS Records

DNS records are small instructions stored in your domain’s DNS settings that tell the internet how to handle requests related to your domain. These instructions decide where your website loads from, which servers can send emails on your behalf, and how incoming emails should be routed. Without properly configured DNS records, websites may not open correctly, and emails may fail to reach inboxes.

As a domain owner or marketing professional, it’s important to understand which DNS records are used for email servers, as email delivery depends on specific records such as MX, TXT, and PTR. Having an understanding of these common DNS record types helps prevent misconfiguration and improve domain reliability. In this guide, we explain the most common DNS record types, their purposes, and simple examples to help so understand how each one works.

A Record

An A record is one of the most commonly used DNS record types. It connects a domain name to the IPv4 address of the server where the website is hosted. The letter “A” stands for Address, meaning the record tells the internet which server address should respond when someone enters your domain in a browser.

During a DNS lookup, the system checks the A record to find the correct IPv4 address associated with the domain. For example, when someone visits easydmarc.com, the A record directs the browser request to the corresponding IPv4 server that hosts the website.

A records can also be configured in multiple instances for the same domain. This setup is often used for redundancy, load balancing, or failover purposes, ensuring that traffic can still reach an available server if one becomes unavailable.

A records follow the standard DNS format defined in RFC 1035. A typical DNS record example looks like this:

How A Records Map Domains to IP Addresses

When a user types a domain name into a browser, the DNS resolver searches for the domain’s A record. Once the IPv4 address is found, the browser uses that address to connect directly to the hosting server and load the website. This entire process usually happens in milliseconds and is essential for making domain names human-friendly instead of requiring users to remember numerical IP addresses.

Common Use Cases of A Records

A records are widely used in everyday domain management, including:

• Pointing the root domain (example.com) to a website hosting server.
• Connecting subdomains such as shop.example.com or blog.example.com to specific servers.
• Setting up basic load balancing by using multiple A records.
• Creating redundancy so traffic can continue to flow if a server fails.

Because nearly every website depends on an A record to function, it is considered one of the foundational components of DNS configuration.

AAAA Record

An AAAA record is another important entry among common DNS record types. It performs the same function as an A record, but instead of pointing a domain to an IPv4 address, it maps the domain to an IPv6 address. The name “AAAA” refers to the 128-bit format used by IPv6, which was introduced to address the global shortage of IPv4 addresses.

When a user visits a domain hosted in an IPv6-enabled environment, the DNS system checks the AAAA record and routes the request to the corresponding IPv6 address. Many modern hosting providers now support both A and AAAA records so that domains remain accessible across different network environments.

Here is the example of a typical AAAA record:

Difference Between A and AAAA Records

The main difference between these two records lies in the type of IP address they store. An A record maps a domain to an IPv4 address (e.g., 192.0.2.1), while an AAAA record maps a domain to an IPv6 address (e.g., 2001:db8::1).

Both records can exist simultaneously for the same domain to support dual-stack connectivity Systems automatically choose the appropriate address type depending on network compatibility That’s why using both records ensures that users on either IPv4 or IPv6 networks can reach the same website without any disruption.

When IPv6 AAAA Records are Required?

AAAA records are required when a website or service is hosted on infrastructure that supports IPv6 connectivity. They are also commonly added when organizations want to:

• Prepare their domains for long-term internet scalability.
• Improve global accessibility in regions where IPv6 adoption is high.
• Meet hosting provider or compliance requirements that mandate IPv6 support.

Although not every domain strictly requires an AAAA record today, adding one where IPv6 hosting is available helps maintain compatibility as internet networks continue transitioning toward IPv6-based communication.

CNAME Record

A CNAME (Canonical Name) record is a type of DNS record that points one domain name to another domain name instead of linking directly to an IP address. This allows multiple domain names or subdomains to reference a single primary domain, making DNS management simpler and more flexible. For example, a subdomain like www.example.com can point to example.com, ensuring both addresses lead users to the same destination without needing separate IP mappings.

A typical DNS record example for a CNAME entry may look like:

This configuration tells DNS resolvers that any request for www.example.com should be redirected to the domain example.com.

How CNAME Records Work?

When a user enters a domain configured with a CNAME record, the DNS resolver first looks up the alias (for example, blog.example.com). Instead of returning an IP address immediately, it finds the CNAME record pointing to another hostname, such as hostingprovider.net. The resolver then performs a second lookup to retrieve the final A or AAAA record associated with that hostname and completes the connection. This two-step resolution process allows organizations to change underlying server IPs without updating every related subdomain individually.

CNAME Record Limitations and Best Practices

Although CNAME records are very useful, they have certain limitations that must be considered:

• A CNAME record usually cannot be placed at the root (apex) domain in many DNS configurations.
• A hostname with a CNAME record should not contain other record types simultaneously.
• Excessive CNAME chaining can slightly increase lookup time due to multiple resolution steps.
• It is best to use CNAME records mainly for subdomains such as www, app, or shop.

Following these best practices helps maintain clean DNS configurations while ensuring that domain aliases function reliably across different hosting and service environments.

DNS PTR Record

A PTR (Pointer) record is a special type of DNS record used for reverse DNS lookups. Unlike most DNS record types that map a domain name to an IP address, a PTR record maps an IP address back to its associated domain name. This reverse mapping helps verify the identity of the server behind an IP address and is widely used in email infrastructure and network validation processes.

PTR records are usually configured by the organization that controls the IP address block, such as an internet service provider or hosting provider, rather than the domain owner directly.

How Reverse DNS Lookup Works?

In a reverse DNS lookup, the process begins with an IP address instead of a domain name. When a receiving server wants to verify the identity of the sender, it queries the DNS system for the PTR record associated with that IP. If a valid PTR record exists, the DNS server returns the hostname linked to that IP address. Many systems then perform a forward lookup to confirm that the hostname resolves back to the same IP, ensuring consistency and trust.

Why PTR Records Matter For Email Servers?

PTR records play a major role in email reputation and authentication checks. Mailbox providers often verify reverse DNS entries to determine whether the sending server appears legitimate. Proper email delivery depends not only on MX and TXT records but also on correctly configured PTR records.

Missing or mismatched PTR records can cause emails to be flagged as suspicious, routed to spam folders, or rejected entirely. Maintaining accurate reverse DNS entries helps improve deliverability and strengthens the overall credibility of the sending infrastructure.

NS Record

An NS (Name Server) record is a DNS record type that identifies the authoritative name servers for a domain. It ensures that internet queries are routed to the correct DNS servers that store and manage the domain’s records. Without properly configured NS records, browsers and email systems would not know where to retrieve the domain’s DNS settings.

Each domain typically has multiple NS records that point to at least two authoritative name servers. This redundancy ensures continued DNS availability even if one server becomes unreachable.

How Does NS Records Control DNS Authority?

NS records act as the directory that tells the Internet which DNS servers hold the official records for a domain. When a DNS query is initiated, the resolver checks the domain’s NS records to determine which authoritative name servers should provide the final answer. These authoritative servers then return the requested records, such as A, MX, or TXT entries, allowing the website or email service to function correctly.

This delegation system allows domain owners to host DNS with specialized providers while keeping domain registration and hosting services separate.

Common NS Record Configuration Mistakes

Incorrect NS configurations can cause serious domain resolution problems. Some of the most common mistakes include:

• Mixing name servers from different DNS providers during migrations.
• Forgetting to update NS records after switching DNS hosting services.
• Removing default NS entries accidentally, causing domain lookup failures.
• Allowing mismatched NS records between the domain registrar and the DNS zone.

MX Record

An MX (Mail Exchange) record is responsible for directing incoming emails to the correct mail servers associated with a domain. Each MX record contains the hostname of a mail server along with a priority value that determines the order in which mail servers are used. A simple DNS record example looks like:

This entry instructs sending systems to route emails for the domain to the specified mail server.

How do MX Records Route Email?

When an email is sent to [email protected], the sending mail server checks the domain’s DNS settings for MX records. The MX record provides the destination mail server responsible for receiving messages. The sending system then connects directly to that server to deliver the email. If multiple MX records exist, the system follows the priority order to determine which server should be used first.

MX Priority Values Explained Simply

MX records use numerical priority values to manage backup mail servers:

• Lower number = higher priority
• Higher number = backup server
• If the primary server becomes unavailable, email is automatically routed to the next available server.

This priority-based routing ensures reliable email delivery and provides redundancy in case of server downtime.

SOA Record

The SOA (Start of Authority) record defines the primary information about a domain’s DNS zone. It serves as the central control record, containing administrative details and configuration settings that enable DNS servers to manage and synchronize domain data correctly. Every DNS zone contains a single SOA record, and it is automatically created when a domain is set up with a DNS provider. This record helps ensure that all authoritative name servers stay updated with the latest DNS changes.

SOA Record Fields Explained in Simple Terms

An SOA record includes several key fields that manage DNS operations:

• Primary Name Server– The main authoritative DNS server for the domain.
• Responsible Email Address– Contact information for the domain administrator.
• Serial Number– A version number that increases whenever DNS records are updated.
• Refresh Interval– How often secondary DNS servers check for updates.
• Retry Interval– How quickly servers try again if an update check fails.
• Expire Time– How long secondary servers keep existing data if they cannot reach the primary server.
• Minimum TTL– Default caching duration for DNS responses.

These fields work together to maintain consistency across DNS systems.

How SOA Records Help with DNS Synchronization?

The SOA record plays a critical role in keeping multiple DNS servers synchronized. When DNS changes are made, the serial number in the SOA record is updated. Secondary name servers periodically check this number, and if they detect a newer version, they automatically retrieve the updated DNS zone data. This process ensures that DNS updates propagate correctly across all authoritative servers, preventing mismatched or outdated records from affecting domain resolution.

TXT Record

A TXT (Text) record is a flexible type of DNS record used to store text-based information associated with a domain. Among various DNS record types, TXT records are widely used for domain verification, service validation, and email authentication. Many online platforms require TXT records to confirm domain ownership, while email systems rely on them to publish authentication policies that help protect against spoofing and phishing.

Because TXT records can store structured instructions, they are commonly used to define rules that receiving servers check before accepting emails from a domain.

TXT Records For SPF, DKIM, and DMARC

TXT records play a critical role in email security by hosting authentication configurations, such as:

• SPF (Sender Policy Framework): Specifies which mail servers are authorized to send emails on behalf of the domain. You can use EasyDMARC’s SPF record generator to create an SPF TXT record for your domain. 
• DKIM (DomainKeys Identified Mail): Publishes the public cryptographic key used to verify email signatures. You can use EasyDMARC’s DKIM record generator to create a DKIM TXT record for your domain.
• DMARC (Domain-based Message Authentication, Reporting, and Conformance): Defines enforcement policies and reporting instructions for authentication failures. You can use EasyDMARC’s DMARC record generator to create a DMARC TXT record for your domain.

These authentication entries help mailbox providers verify whether incoming emails are legitimate, improving domain trust and email deliverability.

Common TXT Record Length and Formatting Issues

Although TXT records are simple in concept, formatting errors are common and can lead to authentication failures. Some frequent issues include:

• Exceeding character limits for single TXT strings without proper splitting.
• Missing quotation marks or incorrect spacing within record values.
• Publishing multiple conflicting SPF TXT records instead of merging them.
• Copy-paste errors that introduce hidden characters.

DNS Records Comparison Overview

The table below provides a quick, at-a-glance summary of the most common DNS record types, their primary purpose, and where they are typically used.

Understanding DNS Records: Key Takeaways

Understanding the most common DNS record types helps ensure that your website loads correctly, your emails are delivered reliably, and your domain remains properly authenticated. From A and AAAA records that connect users to your servers to MX, PTR, and TXT records that support secure email delivery, each record plays a specific role in maintaining a healthy domain infrastructure.

However, managing DNS manually can quickly become complex, especially when configuring email authentication records like SPF, DKIM, and DMARC. EasyDMARC simplifies this process with automated tools that help you generate, validate, and monitor your DNS authentication records, reducing configuration errors and improving deliverability. Create your account and start yourfree 14-day trial to gain better visibility into your domain’s email security and ensure your DNS settings are always working as intended.