Description: The CNAME record points a name to another name, instead of an IP.
Example: CNAME hr.ExampleDomain.com
Explanation: A subdomain is created (for example, recruiting) on the domain which points to an existing subdomain (for example, hr).
Analogy: John works for ExampleDomain.com as a recruiter and is part of the HR department. There is already an entry in the corporate directory for HR, however recruiting is not represented in the directory. John will need a CNAME record to be created on the domain called “recruiting” which will point to “hr”. Individuals contacting both “recruiting” and “hr” will be directed to the same resources.
Description: The A record points a name to a specific IP.
Example: exampledomain.com A 220.127.116.11
Explanation: An entry is created on the domain which points to a server via its IP address.
Analogy: John access www.exampledomain.com which is associated with the A record IP address.
Description: MX records stand for Mail Exchange. These records govern where mail is sent for a given domain.
Example: @ MX aspmx.l.google.com
Explanation: An MX record is created on the domain which points to the desired mail server.
Analogy: John decided to use G Suite for his company email services. He will need to replace his company domain MX records with MX records provided by Google.
Description: SPF records stand for Sender Policy Framework. These records declare what resources or servers can send email on behalf of the domain.
Example: @”v=spf3 include: spf.protection.outlook.com -all”
Explanation: An SPF record is type of Domain Name System (DNS) record that can help to prevent email address forgery. Spammers can falsify email headers so it looks like they’re sending from an email address at your domain.
Analogy: John decided to move his company email services to Microsoft Office 365. He will need to update his company domain SPF record to respect the standard SPF provided by Microsoft.
Description: A free-form field that can hold any text data, TXT rarely dictate flow of traffic however play an important role in providing domain name ownership validation and domain management validation.
Example: @ “MS=rXOxyZounnZasA10Z9oaD5c16JdjS11aKSWvsR3EbUSIQ”
Explanation: A TXT record is created on the domain which holds a value which is expected by a third-party. The presence of the record with the expected value assures the third-party that the customer owns the domain. The key provided is unique to the domain and provided by the third-party.
Analogy: MegaShippers (MS) has been hired to ship widgets to ExampleDomain.com customers. ExampleDomain.com is unsure as to when they expect to ship their first products. Both companies have agreed that shipping should start when ExampleDomain has placed a MegaShippers poster on the warehouse door. Everyday, a MegaShippers truck will drive by the ExampleDomain.com offices and check if the poster is on the door. If it is, the MegaShippers will be assured that they can start picking up packages for ExampleDomain.com from now on.