An MX record must be added to your domain’s public DNS zone when you start setting up Internet mail delivery to your mail system. This record instructs all other mail servers on earth regarding where they should forward messages addressed to your domain. Check out NitroMail.io to know more
Few would tell you that the send connector server requires forward (A record) and reverse (PTR record) DNS entries. It’s possible (but not required) that this be the same server as the receive connector. Any server used as an Internet Send Connector must have a forward (A record) and reverse (PTR record) published in DNS, with values identical to those supplied in the FQDN field of the Send Connector’s general tab. If both the send and receive connectors are hosted on the same server, then the MX record should likewise point to that server’s name.
To have your company receive mail for several domains, you need only change the MX record for each name to point to the same FQDN. An MX record need not direct traffic to a server part of the same DNS domain as the MX record itself.
Maybe you’re wondering, “Why does it matter so much that these names are identical?”… The fundamental cause is that most Anti-Spam services take the presence of mismatched records and the absence of a reverse DNS entry as indicators that mail from this host should be regarded as Spam. Mail from hosts without a corresponding reverse DNS entry is blocked by some companies (including AOL and Comcast). Getting business email delivered means reducing Anti-Spam services’ concerns that the email is Spam.
Quickly and easily verify your company’s DNS settings with the help of the tools provided by mxtoolbox.com. Type a: Servername into the command prompt to locate your server’s forward or A record. Servername is your server’s fully qualified domain name as specified in the FQDN of your Send Connector in Exchange.
If you know the public IP address of your server, you may look up its PTR record by entering ptr: IPAddress into the command box. All is well if the answers to these questions are consistent. If not, don’t worry; there’s an easy solution.
Publishing the forward address (A record) in DNS is the same as printing any other address. Just like you did when you added your MX record or published the WWW URL for your domain, you will need to interact with your DNS hosting provider to post the name you have set up for your send connector by giving them the full term and apparent IP address. The PTR record, or reverse entry, is where things get complicated.
Since your business probably doesn’t own the IP block it’s utilizing, your ISP is the only entity that may publish a PTR record on your behalf. Therefore, you must coordinate with your Internet service provider to post the reverse entry. Since this is a frequent request, many ISPs have implemented this feature in their online support centers. However, this method is only viable if your Internet service provider provides a static IP address or range.
The method above won’t function if your ISP assigns a dynamic IP address. Assuming you want to ensure the safe arrival of your mail, a decision must be made. You can use a “Smarthost” or switch to an ISP that offers a Static IP range and proceed as described above. What we mean by “Trusts you” is that the server(s) you’re using on the internet “Trusts you.”
This premium service allows you to authenticate your mail server from any IP address using a single username and password. These servers are responsible for forwarding your emails to their final recipients. Your Internet service provider (ISP) is usually the best place to look first. However, many Internet service providers (ISPs) actively restrict SMTP (email) traffic from their dynamic IP service range to maintain a positive reputation. Thus, you must verify that they do not offer this service to their clients.