{"id":28211,"date":"2022-06-15T10:54:01","date_gmt":"2022-06-15T10:54:01","guid":{"rendered":"https:\/\/easydmarc.com\/blog\/?p=28211"},"modified":"2026-11-05T12:22:24","modified_gmt":"2026-11-05T12:22:24","slug":"top-8-most-common-types-of-dns-records","status":"publish","type":"post","link":"https:\/\/easydmarc.com\/blog\/top-8-most-common-types-of-dns-records\/","title":{"rendered":"Top 8 Most Common DNS Records Types"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">DNS records are instructions stored in your domain\u2019s DNS zone that tell the internet how to handle requests related to your domain, and each of the common DNS record types handles one specific kind of request. 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.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">As a domain owner or marketing professional, it\u2019s 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. This guide covers the most common DNS record types explained one by one, with what each record does, how it is formatted, and how to check your own configuration.<\/p>\n\n\n\n<div style=\"text-align: center;\">\n<p><iframe title=\"YouTube video player\" src=\"https:\/\/www.youtube.com\/embed\/62qVTVeCupk\" width=\"560\" height=\"315\" frameborder=\"0\" allowfullscreen=\"allowfullscreen\"><\/iframe><\/p>\n<\/div>\n\n\n\n<h2 id=\"h-what-is-a-dns-record\" class=\"wp-block-heading\">What Is a DNS Record?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A DNS record is a single entry in a domain&#8217;s DNS zone file. Each record maps a name to a value and tells resolvers how to answer one specific type of query. Together, the records in a zone form the instruction set that browsers, mail servers, and other systems rely on when they look up your domain.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Most of the common DNS record types share the same basic fields:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Host (or name):<\/strong> the domain or subdomain the record applies to. The @ symbol refers to the root domain.<\/li>\n\n\n\n<li><strong>Record type:<\/strong> the category of record, such as A, MX, or TXT.<\/li>\n\n\n\n<li><strong>Value:<\/strong> the data returned, such as an IP address, a hostname, or a text string.<\/li>\n\n\n\n<li><strong>TTL:<\/strong> how long resolvers may cache the answer, in seconds.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Some types add their own fields. MX records include a priority value, and SOA records carry a set of zone management fields. This structure is defined in RFC 1035, which is why the same fields appear across nearly every DNS provider even when the interface looks different.<\/p>\n\n\n\n<h2 id=\"h-the-8-most-common-dns-record-types-at-a-glance\" class=\"wp-block-heading\">The 8 Most Common DNS Record Types at a Glance<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The table below summarizes the eight most common DNS record types, what each one does, and where it is typically used. Each record is covered in detail in the section that follows.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><td><strong>DNS Record Type<\/strong><\/td><td><strong>Main Purpose<\/strong><\/td><td><strong>What It Points To<\/strong><\/td><td><strong>Common Use Case<\/strong><\/td><\/tr><tr><td><strong>A<\/strong><\/td><td>Connects a domain to a server<\/td><td>IPv4 address<\/td><td>Website hosting (example.com \u2192 server IP)<\/td><\/tr><tr><td><strong>AAAA<\/strong><\/td><td>Connects a domain to a server<\/td><td>IPv6 address<\/td><td>IPv6-enabled website hosting<\/td><\/tr><tr><td><strong>CNAME<\/strong><\/td><td>Creates a domain alias<\/td><td>Another domain name<\/td><td>Redirects www or subdomains to a main domain<\/td><\/tr><tr><td><strong>NS<\/strong><\/td><td>Defines authoritative DNS servers<\/td><td>Name server hostnames<\/td><td>Delegating DNS authority for a domain<\/td><\/tr><tr><td><strong>SOA<\/strong><\/td><td>Provides DNS zone control info<\/td><td>DNS administrative settings<\/td><td>DNS synchronization and zone management<\/td><\/tr><tr><td><strong>MX<\/strong><\/td><td>Routes incoming emails<\/td><td>Mail server hostname<\/td><td>Directing emails to Google Workspace, Microsoft 365, etc.<\/td><\/tr><tr><td><strong>TXT<\/strong><\/td><td>Stores text-based policies and verification data<\/td><td>Text instructions<\/td><td>SPF, DKIM, DMARC, and domain verification<\/td><\/tr><tr><td><strong>PTR<\/strong><\/td><td>Performs reverse lookup<\/td><td>IP address \u2192 domain<\/td><td>Email server identity verification and reverse DNS<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 id=\"h-records-that-point-your-domain-to-a-server-nbsp\" class=\"wp-block-heading\">Records That Point Your Domain to a Server&nbsp;<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Three record types handle the basic job of resolving a name to a destination: A, AAAA, and CNAME.<\/p>\n\n\n\n<h3 id=\"h-a-record-maps-a-domain-to-an-ipv4-address\" class=\"wp-block-heading\">A Record: Maps a Domain to an IPv4 Address<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><span style=\"font-weight: 400;\">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 \u201cA\u201d stands for Address, meaning the record tells resolvers which server address should respond when someone enters your domain in a browser.<\/span><\/p>\n\n\n\n<h4 id=\"h-how-a-records-work-nbsp\" class=\"wp-block-heading\">How A Records Work&nbsp;<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">When a user types a domain name into a browser, the <a href=\"https:\/\/easydmarc.com\/tools\/dns-record-checker\">DNS lookup<\/a> searches for the domain\u2019s A record and returns the correct IPv4 address. The browser then connects to that address and loads the website. For example, when someone visits easydmarc.com, the A record directs the browser request to the IPv4 server hosting the site. The process usually completes in milliseconds and is what allows people to use domain names instead of numerical IP addresses.<\/p>\n\n\n\n<h4 id=\"h-example-and-common-use-cases-nbsp\" class=\"wp-block-heading\">Example and Common Use Cases&nbsp;<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">A typical A record example looks like this:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><td>\n<p style=\"text-align: center;\"><b>Host<\/b><\/p>\n<\/td><td class=\"has-text-align-center\" data-align=\"center\">\n<p><b>Record Type<\/b><\/p>\n<\/td><td class=\"has-text-align-center\" data-align=\"center\">\n<p><b>Value<\/b><\/p>\n<\/td><td class=\"has-text-align-center\" data-align=\"center\">\n<p style=\"text-align: center;\"><b>TTL<\/b><\/p>\n<\/td><\/tr><tr><td>\n<p style=\"text-align: center;\"><span style=\"font-weight: 400;\">&nbsp; &nbsp; @<\/span><\/p>\n<\/td><td class=\"has-text-align-center\" data-align=\"center\">\n<p><span style=\"font-weight: 400;\">A<\/span><\/p>\n<\/td><td class=\"has-text-align-center\" data-align=\"center\">\n<p><span style=\"font-weight: 400;\">192.168.10.1<\/span><\/p>\n<\/td><td>\n<p style=\"text-align: center;\"><span style=\"font-weight: 400;\">14400<\/span><\/p>\n<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\"><span style=\"font-weight: 400;\">A records are widely used in everyday domain management, including:<\/span><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><span style=\"font-weight: 400;\">Pointing the root domain (example.com) to a website hosting server.<\/span><\/li>\n\n\n\n<li><span style=\"font-weight: 400;\">Connecting subdomains such as shop.example.com or blog.example.com to specific servers.<\/span><\/li>\n\n\n\n<li><span style=\"font-weight: 400;\">Setting up basic load balancing by using multiple A records.<\/span><\/li>\n\n\n\n<li><span style=\"font-weight: 400;\">Creating redundancy so traffic can continue to flow if a server fails.<\/span><\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><span style=\"font-weight: 400;\">Because nearly every website depends on an A record to function, it is considered one of the foundational components of DNS configuration. An <a href=\"https:\/\/easydmarc.com\/tools\/a-record-lookup\">A record lookup<\/a> confirms which IPv4 address a hostname currently resolves to, which is the first thing to check when a site stops loading after a hosting change.<\/span><\/p>\n\n\n\n<h4 id=\"h-common-a-record-mistakes\" class=\"wp-block-heading\">Common A Record Mistakes<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">A few configuration errors account for most A record problems:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Pointing a public hostname at a private address such as 192.168.1.10, which is not routable on the internet.<\/li>\n\n\n\n<li>Leaving stale A records in place after a hosting migration, so some traffic still reaches a decommissioned server.<\/li>\n\n\n\n<li>Publishing an A record and a CNAME on the same hostname, which is invalid and produces inconsistent resolution.<\/li>\n\n\n\n<li>Forgetting the www host, so example.com resolves while www.example.com does not.<\/li>\n\n\n\n<li>Leaving a long TTL in place before a planned migration, which extends the window in which resolvers keep serving the old address.<\/li>\n<\/ul>\n\n\n\n<h2 id=\"h-aaaa-record-maps-a-domain-to-an-ipv6-address\" class=\"wp-block-heading\"><b>AAAA Record<\/b>: Maps a Domain to an IPv6 Address<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><span style=\"font-weight: 400;\">An AAAA record is another important entry among common DNS record types. It performs the same function as an A record for IPv6, mapping a domain to a 128-bit IPv6 address. The format was introduced to address the global shortage of IPv4 addresses. The name comes from the size of that address: an IPv6 address is four times the length of a 32-bit IPv4 address, so the record type is written with four As.<\/span><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><span style=\"font-weight: 400;\">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.<\/span><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><span style=\"font-weight: 400;\">Here is the example of a typical AAAA record:<\/span><\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><td><span style=\"font-weight: 400;\">Host<\/span><\/td><td><span style=\"font-weight: 400;\">Record type:<\/span><\/td><td><span style=\"font-weight: 400;\">Value:<\/span><\/td><td><span style=\"font-weight: 400;\">TTL<\/span><\/td><\/tr><tr><td><span style=\"font-weight: 400;\">@<\/span><\/td><td><span style=\"font-weight: 400;\">AAAA<\/span><\/td><td><span style=\"font-weight: 400;\">2001:db8:85a3::8a2e:370:7334<\/span><\/td><td><span style=\"font-weight: 400;\">14400<\/span><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h4 id=\"h-a-vs-aaaa-records\" class=\"wp-block-heading\"><b>A vs. AAAA Records<\/b><\/h4>\n\n\n\n<p class=\"wp-block-paragraph\"><span style=\"font-weight: 400;\">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).<\/span><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><span style=\"font-weight: 400;\">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\u2019s why using both records ensures that users on either IPv4 or IPv6 networks can reach the same website without any disruption.<\/span><\/p>\n\n\n\n<h4 id=\"h-when-you-actually-need-an-aaaa-record\" class=\"wp-block-heading\"><b>When You Actually Need an AAAA Record<\/b><\/h4>\n\n\n\n<p class=\"wp-block-paragraph\"><span style=\"font-weight: 400;\">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:<\/span><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><span style=\"font-weight: 400;\">Prepare their domains for long-term internet scalability.<\/span><\/li>\n\n\n\n<li><span style=\"font-weight: 400;\">Improve global accessibility in regions where IPv6 adoption is high.<\/span><\/li>\n\n\n\n<li><span style=\"font-weight: 400;\">Meet hosting provider or compliance requirements that mandate IPv6 support.<\/span><\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><span style=\"font-weight: 400;\">Publish an AAAA record only when the destination actually answers on IPv6. An AAAA record that points to an address that does not respond can cause connection delays for IPv6 clients, because clients try IPv6 first and only fall back to IPv4 after a short delay or failure.\u201d.<\/span><\/p>\n\n\n\n<h3 id=\"h-cname-record-points-one-domain-to-another\" class=\"wp-block-heading\"><b>CNAME Record<\/b>: Points One Domain to Another<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><span style=\"font-weight: 400;\">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.<\/span><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><span style=\"font-weight: 400;\">A typical DNS record example for a CNAME entry may look like:<\/span><\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><td><br \/><p style=\"text-align: center;\"><b>Host<\/b><\/p><\/td><td class=\"has-text-align-center\" data-align=\"center\"><br \/><p><b>Record Type<\/b><\/p><\/td><td class=\"has-text-align-center\" data-align=\"center\"><br \/><p><b>Value<\/b><\/p><\/td><td class=\"has-text-align-center\" data-align=\"center\"><br \/><p><b>TTL<\/b><\/p><\/td><\/tr><tr><td><br \/><p style=\"text-align: center;\"><span style=\"font-weight: 400;\">www<\/span><\/p><\/td><td class=\"has-text-align-center\" data-align=\"center\"><br \/><p><span style=\"font-weight: 400;\">CNAME<\/span><\/p><\/td><td class=\"has-text-align-center\" data-align=\"center\"><br \/><p><span style=\"font-weight: 400;\">example.com<\/span><\/p><\/td><td class=\"has-text-align-center\" data-align=\"center\"><br \/><p><span style=\"font-weight: 400;\">3600<\/span><\/p><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\"><span style=\"font-weight: 400;\">This configuration tells DNS resolvers that any query for www.example.com should be answered using the records published for example.com.<\/span><\/p>\n\n\n\n<h4 id=\"h-how-cname-records-work\" class=\"wp-block-heading\"><b>How CNAME Records Work?<\/b><\/h4>\n\n\n\n<p class=\"wp-block-paragraph\"><span style=\"font-weight: 400;\">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.<\/span> A <a href=\"https:\/\/easydmarc.com\/tools\/cname-lookup\">CNAME record checker<\/a> confirms which canonical hostname an alias currently resolves to.<\/p>\n\n\n\n<h4 id=\"h-why-cname-can-t-be-used-at-the-root-domain\" class=\"wp-block-heading\">Why CNAME Can&#8217;t Be Used at the Root Domain<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">The root, or apex, of a domain has to carry SOA and NS records. DNS rules do not allow a hostname holding a CNAME to hold other record types at the same name, so a CNAME cannot be published at the apex. Most DNS providers reject the attempt outright.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Providers that support apex aliasing offer ALIAS or ANAME records instead. These behave like a CNAME from the reader&#8217;s point of view, and the DNS provider resolves the target and returns A or AAAA records in the response, which keeps the apex compliant. Support and naming vary by provider, so confirm what your DNS host offers before planning around it.<\/p>\n\n\n\n<h4 id=\"h-cname-chaining-and-best-practices\" class=\"wp-block-heading\"><b>CNAME Chaining and Best Practices<\/b><\/h4>\n\n\n\n<p class=\"wp-block-paragraph\"><span style=\"font-weight: 400;\">Although CNAME records are very useful, they have certain limitations that must be considered:<\/span><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><span style=\"font-weight: 400;\">A CNAME record usually cannot be placed at the root (apex) domain in many DNS configurations.<\/span><\/li>\n\n\n\n<li><span style=\"font-weight: 400;\">A hostname with a CNAME record should not contain other record types simultaneously.<\/span><\/li>\n\n\n\n<li><span style=\"font-weight: 400;\">Excessive CNAME chaining adds lookup time through multiple resolution steps, and a broken link anywhere in the chain breaks the whole path.<\/span><\/li>\n\n\n\n<li><span style=\"font-weight: 400;\">It is best to use CNAME records mainly for subdomains such as www, app, or shop.<\/span><\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><span style=\"font-weight: 400;\">DKIM keys are frequently published as CNAME records that point to a provider&#8217;s hosted key, so the same chaining rules apply directly to email authentication. If the provider&#8217;s target stops resolving, DKIM verification fails for every message that service signs.<\/span><\/p>\n\n\n\n<h2 id=\"h-records-that-control-dns-authority\" class=\"wp-block-heading\">Records That Control DNS Authority<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Two record types govern who is allowed to answer for your domain and how those answers stay consistent across servers.<\/p>\n\n\n\n<h3 id=\"h-ns-record-names-the-authoritative-servers-for-your-domain\" class=\"wp-block-heading\">NS Record: Names the Authoritative Servers for Your Domain<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><span style=\"font-weight: 400;\">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\u2019s records. Without properly configured NS records, browsers and email systems would not know where to retrieve the domain\u2019s DNS settings.<\/span><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><span style=\"font-weight: 400;\">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.<\/span><\/p>\n\n\n\n<h4 id=\"h-how-ns-records-delegate-authority\" class=\"wp-block-heading\">How NS Records Delegate Authority<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\"><span style=\"font-weight: 400;\">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\u2019s 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.<\/span><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><span style=\"font-weight: 400;\">This delegation system allows domain owners to host DNS with specialized providers while keeping domain registration and hosting services separate.<\/span><\/p>\n\n\n\n<h4 id=\"h-common-ns-record-configuration-mistakes\" class=\"wp-block-heading\"><b>Common NS Record Configuration Mistakes<\/b><\/h4>\n\n\n\n<p class=\"wp-block-paragraph\"><span style=\"font-weight: 400;\">Incorrect NS configurations can cause serious domain resolution problems. Some of the most common mistakes include:<\/span><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><span style=\"font-weight: 400;\">Mixing name servers from different DNS providers during migrations.<\/span><\/li>\n\n\n\n<li><span style=\"font-weight: 400;\">Forgetting to update NS records after switching DNS hosting services.<\/span><\/li>\n\n\n\n<li><span style=\"font-weight: 400;\">Removing default NS entries accidentally, causing domain lookup failures.<\/span><\/li>\n\n\n\n<li><span style=\"font-weight: 400;\">Allowing mismatched NS records between the domain registrar and the DNS zone.<\/span><\/li>\n<\/ul>\n\n\n\n<h3 id=\"h-soa-record-defines-the-zone-s-master-settings\" class=\"wp-block-heading\">SOA Record: Defines the Zone&#8217;s Master Settings<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The SOA (Start of Authority) record defines the primary information about a domain\u2019s 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 are kept up to date with the latest DNS changes. These fields work together to maintain consistency across DNS systems.&nbsp;<\/p>\n\n\n\n<h3 id=\"h-soa-record-fields-explained-in-simple-terms\" class=\"wp-block-heading\">SOA Record Fields Explained in Simple Terms<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">An SOA record includes several key fields that manage DNS operations:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Primary Name Server:<\/strong> The main authoritative DNS server for the domain.<\/li>\n\n\n\n<li><strong>Responsible Email Address:<\/strong> Contact information for the domain administrator, written in DNS format with the @ replaced by a dot.<\/li>\n\n\n\n<li><strong>Serial Number:<\/strong> A version number that increases whenever DNS records are updated.<\/li>\n\n\n\n<li><strong>Refresh Interval:<\/strong> How often secondary DNS servers check for updates.<\/li>\n\n\n\n<li><strong>Retry Interval:<\/strong> How quickly servers try again if an update check fails.<\/li>\n\n\n\n<li><strong>Expire Time:<\/strong> How long secondary servers keep existing data if they cannot reach the primary server.<\/li>\n\n\n\n<li><strong>Minimum TTL:<\/strong> The caching duration applied to negative responses, meaning answers for names that do not exist.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">These fields work together to maintain consistency across DNS systems, and each one is covered in more depth in our guide to the <a href=\"https:\/\/easydmarc.com\/blog\/what-is-soa-record-in-dns\/\">SOA record in DNS<\/a>.<\/p>\n\n\n\n<h4 id=\"h-how-soa-keeps-dns-servers-in-sync\" class=\"wp-block-heading\">How SOA Keeps DNS Servers in Sync<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">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. An <a href=\"https:\/\/easydmarc.com\/tools\/soa-record-lookup\">SOA record lookup<\/a> shows the current serial number and timer values for a zone, which is useful when confirming that a change has been picked up by every authoritative server.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">An incorrect SOA serial number can prevent secondary DNS servers from recognizing zone updates. Learn how to identify and fix an <a href=\"https:\/\/easydmarc.com\/blog\/soa-serial-number-format-is-invalid\/\" target=\"_blank\" rel=\"noreferrer noopener\">invalid SOA serial number format<\/a> to help maintain consistent DNS synchronization.<\/p>\n\n\n\n<h2 id=\"h-records-that-make-email-work\" class=\"wp-block-heading\">Records That Make Email Work<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Email delivery depends on a specific group of DNS records. MX records route incoming mail, TXT records publish the authentication policies receiving servers evaluate, and PTR records support the reverse DNS checks run against the sending IP address.<\/p>\n\n\n\n<h3 id=\"h-mx-record-routes-incoming-email-to-your-mail-servers\" class=\"wp-block-heading\">MX Record: Routes Incoming Email to Your Mail Servers<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">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:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><td><strong>Host<\/strong><\/td><td><strong>Record Type<\/strong><\/td><td><strong>Value<\/strong><\/td><td><strong>Priority<\/strong><\/td><td><strong>TTL<\/strong><\/td><\/tr><tr><td>@<\/td><td>MX<\/td><td>mail.example.com<\/td><td>10<\/td><td>3600<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">This entry instructs sending systems to route emails for the domain to the specified mail server.<\/p>\n\n\n\n<h4 id=\"h-how-mx-records-route-email\" class=\"wp-block-heading\">How MX Records Route Email<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">When an email is sent to user@example.com, the sending mail server checks the domain\u2019s 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. An MX record has to point to a hostname, never to an IP address, and that hostname has to resolve to an A or AAAA record. An <a href=\"https:\/\/easydmarc.com\/tools\/mx-lookup\">MX record lookup<\/a> returns the mail servers and priorities currently published for a domain, which is the first check to run when inbound mail stops arriving.<\/p>\n\n\n\n<h4 id=\"h-mx-priority-values-explained-simply\" class=\"wp-block-heading\">MX Priority Values Explained Simply<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">MX records use numerical priority values to manage backup mail servers:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Lower number = higher priority. The lowest value is tried first.<\/li>\n\n\n\n<li>Higher number = backup server<\/li>\n\n\n\n<li>Records sharing the same value split traffic between them.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">This priority-based routing ensures reliable email delivery and provides redundancy in case of server downtime.<\/p>\n\n\n\n<h3 id=\"h-txt-record-stores-verification-and-authentication-data\" class=\"wp-block-heading\">TXT Record: Stores Verification and Authentication Data<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">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 receiving servers evaluate before deciding how to treat a message.<\/p>\n\n\n\n<h4 id=\"h-txt-records-for-spf-dkim-and-dmarc\" class=\"wp-block-heading\">TXT Records for SPF, DKIM, and DMARC<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">Three email authentication standards are published as TXT records, each at a different host inside the zone.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>SPF (Sender Policy Framework)<\/strong> is published at the root of the domain and lists the servers authorized to send on its behalf. A receiving server compares the connecting IP address against that list. SPF evaluation is capped at 10 DNS lookups, and exceeding the cap returns a permanent error that DMARC treats as a failure, so records that include several third-party senders need to be kept within that limit. You can <a href=\"https:\/\/easydmarc.com\/tools\/spf-record-generator\">generate a correctly formatted SPF record<\/a> before publishing, which avoids the syntax errors that cause most SPF failures.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>DKIM (DomainKeys Identified Mail)<\/strong> is published at a selector host in the form selector._domainkey.example.com, and contains the public key receiving servers use to verify the cryptographic signature on a message. A valid signature confirms that the message was signed by the domain and that the signed content was not altered in transit. It does not establish that the sender is trustworthy. Each sending service uses its own selector, so a domain sending through several providers publishes several DKIM records. You can <a href=\"https:\/\/easydmarc.com\/tools\/dkim-record-generator\">generate a DKIM record<\/a> for a new selector.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>DMARC (Domain-based Message Authentication, Reporting, and Conformance)<\/strong> is published at _dmarc.example.com. It tells receiving servers what to do with messages that fail authentication and where to send reports. DMARC also requires alignment: the domain in the visible From header has to match the domain validated by SPF or DKIM, which is a separate condition from SPF or DKIM passing on their own. Reporting is aggregate, so DMARC provides visibility into how a domain is being used across a reporting window rather than message-level alerting. You can <a href=\"https:\/\/easydmarc.com\/tools\/dmarc-record-generator\">generate a DMARC record<\/a> with the policy and reporting addresses you need.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Together, these records let mailbox providers determine whether a message is authorized to use your domain. Authentication does not guarantee inbox placement. It gives receiving servers a verifiable basis for separating authorized mail from messages that only claim to come from you.<\/p>\n\n\n\n<h4 id=\"h-length-and-formatting-issues-255-character-strings\" class=\"wp-block-heading\">Length and Formatting Issues (255-Character Strings)<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">Although TXT records are simple in concept, formatting errors are common and can lead to authentication failures. Some frequent issues include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>A single TXT string exceeding the 255-character limit.<\/li>\n\n\n\n<li>Missing quotation marks or incorrect spacing within record values.<\/li>\n\n\n\n<li>Publishing multiple conflicting SPF TXT records instead of merging them.<\/li>\n\n\n\n<li>Copy-paste errors that introduce hidden characters.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Long values such as 2048-bit DKIM keys have to be split into multiple quoted strings inside one record, which resolvers concatenate on retrieval. A <a href=\"https:\/\/easydmarc.com\/tools\/txt-record-lookup\">TXT record lookup<\/a> shows the value exactly as resolvers see it, which is the fastest way to confirm that a new record was published correctly.<\/p>\n\n\n\n<h3 id=\"h-ptr-record-maps-an-ip-address-back-to-a-domain\" class=\"wp-block-heading\">PTR Record: Maps an IP Address Back to a Domain<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">A PTR (Pointer) record is used for reverse DNS lookups. It maps an IP address back to a hostname, which is the reverse of what most record types do. Reverse DNS is used to check whether the host behind a sending IP address identifies itself consistently.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">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. They live in a reverse DNS zone owned by that provider, so domain owners request them rather than publishing them in their own zone.<\/p>\n\n\n\n<h4 id=\"h-how-reverse-dns-lookup-works\" class=\"wp-block-heading\">How Reverse DNS Lookup Works<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">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, a check known as forward-confirmed reverse DNS. A <a href=\"https:\/\/easydmarc.com\/tools\/ptr-record-lookup\">PTR lookup<\/a> returns the hostname published for a given IP address, which is how you verify what your sending infrastructure looks like from the receiving side.<\/p>\n\n\n\n<h4 id=\"h-why-ptr-records-matter-for-deliverability\" class=\"wp-block-heading\">Why PTR Records Matter for Deliverability<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">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. Reverse DNS is evaluated at connection time, before message content or authentication results are considered.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Missing or mismatched PTR records can cause emails to be flagged as suspicious, routed to spam folders, or rejected entirely. If you send from IP addresses under your control, request a PTR record that matches the hostname your mail server announces in its HELO or EHLO greeting. If you send through a provider, that provider controls the PTR record for its shared IPs, and the hostname it publishes is the one receivers will see.<\/p>\n\n\n\n<h2 id=\"h-ttl-how-long-dns-records-are-cached\" class=\"wp-block-heading\">TTL: How Long DNS Records Are Cached<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Every DNS record carries a TTL (time to live) value, expressed in seconds, that tells resolvers how long they may cache the answer before querying again. A TTL of 3600 permits one hour of caching. A TTL of 14400, the value used in the examples above, permits four hours.<\/p>\n\n\n\n<h3 id=\"h-choosing-a-ttl-value\" class=\"wp-block-heading\">Choosing a TTL Value<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">TTL is a trade-off between how quickly changes take effect and how much query traffic reaches your name servers.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Stable records such as NS entries usually carry longer TTLs, often 86400 seconds.<\/li>\n\n\n\n<li>Records that change more often, including A records and authentication TXT records, are commonly set between 300 and 3600 seconds.<\/li>\n\n\n\n<li>Before a planned change, lower the TTL on the affected records and wait for the previous TTL to expire. Once the change is live and verified, raise it back.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Lowering a TTL after publishing a change has no effect on resolvers that already cached the previous value. The reduction applies only to lookups made once the cached entry expires.<\/p>\n\n\n\n<h3 id=\"h-why-changes-don-t-take-effect-immediately\" class=\"wp-block-heading\">Why Changes Don&#8217;t Take Effect Immediately<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">DNS changes are commonly described as propagating. In practice, authoritative name servers publish the new value immediately, and every resolver that already cached the old value keeps serving it until its TTL expires. Users behind different resolvers therefore see the change at different times.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This matters when publishing or updating email authentication records. A lookup tool can return the new record while some receiving servers are still evaluating the cached version, so allow the full previous TTL to elapse before concluding that a change did not work.<\/p>\n\n\n\n<h2 id=\"h-other-dns-records-worth-knowing\" class=\"wp-block-heading\">Other DNS Records Worth Knowing<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Several record types fall outside the eight most common but appear regularly in enterprise environments.<\/p>\n\n\n\n<h3 id=\"h-srv-caa-and-alias-aname-records\" class=\"wp-block-heading\">SRV, CAA, and ALIAS\/ANAME Records<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>SRV (Service) records<\/strong> publish the hostname and port for a specific service on a domain, using the format _service._protocol.example.com. Microsoft 365, SIP, and XMPP deployments rely on them for client autodiscovery.<\/li>\n\n\n\n<li><strong>CAA (Certification Authority Authorization) records<\/strong> specify which certificate authorities are permitted to issue certificates for a domain. Certificate authorities are required to check CAA records before issuance, which makes them a practical control against unauthorized certificate issuance.<\/li>\n\n\n\n<li><strong>ALIAS and ANAME records<\/strong> provide CNAME-like behavior at the domain apex. They are provider-specific implementations rather than a standardized record type, and the DNS provider resolves the target and returns A or AAAA records in the response.<\/li>\n<\/ul>\n\n\n\n<h3 id=\"h-why-the-standalone-spf-record-type-was-deprecated\" class=\"wp-block-heading\">Why the Standalone SPF Record Type Was Deprecated<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">DNS once had a dedicated record type for SPF, registered as type 99. It was intended to give SPF its own record rather than sharing the TXT type. Adoption stayed low, resolvers and DNS providers supported it inconsistently, and domains that published both versions often let the two drift out of sync.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">RFC 7208 removed it in 2014. SPF policies are published only as TXT records today. If a legacy type 99 record still exists in a zone, it can be removed once the TXT version is confirmed correct.<\/p>\n\n\n\n<h2 id=\"h-how-to-check-your-domain-s-dns-records\" class=\"wp-block-heading\">How to Check Your Domain&#8217;s DNS Records<\/h2>\n\n\n\n<h3 id=\"h-using-a-dns-record-lookup-tool\" class=\"wp-block-heading\">Using a DNS Record Lookup Tool<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">A lookup tool queries a domain and returns its published records in readable form, without requiring command line access. This is the practical option when you need to check records across several domains, share results with people outside the infrastructure team, or inspect a third party&#8217;s zone. A <a href=\"https:\/\/easydmarc.com\/tools\/dns-record-checker\">DNS record checker<\/a> returns A, AAAA, CNAME, MX, TXT, NS, SOA, and PTR records for a domain or IP address in a single query.<\/p>\n\n\n\n<h3 id=\"h-checking-records-from-the-command-line-dig-nslookup\" class=\"wp-block-heading\">Checking Records from the Command Line (dig \/ nslookup)<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">dig is available on macOS and most Linux distributions. nslookup ships with Windows.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Common dig queries:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>dig example.com A +short<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>dig example.com MX<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>dig TXT _dmarc.example.com<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>dig -x 192.0.2.1<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The nslookup equivalents:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>nslookup -type=a example.com<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>nslookup -type=mx example.com<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>nslookup -type=txt _dmarc.example.com<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Both commands query your local resolver by default, which may return a cached answer. To query an authoritative server directly and bypass caching, append the name server: dig example.com MX @ns1.example.com.<\/p>\n\n\n\n<h3 id=\"h-verifying-your-email-records-mx-spf-dkim-dmarc-ptr\" class=\"wp-block-heading\">Verifying Your Email Records (MX, SPF, DKIM, DMARC, PTR)<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Email configuration spans several records published at different hosts, so verification follows a sequence:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>MX records at the domain root, confirming they point to hostnames that resolve.<\/li>\n\n\n\n<li>SPF as a single TXT record at the root, confirming syntax and that DNS lookups stay within the limit of 10.<\/li>\n\n\n\n<li>DKIM as a TXT or CNAME record at every selector host in use, confirming each active sending service has a published key.<\/li>\n\n\n\n<li>DMARC as a TXT record at _dmarc, confirming the policy and the reporting addresses.<\/li>\n\n\n\n<li>PTR for each sending IP under your control, confirming reverse DNS matches the hostname the mail server announces.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">Checking these individually returns a point-in-time result. Across a portfolio of domains and sending sources, the EasyDMARC platform monitors authentication status continuously, and the dashboard displays which domains and sending sources are passing or failing, so configuration drift surfaces without a manual re-check of every zone.<\/p>\n\n\n\n<h2 id=\"h-dns-misconfigurations-that-break-email-delivery\" class=\"wp-block-heading\">DNS Misconfigurations That Break Email Delivery<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A small number of DNS errors account for most authentication and delivery failures:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Multiple SPF records on one host.<\/strong> A domain may publish only one SPF TXT record. A second causes a permanent error, and DMARC evaluates that error as an SPF failure.<\/li>\n\n\n\n<li><strong>SPF exceeding the 10 DNS lookup limit.<\/strong> Every include, a, mx, and redirect mechanism consumes lookups. Adding sending services over time pushes a record past the limit with no visible change to the record itself.<\/li>\n\n\n\n<li><strong>DKIM selectors that were never published.<\/strong> A sending service signs with a selector that has no corresponding record in DNS, so verification fails for everything it sends.<\/li>\n\n\n\n<li><strong>DMARC published at the wrong host.<\/strong> The record has to sit at _dmarc.example.com. Published at the root, it is ignored.<\/li>\n\n\n\n<li><strong>Stale records after a migration.<\/strong> Old A, MX, or authentication records left in a zone after a provider change produce inconsistent results depending on which record a receiver reads.<\/li>\n\n\n\n<li><strong>Reverse DNS that does not match.<\/strong> A sending IP whose PTR record does not resolve back to the hostname the server announces looks misconfigured to receivers.<\/li>\n\n\n\n<li><strong>Alignment overlooked.<\/strong> SPF or DKIM can pass while DMARC still fails, because DMARC requires the passing domain to align with the domain in the From header.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">These conditions surface in DMARC aggregate reports, which show authentication and alignment results per sending source. Aggregate reporting covers a reporting window rather than individual messages in real time, so it supports investigation and enforcement decisions rather than immediate alerting.<\/p>\n\n\n\n<h2 id=\"h-understanding-dns-records-key-takeaways\" class=\"wp-block-heading\">Understanding DNS Records: Key Takeaways<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">With the most common DNS record types explained, the practical benefit is a domain where the website loads correctly, email is delivered reliably, and authentication holds up under checks from receiving servers. 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.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">However, managing DNS manually can quickly become complex, especially when configuring email authentication records like SPF, DKIM, and DMARC. The EasyDMARC platform helps you generate, validate, and monitor your DNS authentication records across all your domains, reducing configuration errors and improving deliverability. Create your account and start your <a href=\"https:\/\/uac.easydmarc.com\/realms\/easydmarc\/protocol\/openid-connect\/registrations?client_id=dmarc-app&amp;response_type=code&amp;scope=openid+email&amp;redirect_uri=https%3A%2F%2Fapp.easydmarc.com%2Flogin%2Fcallback&amp;ui_locales=US&amp;utm_source=&amp;state=eyJ1c2VySXAiOiIyNDA2OmI0MDA6NzI6YWNkMjo5MDc5OmI4MDg6ZjcwOmYxN2EiLCJnb1VybCI6IiIsImxvZ2luT3B0aW9ucyI6e319\">free 14-day trial<\/a> to gain better visibility into your domain\u2019s email security and ensure your DNS settings are always working as intended.<\/p>\n\n\n\n<h2 id=\"h-dns-record-faqs\" class=\"wp-block-heading\">DNS Record FAQs<\/h2>\n\n\n\n<div class=\"schema-faq wp-block-yoast-faq-block\"><div class=\"schema-faq-section\" id=\"faq-question-1793363826621\"><strong class=\"schema-faq-question\">What are the common DNS record types?<\/strong> <p class=\"schema-faq-answer\">The eight most common are A, AAAA, CNAME, NS, SOA, MX, TXT, and PTR. A and AAAA map a domain to IPv4 and IPv6 addresses, CNAME creates an alias to another hostname, NS delegates authority to name servers, SOA holds the zone&#8217;s administrative settings, MX routes incoming email, TXT stores verification and authentication data including SPF, DKIM, and DMARC, and PTR maps an IP address back to a hostname.<\/p> <\/div> <div class=\"schema-faq-section\" id=\"faq-question-1793363837934\"><strong class=\"schema-faq-question\">Which DNS records are required for email?<\/strong> <p class=\"schema-faq-answer\">MX records are required to receive email. For sending, SPF and DKIM are published as TXT records and DMARC as a TXT record at _dmarc, and major mailbox providers now require all three from bulk senders. PTR records are managed by whoever controls the sending IP address and are checked by receiving servers at connection time.<\/p> <\/div> <div class=\"schema-faq-section\" id=\"faq-question-1793363838600\"><strong class=\"schema-faq-question\">What&#8217;s the difference between an A record and a CNAME?<\/strong> <p class=\"schema-faq-answer\">An A record points a hostname directly to an IPv4 address. A CNAME points a hostname to another hostname, which is then resolved to an address in a second lookup. A records can be published at the domain apex; CNAME records cannot, because the apex has to hold SOA and NS records at the same name.<\/p> <\/div> <div class=\"schema-faq-section\" id=\"faq-question-1793363840184\"><strong class=\"schema-faq-question\">Can a domain have more than one A record or MX record?<\/strong> <p class=\"schema-faq-answer\">Yes. Multiple A records on the same hostname return several IPv4 addresses and are used for redundancy and load distribution. Multiple MX records are standard, with priority values setting the order in which sending servers try them. SPF is the exception: only one SPF TXT record may be published per host.<\/p> <\/div> <div class=\"schema-faq-section\" id=\"faq-question-1793363841467\"><strong class=\"schema-faq-question\">How long do DNS changes take to propagate?<\/strong> <p class=\"schema-faq-answer\">Authoritative name servers publish a change immediately. How long it takes to be visible everywhere depends on the TTL set on the previous version of the record, because resolvers keep serving the cached value until it expires. A record with a TTL of 3600 can take up to an hour to clear everywhere. Nameserver changes made at the registrar take longer, commonly 24 to 48 hours.<\/p> <\/div> <\/div>\n","protected":false},"excerpt":{"rendered":"<p>DNS records are instructions stored in your domain\u2019s DNS zone that tell the internet how to handle requests related to your domain, and each of the common DNS record types handles one specific kind of request. These instructions decide where your website loads from, which servers can send emails on your behalf, and how incoming [&hellip;]<\/p>\n","protected":false},"author":25,"featured_media":64207,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[306,205],"tags":[562,566],"class_list":["post-28211","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-dns-records","category-knowledge-base","tag-dns","tag-platform"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v28.8 (Yoast SEO v28.8) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>Top 8 Most Common Types of DNS Records | EasyDMARC<\/title>\n<meta name=\"description\" content=\"Learn the 8 most common DNS record types, including A, AAAA, CNAME, MX, TXT, and more, with simple explanations and examples.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/easydmarc.com\/blog\/top-8-most-common-types-of-dns-records\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Top 8 Most Common DNS Records Types\" \/>\n<meta property=\"og:description\" content=\"Learn the 8 most common DNS record types, including A, AAAA, CNAME, MX, TXT, and more, with simple explanations and examples.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/easydmarc.com\/blog\/top-8-most-common-types-of-dns-records\/\" \/>\n<meta property=\"og:site_name\" content=\"EasyDMARC\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/EasyDMARC\/\" \/>\n<meta property=\"article:published_time\" content=\"2022-06-15T10:54:01+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-11-05T12:22:24+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/easydmarc.com\/blog\/wp-content\/uploads\/2022\/06\/DNS-Records-Hero.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1440\" \/>\n\t<meta property=\"og:image:height\" content=\"910\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Hagop K.\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@easydmarc\" \/>\n<meta name=\"twitter:site\" content=\"@easydmarc\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Hagop K.\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"23 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/easydmarc.com\\\/blog\\\/top-8-most-common-types-of-dns-records\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/easydmarc.com\\\/blog\\\/top-8-most-common-types-of-dns-records\\\/\"},\"author\":{\"name\":\"Hagop K.\",\"@id\":\"https:\\\/\\\/easydmarc.com\\\/blog\\\/#\\\/schema\\\/person\\\/740e38b8d7f98e6c4141ae2931ca5a2a\"},\"headline\":\"Top 8 Most Common DNS Records Types\",\"datePublished\":\"2022-06-15T10:54:01+00:00\",\"dateModified\":\"2026-11-05T12:22:24+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/easydmarc.com\\\/blog\\\/top-8-most-common-types-of-dns-records\\\/\"},\"wordCount\":5110,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/easydmarc.com\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/easydmarc.com\\\/blog\\\/top-8-most-common-types-of-dns-records\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/easydmarc.com\\\/blog\\\/wp-content\\\/uploads\\\/2022\\\/06\\\/DNS-Records-Hero.png\",\"keywords\":[\"DNS\",\"Platform\"],\"articleSection\":[\"DNS Records\",\"Knowledge Base\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/easydmarc.com\\\/blog\\\/top-8-most-common-types-of-dns-records\\\/#respond\"]}]},{\"@type\":[\"WebPage\",\"FAQPage\"],\"@id\":\"https:\\\/\\\/easydmarc.com\\\/blog\\\/top-8-most-common-types-of-dns-records\\\/\",\"url\":\"https:\\\/\\\/easydmarc.com\\\/blog\\\/top-8-most-common-types-of-dns-records\\\/\",\"name\":\"Top 8 Most Common Types of DNS Records | EasyDMARC\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/easydmarc.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/easydmarc.com\\\/blog\\\/top-8-most-common-types-of-dns-records\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/easydmarc.com\\\/blog\\\/top-8-most-common-types-of-dns-records\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/easydmarc.com\\\/blog\\\/wp-content\\\/uploads\\\/2022\\\/06\\\/DNS-Records-Hero.png\",\"datePublished\":\"2022-06-15T10:54:01+00:00\",\"dateModified\":\"2026-11-05T12:22:24+00:00\",\"description\":\"Learn the 8 most common DNS record types, including A, AAAA, CNAME, MX, TXT, and more, with simple explanations and examples.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/easydmarc.com\\\/blog\\\/top-8-most-common-types-of-dns-records\\\/#breadcrumb\"},\"mainEntity\":[{\"@id\":\"https:\\\/\\\/easydmarc.com\\\/blog\\\/top-8-most-common-types-of-dns-records\\\/#faq-question-1793363826621\"},{\"@id\":\"https:\\\/\\\/easydmarc.com\\\/blog\\\/top-8-most-common-types-of-dns-records\\\/#faq-question-1793363837934\"},{\"@id\":\"https:\\\/\\\/easydmarc.com\\\/blog\\\/top-8-most-common-types-of-dns-records\\\/#faq-question-1793363838600\"},{\"@id\":\"https:\\\/\\\/easydmarc.com\\\/blog\\\/top-8-most-common-types-of-dns-records\\\/#faq-question-1793363840184\"},{\"@id\":\"https:\\\/\\\/easydmarc.com\\\/blog\\\/top-8-most-common-types-of-dns-records\\\/#faq-question-1793363841467\"}],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/easydmarc.com\\\/blog\\\/top-8-most-common-types-of-dns-records\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/easydmarc.com\\\/blog\\\/top-8-most-common-types-of-dns-records\\\/#primaryimage\",\"url\":\"https:\\\/\\\/easydmarc.com\\\/blog\\\/wp-content\\\/uploads\\\/2022\\\/06\\\/DNS-Records-Hero.png\",\"contentUrl\":\"https:\\\/\\\/easydmarc.com\\\/blog\\\/wp-content\\\/uploads\\\/2022\\\/06\\\/DNS-Records-Hero.png\",\"width\":1440,\"height\":910,\"caption\":\"Top most common types of DNS Records\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/easydmarc.com\\\/blog\\\/top-8-most-common-types-of-dns-records\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Startseite\",\"item\":\"https:\\\/\\\/easydmarc.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Knowledge Base\",\"item\":\"https:\\\/\\\/easydmarc.com\\\/blog\\\/category\\\/knowledge-base\\\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"DNS Records\",\"item\":\"https:\\\/\\\/easydmarc.com\\\/blog\\\/category\\\/knowledge-base\\\/dns-records\\\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Top 8 Most Common DNS Records Types\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/easydmarc.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/easydmarc.com\\\/blog\\\/\",\"name\":\"EasyDMARC\",\"description\":\"Blog\",\"publisher\":{\"@id\":\"https:\\\/\\\/easydmarc.com\\\/blog\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/easydmarc.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/easydmarc.com\\\/blog\\\/#organization\",\"name\":\"EasyDMARC\",\"url\":\"https:\\\/\\\/easydmarc.com\\\/blog\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/easydmarc.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/easydmarc.com\\\/blog\\\/wp-content\\\/uploads\\\/2021\\\/09\\\/cropped-android-chrome-512x512-1.png\",\"contentUrl\":\"https:\\\/\\\/easydmarc.com\\\/blog\\\/wp-content\\\/uploads\\\/2021\\\/09\\\/cropped-android-chrome-512x512-1.png\",\"width\":512,\"height\":512,\"caption\":\"EasyDMARC\"},\"image\":{\"@id\":\"https:\\\/\\\/easydmarc.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.facebook.com\\\/EasyDMARC\\\/\",\"https:\\\/\\\/x.com\\\/easydmarc\",\"https:\\\/\\\/www.linkedin.com\\\/company\\\/easydmarc\\\/mycompany\\\/\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/easydmarc.com\\\/blog\\\/#\\\/schema\\\/person\\\/740e38b8d7f98e6c4141ae2931ca5a2a\",\"name\":\"Hagop K.\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/bb6e65e2ae3c6e57f798515a978995b899d1d972034c909397efad978249be85?s=96&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/bb6e65e2ae3c6e57f798515a978995b899d1d972034c909397efad978249be85?s=96&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/bb6e65e2ae3c6e57f798515a978995b899d1d972034c909397efad978249be85?s=96&r=g\",\"caption\":\"Hagop K.\"},\"sameAs\":[\"https:\\\/\\\/www.linkedin.com\\\/in\\\/hagopkhatchoian\\\/\"],\"url\":\"https:\\\/\\\/easydmarc.com\\\/blog\\\/author\\\/hagop-khatchoian\\\/\"},{\"@type\":\"Question\",\"@id\":\"https:\\\/\\\/easydmarc.com\\\/blog\\\/top-8-most-common-types-of-dns-records\\\/#faq-question-1793363826621\",\"position\":1,\"url\":\"https:\\\/\\\/easydmarc.com\\\/blog\\\/top-8-most-common-types-of-dns-records\\\/#faq-question-1793363826621\",\"name\":\"What are the common DNS record types?\",\"answerCount\":1,\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"The eight most common are A, AAAA, CNAME, NS, SOA, MX, TXT, and PTR. A and AAAA map a domain to IPv4 and IPv6 addresses, CNAME creates an alias to another hostname, NS delegates authority to name servers, SOA holds the zone's administrative settings, MX routes incoming email, TXT stores verification and authentication data including SPF, DKIM, and DMARC, and PTR maps an IP address back to a hostname.\",\"inLanguage\":\"en-US\"},\"inLanguage\":\"en-US\"},{\"@type\":\"Question\",\"@id\":\"https:\\\/\\\/easydmarc.com\\\/blog\\\/top-8-most-common-types-of-dns-records\\\/#faq-question-1793363837934\",\"position\":2,\"url\":\"https:\\\/\\\/easydmarc.com\\\/blog\\\/top-8-most-common-types-of-dns-records\\\/#faq-question-1793363837934\",\"name\":\"Which DNS records are required for email?\",\"answerCount\":1,\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"MX records are required to receive email. For sending, SPF and DKIM are published as TXT records and DMARC as a TXT record at _dmarc, and major mailbox providers now require all three from bulk senders. PTR records are managed by whoever controls the sending IP address and are checked by receiving servers at connection time.\",\"inLanguage\":\"en-US\"},\"inLanguage\":\"en-US\"},{\"@type\":\"Question\",\"@id\":\"https:\\\/\\\/easydmarc.com\\\/blog\\\/top-8-most-common-types-of-dns-records\\\/#faq-question-1793363838600\",\"position\":3,\"url\":\"https:\\\/\\\/easydmarc.com\\\/blog\\\/top-8-most-common-types-of-dns-records\\\/#faq-question-1793363838600\",\"name\":\"What's the difference between an A record and a CNAME?\",\"answerCount\":1,\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"An A record points a hostname directly to an IPv4 address. A CNAME points a hostname to another hostname, which is then resolved to an address in a second lookup. A records can be published at the domain apex; CNAME records cannot, because the apex has to hold SOA and NS records at the same name.\",\"inLanguage\":\"en-US\"},\"inLanguage\":\"en-US\"},{\"@type\":\"Question\",\"@id\":\"https:\\\/\\\/easydmarc.com\\\/blog\\\/top-8-most-common-types-of-dns-records\\\/#faq-question-1793363840184\",\"position\":4,\"url\":\"https:\\\/\\\/easydmarc.com\\\/blog\\\/top-8-most-common-types-of-dns-records\\\/#faq-question-1793363840184\",\"name\":\"Can a domain have more than one A record or MX record?\",\"answerCount\":1,\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Yes. Multiple A records on the same hostname return several IPv4 addresses and are used for redundancy and load distribution. Multiple MX records are standard, with priority values setting the order in which sending servers try them. SPF is the exception: only one SPF TXT record may be published per host.\",\"inLanguage\":\"en-US\"},\"inLanguage\":\"en-US\"},{\"@type\":\"Question\",\"@id\":\"https:\\\/\\\/easydmarc.com\\\/blog\\\/top-8-most-common-types-of-dns-records\\\/#faq-question-1793363841467\",\"position\":5,\"url\":\"https:\\\/\\\/easydmarc.com\\\/blog\\\/top-8-most-common-types-of-dns-records\\\/#faq-question-1793363841467\",\"name\":\"How long do DNS changes take to propagate?\",\"answerCount\":1,\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Authoritative name servers publish a change immediately. How long it takes to be visible everywhere depends on the TTL set on the previous version of the record, because resolvers keep serving the cached value until it expires. A record with a TTL of 3600 can take up to an hour to clear everywhere. Nameserver changes made at the registrar take longer, commonly 24 to 48 hours.\",\"inLanguage\":\"en-US\"},\"inLanguage\":\"en-US\"}]}<\/script>\n<meta property=\"og:video\" content=\"https:\/\/www.youtube.com\/embed\/62qVTVeCupk\" \/>\n<meta property=\"og:video:type\" content=\"text\/html\" \/>\n<meta property=\"og:video:duration\" content=\"141\" \/>\n<meta property=\"og:video:width\" content=\"480\" \/>\n<meta property=\"og:video:height\" content=\"270\" \/>\n<meta property=\"ya:ovs:adult\" content=\"false\" \/>\n<meta property=\"ya:ovs:upload_date\" content=\"2022-06-15T10:54:01+00:00\" \/>\n<meta property=\"ya:ovs:allow_embed\" content=\"true\" \/>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Top 8 Most Common Types of DNS Records | EasyDMARC","description":"Learn the 8 most common DNS record types, including A, AAAA, CNAME, MX, TXT, and more, with simple explanations and examples.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/easydmarc.com\/blog\/top-8-most-common-types-of-dns-records\/","og_locale":"en_US","og_type":"article","og_title":"Top 8 Most Common DNS Records Types","og_description":"Learn the 8 most common DNS record types, including A, AAAA, CNAME, MX, TXT, and more, with simple explanations and examples.","og_url":"https:\/\/easydmarc.com\/blog\/top-8-most-common-types-of-dns-records\/","og_site_name":"EasyDMARC","article_publisher":"https:\/\/www.facebook.com\/EasyDMARC\/","article_published_time":"2022-06-15T10:54:01+00:00","article_modified_time":"2026-11-05T12:22:24+00:00","og_image":[{"width":1440,"height":910,"url":"https:\/\/easydmarc.com\/blog\/wp-content\/uploads\/2022\/06\/DNS-Records-Hero.png","type":"image\/png"}],"author":"Hagop K.","twitter_card":"summary_large_image","twitter_creator":"@easydmarc","twitter_site":"@easydmarc","twitter_misc":{"Written by":"Hagop K.","Est. reading time":"23 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/easydmarc.com\/blog\/top-8-most-common-types-of-dns-records\/#article","isPartOf":{"@id":"https:\/\/easydmarc.com\/blog\/top-8-most-common-types-of-dns-records\/"},"author":{"name":"Hagop K.","@id":"https:\/\/easydmarc.com\/blog\/#\/schema\/person\/740e38b8d7f98e6c4141ae2931ca5a2a"},"headline":"Top 8 Most Common DNS Records Types","datePublished":"2022-06-15T10:54:01+00:00","dateModified":"2026-11-05T12:22:24+00:00","mainEntityOfPage":{"@id":"https:\/\/easydmarc.com\/blog\/top-8-most-common-types-of-dns-records\/"},"wordCount":5110,"commentCount":0,"publisher":{"@id":"https:\/\/easydmarc.com\/blog\/#organization"},"image":{"@id":"https:\/\/easydmarc.com\/blog\/top-8-most-common-types-of-dns-records\/#primaryimage"},"thumbnailUrl":"https:\/\/easydmarc.com\/blog\/wp-content\/uploads\/2022\/06\/DNS-Records-Hero.png","keywords":["DNS","Platform"],"articleSection":["DNS Records","Knowledge Base"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/easydmarc.com\/blog\/top-8-most-common-types-of-dns-records\/#respond"]}]},{"@type":["WebPage","FAQPage"],"@id":"https:\/\/easydmarc.com\/blog\/top-8-most-common-types-of-dns-records\/","url":"https:\/\/easydmarc.com\/blog\/top-8-most-common-types-of-dns-records\/","name":"Top 8 Most Common Types of DNS Records | EasyDMARC","isPartOf":{"@id":"https:\/\/easydmarc.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/easydmarc.com\/blog\/top-8-most-common-types-of-dns-records\/#primaryimage"},"image":{"@id":"https:\/\/easydmarc.com\/blog\/top-8-most-common-types-of-dns-records\/#primaryimage"},"thumbnailUrl":"https:\/\/easydmarc.com\/blog\/wp-content\/uploads\/2022\/06\/DNS-Records-Hero.png","datePublished":"2022-06-15T10:54:01+00:00","dateModified":"2026-11-05T12:22:24+00:00","description":"Learn the 8 most common DNS record types, including A, AAAA, CNAME, MX, TXT, and more, with simple explanations and examples.","breadcrumb":{"@id":"https:\/\/easydmarc.com\/blog\/top-8-most-common-types-of-dns-records\/#breadcrumb"},"mainEntity":[{"@id":"https:\/\/easydmarc.com\/blog\/top-8-most-common-types-of-dns-records\/#faq-question-1793363826621"},{"@id":"https:\/\/easydmarc.com\/blog\/top-8-most-common-types-of-dns-records\/#faq-question-1793363837934"},{"@id":"https:\/\/easydmarc.com\/blog\/top-8-most-common-types-of-dns-records\/#faq-question-1793363838600"},{"@id":"https:\/\/easydmarc.com\/blog\/top-8-most-common-types-of-dns-records\/#faq-question-1793363840184"},{"@id":"https:\/\/easydmarc.com\/blog\/top-8-most-common-types-of-dns-records\/#faq-question-1793363841467"}],"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/easydmarc.com\/blog\/top-8-most-common-types-of-dns-records\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/easydmarc.com\/blog\/top-8-most-common-types-of-dns-records\/#primaryimage","url":"https:\/\/easydmarc.com\/blog\/wp-content\/uploads\/2022\/06\/DNS-Records-Hero.png","contentUrl":"https:\/\/easydmarc.com\/blog\/wp-content\/uploads\/2022\/06\/DNS-Records-Hero.png","width":1440,"height":910,"caption":"Top most common types of DNS Records"},{"@type":"BreadcrumbList","@id":"https:\/\/easydmarc.com\/blog\/top-8-most-common-types-of-dns-records\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Startseite","item":"https:\/\/easydmarc.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Knowledge Base","item":"https:\/\/easydmarc.com\/blog\/category\/knowledge-base\/"},{"@type":"ListItem","position":3,"name":"DNS Records","item":"https:\/\/easydmarc.com\/blog\/category\/knowledge-base\/dns-records\/"},{"@type":"ListItem","position":4,"name":"Top 8 Most Common DNS Records Types"}]},{"@type":"WebSite","@id":"https:\/\/easydmarc.com\/blog\/#website","url":"https:\/\/easydmarc.com\/blog\/","name":"EasyDMARC","description":"Blog","publisher":{"@id":"https:\/\/easydmarc.com\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/easydmarc.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/easydmarc.com\/blog\/#organization","name":"EasyDMARC","url":"https:\/\/easydmarc.com\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/easydmarc.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/easydmarc.com\/blog\/wp-content\/uploads\/2021\/09\/cropped-android-chrome-512x512-1.png","contentUrl":"https:\/\/easydmarc.com\/blog\/wp-content\/uploads\/2021\/09\/cropped-android-chrome-512x512-1.png","width":512,"height":512,"caption":"EasyDMARC"},"image":{"@id":"https:\/\/easydmarc.com\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/EasyDMARC\/","https:\/\/x.com\/easydmarc","https:\/\/www.linkedin.com\/company\/easydmarc\/mycompany\/"]},{"@type":"Person","@id":"https:\/\/easydmarc.com\/blog\/#\/schema\/person\/740e38b8d7f98e6c4141ae2931ca5a2a","name":"Hagop K.","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/bb6e65e2ae3c6e57f798515a978995b899d1d972034c909397efad978249be85?s=96&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/bb6e65e2ae3c6e57f798515a978995b899d1d972034c909397efad978249be85?s=96&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/bb6e65e2ae3c6e57f798515a978995b899d1d972034c909397efad978249be85?s=96&r=g","caption":"Hagop K."},"sameAs":["https:\/\/www.linkedin.com\/in\/hagopkhatchoian\/"],"url":"https:\/\/easydmarc.com\/blog\/author\/hagop-khatchoian\/"},{"@type":"Question","@id":"https:\/\/easydmarc.com\/blog\/top-8-most-common-types-of-dns-records\/#faq-question-1793363826621","position":1,"url":"https:\/\/easydmarc.com\/blog\/top-8-most-common-types-of-dns-records\/#faq-question-1793363826621","name":"What are the common DNS record types?","answerCount":1,"acceptedAnswer":{"@type":"Answer","text":"The eight most common are A, AAAA, CNAME, NS, SOA, MX, TXT, and PTR. A and AAAA map a domain to IPv4 and IPv6 addresses, CNAME creates an alias to another hostname, NS delegates authority to name servers, SOA holds the zone's administrative settings, MX routes incoming email, TXT stores verification and authentication data including SPF, DKIM, and DMARC, and PTR maps an IP address back to a hostname.","inLanguage":"en-US"},"inLanguage":"en-US"},{"@type":"Question","@id":"https:\/\/easydmarc.com\/blog\/top-8-most-common-types-of-dns-records\/#faq-question-1793363837934","position":2,"url":"https:\/\/easydmarc.com\/blog\/top-8-most-common-types-of-dns-records\/#faq-question-1793363837934","name":"Which DNS records are required for email?","answerCount":1,"acceptedAnswer":{"@type":"Answer","text":"MX records are required to receive email. For sending, SPF and DKIM are published as TXT records and DMARC as a TXT record at _dmarc, and major mailbox providers now require all three from bulk senders. PTR records are managed by whoever controls the sending IP address and are checked by receiving servers at connection time.","inLanguage":"en-US"},"inLanguage":"en-US"},{"@type":"Question","@id":"https:\/\/easydmarc.com\/blog\/top-8-most-common-types-of-dns-records\/#faq-question-1793363838600","position":3,"url":"https:\/\/easydmarc.com\/blog\/top-8-most-common-types-of-dns-records\/#faq-question-1793363838600","name":"What's the difference between an A record and a CNAME?","answerCount":1,"acceptedAnswer":{"@type":"Answer","text":"An A record points a hostname directly to an IPv4 address. A CNAME points a hostname to another hostname, which is then resolved to an address in a second lookup. A records can be published at the domain apex; CNAME records cannot, because the apex has to hold SOA and NS records at the same name.","inLanguage":"en-US"},"inLanguage":"en-US"},{"@type":"Question","@id":"https:\/\/easydmarc.com\/blog\/top-8-most-common-types-of-dns-records\/#faq-question-1793363840184","position":4,"url":"https:\/\/easydmarc.com\/blog\/top-8-most-common-types-of-dns-records\/#faq-question-1793363840184","name":"Can a domain have more than one A record or MX record?","answerCount":1,"acceptedAnswer":{"@type":"Answer","text":"Yes. Multiple A records on the same hostname return several IPv4 addresses and are used for redundancy and load distribution. Multiple MX records are standard, with priority values setting the order in which sending servers try them. SPF is the exception: only one SPF TXT record may be published per host.","inLanguage":"en-US"},"inLanguage":"en-US"},{"@type":"Question","@id":"https:\/\/easydmarc.com\/blog\/top-8-most-common-types-of-dns-records\/#faq-question-1793363841467","position":5,"url":"https:\/\/easydmarc.com\/blog\/top-8-most-common-types-of-dns-records\/#faq-question-1793363841467","name":"How long do DNS changes take to propagate?","answerCount":1,"acceptedAnswer":{"@type":"Answer","text":"Authoritative name servers publish a change immediately. How long it takes to be visible everywhere depends on the TTL set on the previous version of the record, because resolvers keep serving the cached value until it expires. A record with a TTL of 3600 can take up to an hour to clear everywhere. Nameserver changes made at the registrar take longer, commonly 24 to 48 hours.","inLanguage":"en-US"},"inLanguage":"en-US"}]},"og_video":"https:\/\/www.youtube.com\/embed\/62qVTVeCupk","og_video_type":"text\/html","og_video_duration":"141","og_video_width":"480","og_video_height":"270","ya_ovs_adult":"false","ya_ovs_upload_date":"2022-06-15T10:54:01+00:00","ya_ovs_allow_embed":"true"},"jetpack_featured_media_url":"https:\/\/easydmarc.com\/blog\/wp-content\/uploads\/2022\/06\/DNS-Records-Hero.png","_links":{"self":[{"href":"https:\/\/easydmarc.com\/blog\/wp-json\/wp\/v2\/posts\/28211","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/easydmarc.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/easydmarc.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/easydmarc.com\/blog\/wp-json\/wp\/v2\/users\/25"}],"replies":[{"embeddable":true,"href":"https:\/\/easydmarc.com\/blog\/wp-json\/wp\/v2\/comments?post=28211"}],"version-history":[{"count":19,"href":"https:\/\/easydmarc.com\/blog\/wp-json\/wp\/v2\/posts\/28211\/revisions"}],"predecessor-version":[{"id":64399,"href":"https:\/\/easydmarc.com\/blog\/wp-json\/wp\/v2\/posts\/28211\/revisions\/64399"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/easydmarc.com\/blog\/wp-json\/wp\/v2\/media\/64207"}],"wp:attachment":[{"href":"https:\/\/easydmarc.com\/blog\/wp-json\/wp\/v2\/media?parent=28211"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/easydmarc.com\/blog\/wp-json\/wp\/v2\/categories?post=28211"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/easydmarc.com\/blog\/wp-json\/wp\/v2\/tags?post=28211"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}