You need to recommend a solution to resolve the issue of email messages not being received on the Internet.
What should you include in the solution?
A. Modify the CNAME record.
B. Add an MX record.
C. Modify the TXT record.
D. Add a pointer (PTR) record.
Correct Answer: D
Explanation/Reference:
Detroit and New York users have direct connection to the internet but not Chicago users.
It appears that via a Send Connector Chicago email is sent to New York mail server.
Given this then the spf txt record listing the New York mail server is correct (131.107.1.200) and there should not be any issues with the Chicago email
Once the planned changes have been implemented then the DNS txt record would have to accommodate the Detroit Mail server (EX3) (131.107.2.200) in order for the email to function correctly for Detroit users.
However the question relates to Chicago users not Detroit users.
CNAME record
A Canonical Name or CNAME record is a type of DNS record that links an alias name to another canonical domain name.
You’ll need to configure CNAME records if you want to use URL forwarding to create a custom web address, forward a URL to Google Sites, or forward a naked domain URL, as well as verify your site with your domain name provider.
Lastly, you may need to use CNAME records to reset the administrator password if you can’t access the Google Apps control panel because you’ve forgotten the administrator password.
Your CNAME records are stored in the DNS Zone File as pairs of key values.
The value of a CNAME record is always a domain name. CNAME records are often used to create subdomains. CNAME records are useful because they allow you to set up an alias to a server without using its IP address, through an intermediary standard domain name.
MX Record
MX records are DNS settings associated with your domain that direct its mail to the servers hosting your users’ mail accounts.
These settings are managed by your domain host, not by Google. To make sure mail always gets delivered, you typically create records for multiple servers, all of which can deliver mail to users.
That way, if one server is down, mail can be routed to another server, instead. You determine which servers get tried first by assigning priorities, using values like
10, 20, 30, and so on. The lowest value gets highest priority.
PTR Record
A DNS PTR record – for those of you who are wondering – is a special entry in the Domain Name System
(DNS) that basically maps an IP address (like 65.55.12.249) to a domain name (like wwwco2vip.microsoft.com). Having a DNS PTR record for your IP address is (somewhat) a sign of reliability in the Internet, since only the owner of a specific network zone has the ability to create and edit these DNS records.
Today, most mail exchangers will check this record for each incoming connection and may abort the communication if they find your IP address does not have an associated DNS PTR entry: because of this reason, always suggest to make sure your public servers IP addresses have DNS PTR records configured properly.
While EmailVerify.NET can validate email addresses even without a DNS PTR entry configured, the quality of the validation results in this event may be suboptimal.
TXT Record
A TXT record is an entry within the Domain Name System (DNS) that provides supplemental information about your domain.
A TXT (text) record is used to hold some text information. You can put virtually any free text you want within a TXT record.
A TXT record has a hostname so that you can assign the free text to a particular hostname/zone.
The most common use for TXT records is to store SPF (sender policy framework) records and to prevent emails being faked to appear to have been sent from you.
The name field of the SPF record should be left blank unless mail is sent from a subdomain such as [email protected]. If this was the case “mail” would be entered in the name field of the record.
Alternatively, of email is sent from [email protected], the name field is left blank. The data field of the record is populated with the list of hosts that are permitted to send email for the domain in SPF record format.
There are wizards which can assist in generating an SPF record available. The data field of the record must be enclosed in quotations so servers will read the value as a single string. Below is a default SPF record for example-1.com.
NOT A
Today, most mail exchangers will check this record for each incoming connection and may abort the communication if they find your IP address does not have an associated DNS PTR entry:
Need a ptr record.
NOT B
Today, most mail exchangers will check this record for each incoming connection and may abort the communication if they find your IP address does not have an associated DNS PTR entry:
Need a ptr record.
NOT C
Need to modify the txt record for Detroit email users but not apparently for chicago email users.
DT oday, most mail exchangers will check this record for each incoming connection and may abort the communication if they find your IP address does not have an associated DNS PTR entry:
Need a ptr record.
Managing DNS Records
Explanation/Reference:
Detroit and New York users have direct connection to the internet but not Chicago users.
It appears that via a Send Connector Chicago email is sent to New York mail server.
Given this then the spf txt record listing the New York mail server is correct (131.107.1.200) and there should not be any issues with the Chicago email
Once the planned changes have been implemented then the DNS txt record would have to accommodate the Detroit Mail server (EX3) (131.107.2.200) in order for the email to function correctly for Detroit users.
However the question relates to Chicago users not Detroit users.
CNAME record
A Canonical Name or CNAME record is a type of DNS record that links an alias name to another canonical domain name.
You’ll need to configure CNAME records if you want to use URL forwarding to create a custom web address, forward a URL to Google Sites, or forward a naked domain URL, as well as verify your site with your domain name provider.
Lastly, you may need to use CNAME records to reset the administrator password if you can’t access the Google Apps control panel because you’ve forgotten the administrator password.
Your CNAME records are stored in the DNS Zone File as pairs of key values.
The value of a CNAME record is always a domain name. CNAME records are often used to create subdomains. CNAME records are useful because they allow you to set up an alias to a server without using its IP address, through an intermediary standard domain name.
MX Record
MX records are DNS settings associated with your domain that direct its mail to the servers hosting your users’ mail accounts.
These settings are managed by your domain host, not by Google. To make sure mail always gets delivered, you typically create records for multiple servers, all of which can deliver mail to users.
That way, if one server is down, mail can be routed to another server, instead. You determine which servers get tried first by assigning priorities, using values like
10, 20, 30, and so on. The lowest value gets highest priority.
PTR Record
A DNS PTR record – for those of you who are wondering – is a special entry in the Domain Name System
(DNS) that basically maps an IP address (like 65.55.12.249) to a domain name (like wwwco2vip.microsoft.com). Having a DNS PTR record for your IP address is (somewhat) a sign of reliability in the Internet, since only the owner of a specific network zone has the ability to create and edit these DNS records.
Today, most mail exchangers will check this record for each incoming connection and may abort the communication if they find your IP address does not have an associated DNS PTR entry: because of this reason, always suggest to make sure your public servers IP addresses have DNS PTR records configured properly.
While EmailVerify.NET can validate email addresses even without a DNS PTR entry configured, the quality of the validation results in this event may be suboptimal.
TXT Record
A TXT record is an entry within the Domain Name System (DNS) that provides supplemental information about your domain.
A TXT (text) record is used to hold some text information. You can put virtually any free text you want within a TXT record.
A TXT record has a hostname so that you can assign the free text to a particular hostname/zone.
The most common use for TXT records is to store SPF (sender policy framework) records and to prevent emails being faked to appear to have been sent from you.
The name field of the SPF record should be left blank unless mail is sent from a subdomain such as [email protected]. If this was the case “mail” would be entered in the name field of the record.
Alternatively, of email is sent from [email protected], the name field is left blank. The data field of the record is populated with the list of hosts that are permitted to send email for the domain in SPF record format.
There are wizards which can assist in generating an SPF record available. The data field of the record must be enclosed in quotations so servers will read the value as a single string. Below is a default SPF record for example-1.com.
NOT A
Today, most mail exchangers will check this record for each incoming connection and may abort the communication if they find your IP address does not have an associated DNS PTR entry:
Need a ptr record.
NOT B
Today, most mail exchangers will check this record for each incoming connection and may abort the communication if they find your IP address does not have an associated DNS PTR entry:
Need a ptr record.
NOT C
Need to modify the txt record for Detroit email users but not apparently for chicago email users.
DT oday, most mail exchangers will check this record for each incoming connection and may abort the communication if they find your IP address does not have an associated DNS PTR entry:
Need a ptr record.
Managing DNS Records
