{"id":1787,"date":"2015-12-23T05:58:14","date_gmt":"2015-12-23T05:58:14","guid":{"rendered":"http:\/\/microsoftgeek.com\/?p=1787"},"modified":"2015-12-23T05:59:39","modified_gmt":"2015-12-23T05:59:39","slug":"dns-records","status":"publish","type":"post","link":"https:\/\/microsoftgeek.com\/?p=1787","title":{"rendered":"DNS Records"},"content":{"rendered":"

A Record<\/strong><\/h2>\n
<\/div>\n
The majority of DNS records are \u201cA\u201d records. A records allow for you to point different sections of your domain to different IP addresses or servers. For example, this would be useful for having \u201cwww.domain.com\u201d point to your web server\u2019s IP address and \u201cmail.domain.com\u201d point to your mail server\u2019s IP address. Each record includes a \u201cHost Name\u201d value and a corresponding IP Address. Record field: The record name for that A record. The host name will precede the \u201c.domain.com\u201d. For example, adding a host name of \u201cwww\u201d would translate to \u201cwww.domain.com\u201d. The \u201cwww\u201d would point to the specified IP address in the A record. Address field: The IP address you wish for the A record to point to. For example, an A record name of \u201cwww\u201d could point to \u201c198.64.251.10\u2033, while an A record name of \u201cmail\u201d could point to \u201c198.64.251.11\u2033. Examples\u00a0A records: www, mail, ftp, webmail, www2, secure, store, dev<\/div>\n
<\/div>\n

CNAME Re<\/strong>cord<\/strong><\/h2>\n
<\/div>\n
CNAME records point to domain names, as opposed to specific IP addresses. This is very useful in that you can point a CNAME record to a domain name, change the record value for that domain name, and the CNAME record will reflect the updated record value. This is most commonly used when dealing with several top level domain versions (.com, .net, .org, etc.) of the same domain name. For example, if you own \u201cdomain.com\u201d and \u201cdomain.net\u201d, instead of having to keep both domain name\u2019s records in sync with each other so that they resolve to the same IP address, you can simply create CNAME records for \u201cdomain.net\u201d to mimic the \u201cdomain.com\u201d records. That way, when changing records for \u201cdomain.com\u201d, it will automatically be reflected on \u201cdomain.net\u201d as well. Record field: The host name for that CNAME record. The host name will precede the \u201c.domain.com\u201d. For example, adding a CNAME record name of \u201cwww\u201d would translate to \u201cwww.domain.com\u201d. The \u201cwww\u201d would point to the same IP address of the domain name value entered for the CNAME record. Address field: The domain name you wish for the CNAME record to mimic. For example, a CNAME record of \u201cwww\u201d could point to \u201cdev.anotherdomain.com\u201d. This allows \u201cwww.domain.com\u201d to always point to \u201cdev.anotherdomain.com\u201d even when the IP address is changed or updated. Example CNAME record: Record: webmail Address: mail.hostedmail.com<\/div>\n
<\/div>\n

MX Record<\/strong><\/h2>\n
<\/div>\n
An important part of the email delivery system is \u201cMX\u201d records. MX records essentially tell the world what server to send mail to for a particular domain name. Priority field: The priority preference for that MX record. MX records are processed in order starting with the one with the lowest priority value and working towards high priority records. In situations where you have multiple email servers, or backup email servers, set a lower priority value for your primary mail server and a higher priority value for your backup server. Record field: You can specify a 3rd level mail domain here, but typically you will want to leave it as \u201c@\u201d to specify the record is for the root domain name. Address field: The address of the target mail server. It is recommended to use a domain name value here as opposed to an IP address. Typically you would first create an \u201cA\u201d record of \u201cmail\u201d pointing to the IP address of your mail server, and specify \u201cmail.domain.com\u201d here as the address entry for the MX record. Example MX records: Priority: 10 Record: @ Address: mail.domain.com Priority: 20 Record: @ Address: mail2.domain.com<\/div>\n
<\/div>\n

TXT Record<\/strong><\/h2>\n
<\/div>\n
Typically a TXT record is used to get information about a domain. They can be used to specify what email servers are allowed to send mail for your domain with what is known as a \u201cSender Policy Framework (SPF)\u201d record \u2013 which is very useful in combating spammers from falsely marking spam emails as from your domain name. They can also be used to provide a public \u201cDomainKey\u201d to be used to further prove the identity of emails being sent from your mail server to prove to spam filters that your domain\u2019s email is legitimate email. Record field: The name of the TXT record. For example, to create an SPF record you would want to leave it as \u201c@\u201d to specify the record is for the root domain name. DomainKeys require a more detailed record name. Address field: This is the value of the TXT record. Example TXT records: Record: @ Address: v=spf1 a mx -all Record: dkDomain._domainKey Address: p=MHwwDQYJKoZIhvcNAQEBBQADawAwaAJhANZYB0<\/div>\n","protected":false},"excerpt":{"rendered":"

A Record The majority of DNS records are \u201cA\u201d records. A records allow for you to point different sections of your domain to different IP addresses or servers. For example, this would be useful for having \u201cwww.domain.com\u201d point to your web server\u2019s IP address and \u201cmail.domain.com\u201d point to your mail server\u2019s IP address. Each record […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[45],"tags":[],"class_list":["post-1787","post","type-post","status-publish","format-standard","hentry","category-domain-name-system-dns"],"_links":{"self":[{"href":"https:\/\/microsoftgeek.com\/index.php?rest_route=\/wp\/v2\/posts\/1787","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/microsoftgeek.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/microsoftgeek.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/microsoftgeek.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/microsoftgeek.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1787"}],"version-history":[{"count":2,"href":"https:\/\/microsoftgeek.com\/index.php?rest_route=\/wp\/v2\/posts\/1787\/revisions"}],"predecessor-version":[{"id":1789,"href":"https:\/\/microsoftgeek.com\/index.php?rest_route=\/wp\/v2\/posts\/1787\/revisions\/1789"}],"wp:attachment":[{"href":"https:\/\/microsoftgeek.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1787"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/microsoftgeek.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1787"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/microsoftgeek.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1787"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}