The Domain Name System (DNS) is the Internet's address book. DNS directs web traffic to your server and emails to your inbox by mapping memorable domain names like example.com to IP addresses like
0123:4567:89ab:cdef:0123:4567:89ab:cdef. This guide introduces basic DNS concepts and the different types of DNS records.
Before adding any DNS records, you should learn the basics of DNS. You'll start by dissecting a domain name, and then you'll learn about the mechanics of DNS resolution, including name servers, zone files, and individual DNS records.
Domain names are best understood by reading from right to left. The broadest domain classification is on the right, and become more specific as you move to the left. In the examples below, the top-level domain, or TLD, is .com.
Every term to the left of the TLD and separated by a period is considered a more specific subdomain, although conventionally, first-level subdomains plus their TLDs (example.com) are referred to as domains. Moving to the left, hello and mail are the second- and third-level subdomains, respectively. Typically, subdomains are used to uniquely identify specific machines or services, but this is left up to the domain owner.
Choosing and specifying name servers is an essential part of domain ownership. If you don't, the Internet won't know where to find your DNS information, and your domain won't resolve. Name servers host a domain's DNS information in a text file called the zone file. They're are also known as Servers of Authority (SOAs). You can host your DNS information on name servers in one of the several locations:
You'll specify name servers on your domain registrar's website. They'll take care of publishing that information to the higher-level name servers. You'll want to specify at least two name servers. That way, if one of them is down, the next one can continue to serve your DNS information.
The next aspect of DNS management is specifying DNS records, which actually match domain names to IP addresses. The DNS records are then automatically bundled up into a zone file, which is what allows the Internet to look up the correct IP address for your domain. A default zone file contains records similar to the following:
; cloudgeni.us.com  $TTL 86400 @ IN SOA ns1.cloudgeni.us. 2015062147 14400 14400 1209600 86400 @ NS ns1.cloudgeni.us. @ NS ns2.cloudgeni.us. @ NS ns3.cloudgeni.us. @ NS ns4.cloudgeni.us. @ NS ns5.cloudgeni.us. @ MX 10 mail.cloudgeni.us. @ A 126.96.36.199 mail A 188.8.131.52 www A 184.108.40.206
Every domain's zone file contains the admin's email address, the name servers, and the DNS records. Of course, you are not limited to these default entries. You can create a variety of DNS records for as many different subdomains as you wish. To learn how to add individual DNS records using the DNS Manager, read this article.
So how does DNS actually work? First, the domain name needs to get translated into your server IP address. DNS matches human-friendly domain names like example.com to computer-friendly IP addresses like 220.127.116.11. This happens in a special text file called a zone file, which lists domains and their corresponding IP addresses (and a few other things). A zone file is a lot like a phone book that matches names with street addresses.
Here's how the DNS lookup process works:
The scenario described above is what happens if the ISP has no current information about the requested domain. In actuality, ISPs cache a lot of DNS information after they've looked it up the first time. This results in faster lookups and less strain on DNS servers. Usually caching is a good thing, but it can be a problem if you've recently made a change to your DNS information, like when you move from one provider to another. In those cases, you'll want to pay attention to your zone file's time to live (TTL) so that your DNS change happens as quickly as possible.
An A record matches up a domain (or subdomain) to an IP address. In other words, it points your domain name to your server IP address, which allows web traffic to reach your server. This is the core functionality of DNS. A typical A record looks like the following:
example.com A 18.104.22.168
You can also make A records for subdomains you want to direct to your server:
hello.example.com A 22.214.171.124
You can point different subdomains to different IP addresses. If you want to point every subdomain of example.com to your server IP, you can use an asterisk (***) as your subdomain:
*.example.com A 126.96.36.199
An AAAA record is just like an A record, but for IPv6 IP addresses. A typical AAAA record looks like the following:
example.com AAAA 0123:4567:89ab:cdef:0123:4567:89ab:cdef
An AXFR record is a type of DNS record used for DNS replication, although there are also more modern ways to do DNS replication. AXFR records are not used in ordinary zone files. Rather, they are used on a slave DNS server to replicate the zone file from a master DNS server.
A CNAME record or Canonical Name record matches up a domain (or subdomain) to a different domain. With a CNAME record, DNS lookups use the target domain's DNS resolution as the alias's resolution. Here's an example:
alias.com CNAME example.com example.com A 188.8.131.52
With this setup, when alias.com is requested, the initial DNS lookup will find the CNAME entry with the target of example.com. A new DNS lookup will be started for example.com, which will find the IP address 184.108.40.206. Finally, visitors to alias.com will be directed to 220.127.116.11.
CNAME records exist so that domains can have aliases. You should not use a CNAME record for a domain that gets an email, because some mail servers handle mail oddly for domains with CNAME records. Likewise, MX records cannot reference CNAME-defined hostnames. Also, the target domain for a CNAME record should have a normal A-record resolution. Chaining or looping CNAME records is not recommended.
In some cases, a CNAME record can be an effective way to redirect traffic from one domain to another while keeping the same URL. However, keep in mind that a CNAME record does not function the same way as a URL redirect. A CNAME record directs web traffic for a particular domain to the target domain's IP address. Once the visitor reaches that IP address, the local Apache (or another web server) configuration will determine how the domain is handled. If that domain is not configured on the server, the server will simply display its default web page (if any). This may or may not be the web page for the target domain in the CNAME record, depending on how the server is configured.
A DKIM record or domain keys identified mail record displays the public key for authenticating messages that have been signed with the DKIM protocol. This practice increases the capability to check mail authenticity. A typical DKIM record looks like the following:
selector1._domainkey.example.com TXT k=rsa;p=J8eTBu224i086iK
DKIM records are implemented as text records. The record must be created for a subdomain, which has a unique selector for that key, then a period (.), and then
_domainkey.example.com. The type is TXT, and the value includes the type of key, followed by the actual key.
An MX record or mail exchange record sets the mail delivery destination for a domain (or subdomain). A typical MX record looks like the following:
example.com MX 10 mail.example.com mail.example.com A 18.104.22.168
The above records direct mail for
example.com to the
mail.example.com server. The target domain (mail.example.com above) needs to have its own A record that resolves to your server. Ideally, an MX record should point to a domain that is also the hostname for its server.
Your MX records don't necessarily have to point to your server. If you're using a third-party mail service, like Google Apps, you should use the MX records they provide.
Priority is another component of MX records. This is the number written between the record type and the target server (10 in the example above). Priority allows you to designate a fallback server (or servers) for mail for a particular domain. Lower numbers have a higher priority. Here's an example of a domain that has two fallback mail servers:
example.com MX 10 mail_1.example.com example.com MX 20 mail_2.example.com example.com MX 30 mail_3.example.com
In this example, if mail_1.example.com is down, mail will be delivered to mail_2.example.com. If mail_2.example.com is also down, mail will be delivered to mail_3.example.com.
NS records or name server records set the name servers for a domain (or subdomain). The primary name server records for your domain are set both at your registrar and in your zone file. Typical name server records (you need at least two) look like this:
example.com NS ns1.cloudgeni.us. example.com NS ns2.cloudgeni.us. example.com NS ns3.cloudgeni.us. example.com NS ns4.cloudgeni.us. example.com NS ns5.cloudgeni.us.
The name servers you designate at your registrar then carry the zone file for your domain.
You can also set up different name servers for any of your subdomains. Subdomain NS records get configured in your primary domain's zone file. For example, you could configure separate NS records in your zone file for the subdomain mail.example.com as shown below:
mail.example.com NS ns1.nameserver.com mail.example.com NS ns2.nameserver.com
Primary name servers get configured at your registrar; secondary subdomain name servers get configured in the primary domain's zone file. The order of NS records does not matter; DNS requests are sent randomly to the different servers, and if one host fails to respond, another one will be queried.
A PTR record or pointer record matches up an IP address to a domain (or subdomain), allowing reverse DNS queries to function. It performs the opposite service an A record does, in that it allows you to look up the domain associated with a particular IP address, instead of vice versa.
PTR records are usually set with your hosting provider. They are not part of your domain's zone file. This means that you'll always set reverse DNS for your server, even if your name servers are elsewhere. Likewise, if you have servers somewhere else but are using different name servers, you will still have to set up your PTR records with your hosting provider.
As a prerequisite for adding a PTR record, you need to create a valid, live A or AAAA record that points the desired domain to that IP. If you want an IPv4 PTR record, point the domain (or subdomain) to your server IPv4 address. If you want an IPv6 PTR record, point the domain to your server IPv6 address. Beyond that, IPv4 and IPv6 PTR records work the same way.
It is possible to have different IPs (including both IPv4 and IPv6 addresses) that have the same domain set for reverse DNS. To do this, you will have to configure multiple A or AAAA records for that domain that point to the various IPs.
An SOA record or Start of Authority record labels a zone file with the name of the host where it was originally created. Next, it lists the contact email address for the person responsible for the domain. There are also various numbers, which we'll get into in detail in a moment. First, here's a typical SOA record:
@ IN SOA ns1.cloudgeni.us. admin.example.com. 2013062147 14400 14400 1209600 86400
Here is what the numbers mean:
The single name server mentioned in the SOA record is considered the primary master for the purposes of Dynamic DNS and is the server where zone file changes get made before they are propagated to all other name servers.
An SPF record or Sender Policy Framework record lists the designated mail servers for a domain (or subdomain). It helps establish the legitimacy of your mail server and reduces the chances of spoofing, which occurs when someone fakes the headers on an email to make it look like it's coming from your domain, even though the message did not originate from your server. Spammers sometimes try to do this to get around spam filters. An SPF record for your domain tells other receiving mail servers which outgoing server(s) are valid sources of email, so they can reject spoofed email from your domain that has originated from unauthorized servers. A very basic SPF record looks like the following:
example.com TXT "v=spf1 a ~all"
In your SPF record, you should list all the mail servers from which you send mail and then exclude all the others. Your SPF record will have a domain or subdomain, type (which is TXT, or SPF if your name server supports it), and text (which starts with
v=spf1 and contains the SPF record settings).
If your server is the only mail server you use, you should be able to use the example record above. With this SPF record, the receiving server will check the IP addresses of both the sending server and the IP address of example.com. If the IPs match, the check passes. If not, the check will 'soft fail' (i.e., the message will be marked but will not automatically be rejected for failing the SPF check).
In addition to
~ there are two more flags
? to indicate domain policy
Make sure your SPF records are not too strict. If you accidentally exclude a legitimate mail server, its messages could get marked as spam. We strongly recommend visiting openspf.org to learn how SPF records work and how to construct one that works for your setup. Their examples are also helpful.
An SRV record or service record matches up a specific service that runs on your domain (or subdomain) to a target domain. This allows you to direct traffic to specific services, like instant messaging, to another server. A typical SRV record looks like the following:
_service._protocol.example.com SRV 10 0 5060 service.example.com
Here's a breakdown of the elements in an SRV record:
An example use of SRV records would be to set up Federated VoIP.
A TXT record or text record provides information about the domain in question to other resources on the Internet. It's a flexible type of DNS record that can serve many different purposes depending on the specific contents. One common use of the TXT record is to create an SPF record on nameservers that don't natively support SPF. Another use is to create a DKIM record for mail signing.
Cloud Genius® is a highly rated advanced technical education provider licensed by the State of Washington, USA.