Common DNS Records
Table of Contents
The Domain Name System (DNS) is composed of many different record types (or resource records):
CAA, etc. Some record types are common. Others are less relevant, deprecated, or replaced.
DNSimple supports common and traditional record types, and some newer types introduced to provide innovative services. In this article, we’ll look at the most common record types, and explore the most common DNS records you need for your domains to work.
Common record types
These are the most common DNS record types:
||This is the most popular type. A records create a DNS record that points to an IPv4 address. It allows you to use memonic names, such as
||This record works as an alias and maps one name to another. It’s often used to reduce duplication in domain name configurations, or to simplify the maintenance of multiple records connected to the same IP address. Its use has increased in the last few years, since it’s one of the common mechanisms that’s been adopted by cloud services to provision customer-specific services.|
||This record is used to identify the servers mail should be delivered to for a domain. You need to have these records configured to receive emails.|
||This record allows domain administrators to insert any text content into DNS records. These records are used for various purposes. One example is ownership validation: To prove you own the domain, a provider may require you to add a TXT record with a particular value to your domain.|
||This record is used to delegate a subzone to a set of name servers. It’s common, because these are the types of records you need to modify when you want to delegate a domain to a DNS provider.|
||This record stores important information about the DNS zone (your domain). It’s common, because each zone must have an SOA record. However, it’s unlikely you’ll have to create a SOA record directly. For instance, DNSimple automatically manages the SOA records for all your domains.|
Common DNS records
Although each domain is unique, and will likely have a special DNS configuration, there’s a basic set of DNS records that’s common among the majority of domains.
If you just purchased a domain, or are reviewing your domain’s DNS configuration, compare the DNS records in your domain with the following to determine whether or not anything’s missing:
This article assumes
example.com is your domain name.
1. Root domain (
Each domain needs to have a record for the root domain. Otherwise your domain won’t resolve, and accessing the URL in the browser will return a resolution error.
In most cases, this configuration is an A record pointing to the IP where your site is hosted. However, it can also be an ALIAS if your site is hosted elsewhere (this is common when you want to point your root domain to a cloud service, such as Heroku, Netlify, GitHub, etc.), or a URL record if this domain needs to redirect elsewhere.
dig example.comto check the presence of a root record.
The answer should return at least one A record as below:
dig dnsimple.com ;; ANSWER SECTION: dnsimple.com. 59 IN A 220.127.116.11
Both ALIAS and URL records are synthetized as A records.
If you see a CNAME record, your configuration is invalid. The CNAME can’t be used for the root domain.
2. www subdomain: (
It’s common to have the
www subdomain configured in addition to the root domain. There are several possibilities:
- Using an A record to point to the same IP of the root domain.
- Using a CNAME record to point to the root domain.
- Using a URL record to redirect to the root domain.
Using an ALIAS record for the
www subdomain is not incorrect, however it’s generally unnecessary. In most cases, you can replace the ALIAS with the CNAME.
dig www.example.comto check the presence of a www record.
The answer should return at least one A record or exactly one CNAME record as below:
dig www.dnsimple.com ;; ANSWER SECTION: www.dnsimple.com. 59 IN A 18.104.22.168
dig www.dnsimple.com ;; ANSWER SECTION: www.dnsimple.com. 3599 IN CNAME dnsimple.com. dnsimple.com. 59 IN A 22.214.171.124
3. MX email records
If you want to receive emails for your domain, you need to have at least one MX record pointing to your doamin mail server. For rendudancy, there are generally two or more MX records, each with a different content and priority.
dig MX example.comto check the presence of MX records on the root domain.
The answer should return at least one MX record as below:
dig MX www.dnsimple.com ;; ANSWER SECTION: dnsimple.com. 3599 IN MX 1 aspmx.l.google.com. dnsimple.com. 3599 IN MX 5 alt1.aspmx.l.google.com. dnsimple.com. 3599 IN MX 5 alt2.aspmx.l.google.com. dnsimple.com. 3599 IN MX 10 alt3.aspmx.l.google.com. dnsimple.com. 3599 IN MX 10 alt4.aspmx.l.google.com.
4. CAA record
It’s advisable to add a CAA record to the root domain to specify which certificate authorities can issue a certificate for your domain.
dig CAA example.comto check for the presence of a CAA record on the root domain.
The answer should return at least one CAA record as below:
dig CAA www.dnsimple.com ;; ANSWER SECTION: dnsimple.com. 3599 IN CAA 0 iodef "mailto:email@example.com" dnsimple.com. 3599 IN CAA 0 issue "amazonaws.com" dnsimple.com. 3599 IN CAA 0 issue "comodoca.com" dnsimple.com. 3599 IN CAA 0 issue "letsencrypt.org" dnsimple.com. 3599 IN CAA 0 issuewild "comodoca.com"