Proper Email Server Configuration - Properly Configure Your Public DNS

sizcache="" sizset="47">

When one 1st tackles the project of acquiring World-wide-web mail delivered to their mail program, you are exceptionally easily pointed to the will need for receiving an MX record published within your domain's public DNS zone. It is this record that tells all of the other mail servers on the planet exactly where to route e-mail destined for your domain.

What most do not tell you is the significance of receiving each the forward (A record) and reverse (PTR record) DNS entries proper for the server that is the send connector. In some cases this is the identical server as the get connector, but it does not have to have to be. It is incredibly very important that any server that is configured as an World wide web Send Connector have each a forward (A record) and reverse (PTR record) published in DNS, and that these records specifically match what you have entered in the FQDN field on the common tab of your Send Connector. If this 1 server is hosting each the send and obtain connectors, the MX record should really also point to this similar name. If your organization accepts mail for extra than 1 domain, merely point the MX record in each domain to the exact same FQDN. There is no requirement that an MX record point to a server in the similar DNS domain as the MX record.

You may well be thinking, "Why is it so vital that all of these names match?"...  The underlying reason is that mismatched entries and a lack of a reverse DNS entry are made use of by most Anti-Spam services as a signal that mail messages from this host should really be treated as Spam. Some organizations, such as AOL and Comcast, go as far as to outright block mail from hosts that do not have a matching reverse DNS entry. If your organization's e-mail is to get delivered, you will need to do everything you can to lower the suspicions of the Anti-Spam services.

You can check your organization's DNS entries easily and readily making use of the tools at . To appear for the forward or A record of your server, simply enter a:Servername in the command box, exactly where Servername is the completely qualified domain name of your server as entered in the FQDN of your Send Connector inside Exchange. To look for the reverse or PTR record, simply enter ptr:IPAddress in the command box, where IPAddress is your server's public IP address. If the results of these queries are consistent, you are all set. If not, don't fret the fix is not troublesome.

Getting the forward (A record) entry published in DNS is no numerous than publishing any other address. You simply work with your DNS hosting provider to publish the name you have setup for your send connector just like you did when you added your MX record or published the WWW address for your domain by providing them with the full name and apparent IP address. It is the reverse entry or PTR record that is a bit tricky. This is simply because you cannot directly publish your own PTR record as you are most most likely not the owner of the IP block your organization is working with your ISP is. You simply have to have to function with your ISP to publish the reverse entry. This is a frequent request and lots of of the larger ISPs have even added this functionality to their customer self-help portals. This approach only works although if you have a static IP address/range from your ISP.

 If your Online service is being issued a dynamic address, this above approach will not function. Assuming that you have to have to make confident your mail is delivered you will then have a selection to make. You can either change your ISP service to 1 with a Static IP range and follow the directions above, or use a "Smarthost". A Smarthost is simply a different server or servers on the Online that "Trusts you". This is typically a paid service exactly where they deliver you with a username/password mixture to authenticate your mail server regardless of the IP address it is making use of at the time. It is these servers that then deliver your mail messages to their ultimate destination. Your ISP will normally present this service, so commence with them 1st. It is significant that you make positive that they do not provide this service for their customers as a large number of ISPs actively block SMTP (email) targeted traffic from their whole dynamic IP service range to keep themselves on very good standing.